How do I get DevCycle API credentials?

Log in to your DevCycle dashboard, navigate to **Settings > Organization > API Management**, and create a new Client ID and Client Secret.

Can the agent toggle feature flags?

Yes, you can use the update_feature_flag_status tool to set a flag to 'active' or 'archived' directly from the agent.

Does the integration show SDK keys?

Yes, the get_environment_sdk_keys tool allows the agent to retrieve the specific identifiers needed for your web, mobile, or server-side SDKs.

DevCycle MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: DevCycle
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install DevCycle and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About DevCycle MCP Server

Integrate DevCycle, the modern feature flag and experimentation platform, directly into your AI workflow. Manage your feature flags across projects, monitor staging and production environments, and audit targeting rules and variations using natural language.

GitHub Copilot Agent mode brings DevCycle data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Feature Flag Management — List, search, and retrieve detailed configuration for all your feature flags.
Environment Oversight — Monitor project environments, retrieve SDK keys, and track deployment statuses.
Variable & Variation Tracking — List all defined variables and their variations to ensure technical consistency.
Operational Control — Update feature flag statuses (active/archived) directly via chat.

The DevCycle MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect DevCycle to VS Code Copilot via MCP

Follow these steps to integrate the DevCycle MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using DevCycle

Ask Copilot: "Using DevCycle, help me...". 10 tools available

Why Use VS Code Copilot with the DevCycle MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with DevCycle through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

DevCycle + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the DevCycle MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

DevCycle MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect DevCycle to VS Code Copilot via MCP:

get_environment_sdk_keys

List SDK keys for all environments in a project

get_feature_flag_details

Get full configuration and targeting rules for a specific feature flag

get_project_details

Get detailed information for a specific DevCycle project

list_active_flags

Identify feature flags that are currently active

list_devcycle_projects

List all projects in your DevCycle account

list_feature_flags

g. release, ops), and current statuses. List all feature flags within a specific project

list_feature_variables

List all variables defined in a project

list_project_environments

List all environments (e.g. Production, Staging) for a project

search_feature_flags

Search for feature flags in a project by keyword

update_feature_flag_status

Update the status (e.g. active, archived) of a feature flag

Example Prompts for DevCycle in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with DevCycle immediately.

"List all feature flags in the project 'Main-App'."

"Show me the configuration for the 'Beta-Feature' flag."

"What are the SDK keys for our 'Production' environment?"

Troubleshooting DevCycle MCP Server with VS Code Copilot

Common issues when connecting DevCycle to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

DevCycle + VS Code Copilot FAQ

Common questions about integrating DevCycle MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.