How to Use the Alpic MCP in VS Code Copilot

Q: How do I view Alpic analytics in VS Code?

Ask Copilot for a health check. The agent uses getprojectanalytics to pull live performance data and error rates directly into the chat panel.

Q: Can I test Alpic projects locally before committing?

The agent can generate a temporary URL using gettunnelticket. This lets your team validate changes against live webhooks before merging the pull request.

Manage your Alpic MCP fleet directly through VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Alpic MCP to VS Code Copilot

Create your Vinkius account to connect Alpic to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Alpic with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Control Alpic Teams in VS Code

Alpic transforms VS Code Copilot into a centralized control plane for your entire engineering organization. A developer asks Copilot to list available workspaces, and the agent calls `list_teams` to pull member counts and IDs. You manage team-wide infrastructure without leaving your IDE. Onboarding new microservices happens instantly. Copilot executes `create_project` to provision a new MCP server and attach the company's repository URL. Because the configuration file is committed to Git, every engineer on the team gets immediate access to manage that specific project.

Sync Environments Across the Organization

Keeping dev, staging, and production environments aligned is a massive headache that Alpic solves natively. Copilot runs `list_environments` to pull the active URLs and deployment states for your current project. The agent compares the configurations and tells you exactly what differs between staging and prod. Missing configuration keys get fixed via chat. If a staging environment lacks a feature flag, Copilot invokes `add_variable` to inject it. It cleans up deprecated keys by calling `delete_variable`, ensuring your team's configuration remains pristine across all deployment tiers.

Monitor MCP Server Health

Tracking API performance usually means logging into a separate dashboard, but Alpic brings the metrics straight to your editor. Copilot triggers `get_project_analytics` to fetch request volumes and latency trends. You see exactly which endpoints are failing before you even write a bug fix. Retiring old services is just as straightforward. When a project hits end-of-life, Copilot verifies the shutdown with you and executes `delete_project`. It wipes the environments and frees up resources, keeping your team's infrastructure lean.

Setup guide

Set up Alpic MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Alpic MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Alpic tools listed. Try asking: "List my recent Alpic transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "alpic-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Alpic. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Alpic now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Alpic MCP in VS Code Copilot

Commit a .vscode/mcp.json file to your repository root. Every developer who clones the repo will automatically inherit the Alpic MCP Server configuration.

Yes. Switch Copilot Chat to Agent mode and ask it to push your code. It runs deploy_environment and tracks the progress asynchronously.

Ask Copilot for a health check. The agent uses get_project_analytics to pull live performance data and error rates directly into the chat panel.

The agent can generate a temporary URL using get_tunnel_ticket. This lets your team validate changes against live webhooks before merging the pull request.

The integration processes team IDs, project metadata, and environment variables. Alpic enforces strict role-based access control at the team level, guaranteeing that developers only interact with configurations and secrets they are authorized to modify.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript