How to integrate DevCycle MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With DevCycle MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

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

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With DevCycle MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate DevCycle with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install DevCycle MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the DevCycle MCP server, 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 to your projects, features, environments, audiences, configurations, and variables, so your agent can list projects, inspect feature configurations, search audiences, review environments, and manage variables on your behalf.

  • Project and feature discovery: Have your agent list available DevCycle projects and filter their current features to find the work that matters.
  • Feature configuration review: Let the agent inspect a feature's targeting configurations across every environment or within one selected environment.
  • Environment and audience lookup: Direct your agent to list project environments, search audiences, and check whether each audience is in use.
  • Variable discovery: Instruct your agent to list and filter project variables, including those associated with a specific feature.
  • Variable management: Have your agent create typed variables, update their editable properties, or permanently delete a selected variable.

Conclusion

You've successfully integrated DevCycle with Codex using Composio's MCP server. Now you can interact with DevCycle directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for DevCycle operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various DevCycle operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
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. Codex 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