How to Use the DevCycle MCP in Windsurf

Q: How do I search for specific variables using DevCycle inside Windsurf?

Ask Cascade to find a variable, and it will use listfeaturevariables to scan your project. It maps those variables back to their respective flags, presenting the exact code context directly in your editor.

Q: What happens if Cascade tries to read an invalid project?

The getprojectdetails tool will return a clean API error. Cascade reads this error, explains what went wrong, and prompts you to select a valid project from your account list.

Q: Does this integration expose my DevCycle SDK keys or configuration data?

No. All API keys retrieved via getenvironmentsdkkeys remain inside the local V8 sandbox on Vinkius. Your sensitive environment variables and flag rules are never sent to third-party LLMs; they only pass directly to your local editor session via the MCP.

Let Cascade autonomously audit, target, and toggle DevCycle feature flags across your environments in Windsurf.

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 Windsurf

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-step flag audits directly in Windsurf

To inspect your release pipeline, the agent starts by running `list_devcycle_projects` to find your active projects. Cascade chains this with `list_project_environments` to see where your features are deployed, bypassing the web dashboard entirely. Once it locates the correct environment, Cascade uses `get_environment_sdk_keys` to check configuration details. It builds a complete map of your active environments so you know exactly where your code is running before you trigger a release.

Real-time targeting rule checks

To analyze who gets what variation, the agent uses `get_feature_flag_details` to pull down active targeting rules directly into your editing session. This lets you inspect the logic without forcing you to open a browser. If you need to find a specific flag in a massive project, the agent runs `search_feature_flags` to pinpoint the exact key. It handles the search, reads the configurations, and presents the targeting logic right where you write code.

Autonomous flag cleanups

To clean up stale code, Cascade calls `list_active_flags` to identify which flags are still running in your environment. It checks your local files to see where those flags are referenced, finding the dead code and preparing the cleanup. To make the change official, the agent triggers `update_feature_flag_status` to archive the flag. You get a clean codebase and an updated dashboard in a single, autonomous sweep via the MCP integration.

Setup guide

Set up DevCycle MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the DevCycle MCP

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

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my DevCycle payment history." If connected, Cascade will call the DevCycle tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.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 Windsurf

Cascade auto-discovers the server once you add it to your configuration file. It can then autonomously chain tools like `list_feature_flags` to inspect and modify your flags based on your natural language prompts.

Yes, but you should configure Cascade's execution permissions. While the agent can call `update_feature_flag_status` to toggle flags, we recommend setting write operations to require manual confirmation in your IDE settings.

Ask Cascade to find a variable, and it will use `list_feature_variables` to scan your project. It maps those variables back to their respective flags, presenting the exact code context directly in your editor.

The `get_project_details` tool will return a clean API error. Cascade reads this error, explains what went wrong, and prompts you to select a valid project from your account list.

No. All API keys retrieved via `get_environment_sdk_keys` remain inside the local V8 sandbox on Vinkius. Your sensitive environment variables and flag rules are never sent to third-party LLMs; they only pass directly to your local editor session via the MCP.

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