Download PDF Markdown Version

Claude

ChatGPT

Perplexity

Gemini

Microsoft Copilot

Raycast

Meta AI

Grok

Z.ai

Qwen

Kimi

DeepSeek

Mistral

Cursor

VS Code

Windsurf

JetBrains

Cline

Lovable

Vercel AI SDK

LangChain

Use Alpic with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. AI MCP infrastructure: deploy, manage, and monitor MCP servers programmatically via agents.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPT

Claude

Cursor

Perplexity

Gemini

Microsoft Copilot

Raycast

Meta AI

Complete set · 18 capabilities

The complete Alpic capability set.

These are the exact actions your AI can choose when you ask it to work with Alpic.

Capability set01 / 05

01-04

4 capabilities in this set.

Part of 18 available through Alpic.

01
Add variable
Use this to set API keys, database URLs, feature flags, or any configuration needed by your MCP server. Requires project ID, environment ID, variable key, and value. Variable values are stored securely. Add a new environment variable to an Alpic environment
02
Create project
Requires project name and team ID. Optionally set description, repository URL, and initial configuration. Returns the created project details including the new project ID needed for subsequent operations. Create a new MCP server project in Alpic
03
Deploy environment
The deployment runs asynchronously. Returns the deployment ID which can be used with get_deployment to check status. Use this to push new MCP server versions to dev, staging, or production environments. Trigger a new deployment for a specific Alpic environment
04
Get deployment
Requires the deployment ID. Use this to check if a deployment succeeded, review deployment history, or debug failed deployments. Get detailed status and metadata for a specific Alpic deployment

Capability set02 / 05

05-08

4 capabilities in this set.

Part of 18 available through Alpic.

05
Get deployment logs
Useful for debugging failed deployments, understanding build output, or verifying successful startup of the MCP server. Requires project ID and environment ID. Get deployment logs for a specific Alpic environment
06
Get project
Requires the project ID from list_projects results. Use this to review project settings before making updates or triggering deployments. Get detailed information about a specific Alpic MCP server project
07
Get tunnel ticket
Returns the tunnel URL and ticket token. Use this during development to test your MCP server before deploying to a production environment. Get a tunnel ticket for local development and testing of an MCP server
08
List environments
Each environment has its own URL, variables, and deployment status. Returns environment IDs, names, URLs, and current deployment state. Use this to identify which environment to deploy to or manage variables for. List all environments (dev, staging, prod) for a specific Alpic project

Capability set03 / 05

09-12

4 capabilities in this set.

Part of 18 available through Alpic.

09
Publish to registry
Requires project ID and optionally a server description and category. Use this to make your MCP server publicly available. Publish an MCP server to the official MCP registry via Alpic
10
Update project
Only pass the fields you want to change. Requires the project ID from list_projects results. Use this to rename projects, update descriptions, or point to a new repository branch. Update an existing Alpic MCP server project configuration
11
Delete project
This action cannot be undone. Use with caution. Requires the project ID. Confirm with the user before proceeding. Delete an Alpic MCP server project
12
Delete variable
Use this to clean up unused configuration keys. Requires project ID, environment ID, and variable key. Delete an environment variable from an Alpic environment

Capability set04 / 05

13-15

3 capabilities in this set.

Part of 18 available through Alpic.

13
Get project analytics
Requires the project ID. Use this to monitor MCP server health, identify performance trends, and troubleshoot issues. Get analytics and usage data for a specific Alpic project
14
Get server info
Use this to verify which MCP capabilities are exposed and confirm the server is running correctly. Get server information and status for a specific Alpic project
15
List projects
Returns project IDs, names, descriptions, associated teams, deployment status, and environment counts. Use this to overview your entire MCP infrastructure before managing specific projects or triggering deployments. List all MCP server projects in your Alpic account

Capability set05 / 05

16-18

3 capabilities in this set.

Part of 18 available through Alpic.

16
List teams
Each team contains projects and environments for deploying MCP servers. Returns team IDs, names, and member counts. Use this first to identify which team to manage projects under. List all teams associated with your Alpic account
17
List variables
Variable values are masked for security. Returns variable keys and metadata. Use this to audit environment configuration before deploying or adding new variables. List all environment variables configured for an Alpic environment
18
Create environment
Requires environment name and project ID. Optionally set initial variables and configuration. Each environment gets a unique URL for MCP client connections. Returns the created environment details. Create a new deployment environment (dev, staging, prod) for an Alpic project

Observed, not estimated

952ms average. Fast in production.

Alpic is checked daily against the live service.

Daily averagePeak 1149ms

Aug 20Today

Fastest day: 802ms
Slowest day: 1149ms
14-day trend: Slowing+18%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 18 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Alpic, so you can see the experience inside your AI.

It does not authenticate your account with Alpic. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Alpic Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Alpic capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "alpic-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_2KgnFzVSaiaSHBNFbROaJ4IhOHTa3rucrY1KgZYb/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Alpic owners ask.

01
Can I deploy environments from specific Git branches directly from the terminal?
Yes! You can operate create_environment mapping parameters matching your active branches, then instruct your agent to trigger the deploy_environment sync.
02
Are environment variables secured during deployment processes?
Absolutely. You can invoke add_variable providing exact tokens without storing them in repositories. They remain encrypted at rest and dynamically injected upon startup.
03
Can I test server configuration before final production merges?
Yes. Request your AI agent to trigger get_tunnel_ticket enabling you to natively tunnel local host environments through Alpic before pushing any true integration commits.

Explore

More in Friends