How to Use the DevCycle MCP in Claude

Q: How do I install the DevCycle MCP server in Claude Desktop?

Open your claudedesktopconfig.json file. Add the server command and arguments under the mcpServers key, then restart the application. You can also paste the remote URL directly into Claude Web under the Integrations tab.

Q: Can Claude Desktop actually change DevCycle feature flags?

Yes. The agent uses the updatefeatureflagstatus tool to modify flag states. It requires proper API permissions, so ensure your token has write access if you want automated toggling.

Q: How do I find specific DevCycle flags using Claude Desktop?

Tell your agent what you are looking for. It runs searchfeatureflags to scan your project for keywords and returns the matching configurations.

Give Claude Desktop direct control over your DevCycle feature flags and environments.

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 Claude Desktop

Create your Vinkius account to connect DevCycle to Claude Desktop 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 Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Control rollouts via Claude Desktop

`update_feature_flag_status` lets your agent flip toggles directly from the chat interface. You don't need to log into the dashboard to kill a broken feature. Tell Claude to archive the old flag, and it executes the state change instantly. Pair this with `list_active_flags` to see exactly what is running in production right now. When a deployment goes wrong, your agent pulls the live configuration and shuts down the offending variation before the support tickets pile up.

Query environment configurations

`list_project_environments` returns the exact setup for your staging and production tiers. This MCP server pulls the raw environment data so you stop guessing which keys belong to which deployment. Need the actual credentials? Your agent calls `get_environment_sdk_keys` to grab them instantly. It speeds up local testing when you don't have to hunt through settings pages just to connect a new test client.

Inspect variables and targeting rules

`get_feature_flag_details` dumps the complete targeting logic and variation rules into your context window. If a user complains about missing a feature, your agent checks the exact rollout percentage and user segment logic. You can also map out the entire project using `list_feature_variables` and `search_feature_flags`. It gives you a clear picture of every variable tied to a specific project, making cleanup of stale code significantly faster.

Setup guide

Set up DevCycle MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The DevCycle MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the DevCycle MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under devcycle-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 Claude Desktop

Open your `claude_desktop_config.json` file. Add the server command and arguments under the `mcpServers` key, then restart the application. You can also paste the remote URL directly into Claude Web under the Integrations tab.

Yes. The agent uses the `update_feature_flag_status` tool to modify flag states. It requires proper API permissions, so ensure your token has write access if you want automated toggling.

It does. You connect the remote MCP server URL via the Custom Connectors menu. Product managers can check flag statuses without installing the local desktop application.

Tell your agent what you are looking for. It runs `search_feature_flags` to scan your project for keywords and returns the matching configurations.

The server reads feature variables, environment SDK keys, and targeting rules. Vinkius runs this connection in an ephemeral V8 Isolate Sandbox. Your credentials and flag configurations remain isolated and are never stored after the session ends.

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