How to connect DevCycle to Claude

Connect Claude Web, Desktop and Cowork to DevCycle MCP. List active flags in production, create checkout rollout feature flag, and more using natural language, with authentication handled for you.

DevCycle logoDevCycle
S2s Oauth2

DevCycle is a feature management platform for feature flags, targeting, releases, and monitoring. It helps teams ship safely with controlled rollouts, experiments, and fast rollback.

9 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your DevCycle account to Claude via Composio Connect, enabling it to list active flags in production, create checkout rollout feature flag, summarize recent DevCycle flag changes, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate DevCycle with

Connecting DevCycle to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your DevCycle account

Back in Claude, ask it to connect to DevCycle or give it any DevCycle-related task.

For example, ask Claude to:

  • "List active flags in production"
  • "Create checkout rollout feature flag"
  • "Summarize recent DevCycle flag changes"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your DevCycle account is ready to use.

What is the DevCycle Claude Connector, and what's possible with it?

The DevCycle MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your DevCycle account. It provides structured and secure access so your agent can perform DevCycle operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for DevCycle?

The connector can show as connected, but Claude must use it in each DevCycle conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to DevCycle again.

2. Why does Claude show an MCP server error before DevCycle connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for DevCycle.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect DevCycle.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the DevCycle authorization link not work?

The Composio connector is one server. Your DevCycle account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the DevCycle connection.
  • Composio creates a fresh DevCycle authorization link.
  • Open that link in your browser and finish the DevCycle sign-in.

4. Why do DevCycle actions fail after they worked before?

The DevCycle connection can expire or lose permission.

  • Ask Claude to inspect the DevCycle connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the DevCycle account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in DevCycle.
  • If the action still fails with a permission error, check that the connected account has that permission in DevCycle itself.

5. How do I switch to a different DevCycle account?

Claude can manage the DevCycle connection for you.

  • Ask Claude to disconnect or delete the current DevCycle account.
  • Ask Claude to connect DevCycle again.
  • Open the new Composio authorization link for DevCycle.
  • Sign in with the other DevCycle account in the browser.
  • After the account connects, ask Claude to retry the DevCycle task.

6. Why is my DevCycle connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your DevCycle connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If DevCycle tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect DevCycle.
TOOLS

Supported Tools

Every DevCycle action and event your agent gets out of the box.

Create Variable

Create a typed variable in a DevCycle project, optionally associating it with a feature.

Delete Variable

Permanently delete exactly one DevCycle variable, selected by key or stable ID, from the specified project.

List Audiences

List and search project audiences, optionally including whether each audience is used.

List Environments

List environments in a DevCycle project without exposing SDK key values.

List Feature Configurations

Inspect a feature's targeting configurations across all environments or one selected environment.

List Features

List and filter current Feature v2 resources in a DevCycle project.

List Projects

List DevCycle projects visible to the connected Management service account, with filtering and controlled pagination.

List Variables

List and filter variables in a DevCycle project, including variables associated with a feature.

Update Variable

Update one or more editable properties of an existing DevCycle variable.

FAQ

Frequently asked questions

With a standalone DevCycle MCP server, the agents and LLMs can only access a fixed set of DevCycle tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from DevCycle and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right DevCycle tools.

Yes, absolutely. You can configure which DevCycle scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your DevCycle data and credentials are handled as safely as possible.

Start with DevCycle.It takes 30 seconds.

Managed auth, hosted MCP servers, and every DevCycle tool your agent needs.Free to start.

Start building