How to Use the DevCycle MCP in VS Code Copilot

Q: How do I share the DevCycle MCP server across my team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and add the server configuration. Commit this file to Git. Anyone who pulls the repo and uses VS Code 1.96+ gets instant access.

Q: Can VS Code Copilot read DevCycle staging environments?

Yes. The agent uses listprojectenvironments to find your staging setup, then grabs the specific details. It reads whatever environments your API token has permission to view.

Q: How do I get DevCycle SDK keys using VS Code Copilot?

Ask Copilot for the keys. It triggers the getenvironmentsdkkeys tool and outputs the credentials for your specified project and environment.

Give your whole engineering team direct DevCycle control inside 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 DevCycle MCP to VS Code Copilot

Create your Vinkius account to connect DevCycle 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 DevCycle with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Standardize DevCycle access via MCP

`list_feature_flags` pulls your entire project's toggle inventory straight into the Copilot chat. When a developer asks why a feature isn't showing up locally, the agent checks the actual API state instead of guessing. You commit the MCP configuration to `.vscode/mcp.json` so every engineer gets the same tools. The agent uses `list_active_flags` to debug routing issues, keeping your team aligned on what is actually running in staging.

Inspect targeting rules inline

`get_feature_flag_details` extracts the exact user segments and variation logic for any toggle. If a bug report comes in for a specific user cohort, Copilot reads the live DevCycle rules to see if the flag is misconfigured. It maps the available data using `list_feature_variables` before writing any new implementation code. This prevents developers from creating duplicate variables or using the wrong data types for existing flags.

Manage project states directly

`update_feature_flag_status` allows developers to enable or archive flags without leaving their IDE. You spot a broken feature in local testing, and you tell Copilot to turn it off immediately. The server also provides `list_devcycle_projects` and `get_project_details` for structural context. When onboarding new hires, Copilot can explain the exact environment setup by querying the live API.

Setup guide

Set up DevCycle 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 DevCycle 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 DevCycle tools listed. Try asking: "List my recent DevCycle transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "devcycle-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 DevCycle. 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 DevCycle 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 DevCycle MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and add the server configuration. Commit this file to Git. Anyone who pulls the repo and uses VS Code 1.96+ gets instant access.

Yes. The agent uses `list_project_environments` to find your staging setup, then grabs the specific details. It reads whatever environments your API token has permission to view.

It works with any Copilot tier running inside VS Code. As long as you have Agent mode enabled and the MCP extension active, the tools function normally.

Ask Copilot for the keys. It triggers the `get_environment_sdk_keys` tool and outputs the credentials for your specified project and environment.

This server handles project IDs, variation rules, and SDK keys. Vinkius routes the requests through an ephemeral, stateless sandbox. Your infrastructure data passes directly to the IDE and never touches disk on our end.

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