Skip to directory

About DevCycle MCP

DevCycle exposes feature flags, variables, project configuration, SDK setup, self-targeting overrides, and evaluation analytics to AI coding clients through local and hosted MCP servers.

What you can use it for

  • Inspect and manage feature flags and variables
  • Review feature audit history
  • Retrieve SDK install guidance
  • Set self-targeting identity and overrides for testing
  • Review feature or project evaluation totals
Connection and setup
Hosting
both
Transport
Not documented
Endpoint
https://mcp.devcycle.com/mcp (hosted; SSE fallback https://mcp.devcycle.com/sse)
Authentication
Hosted server uses OAuth 2.0 via DevCycle Auth0; user grants browser consent and selects an organization if needed, then selects a project with select_project. Local server uses dvc login sso and dvc projects select, or DEVCYCLE_CLIENT_ID, DEVCYCLE_CLIENT_SECRET, and DEVCYCLE_PROJECT_KEY.

Requirements

  • DevCycle account and project
  • For local server: Node.js 18+ and globally installed @devcycle/cli
  • For hosted server: MCP client supporting remote HTTP OAuth; clients without native support may require the documented client-specific bridge

Setup steps

  1. Hosted: add https://mcp.devcycle.com/mcp as a remote HTTP MCP server; if protocol negotiation fails, use https://mcp.devcycle.com/sse.
  2. Authenticate through the client browser flow, approve access, and choose the intended organization if prompted.
  3. Call select_project to choose/list projects before project operations.
  4. Local: install with npm install -g @devcycle/cli; authenticate using dvc login sso, then dvc projects select; configure stdio command dvc-mcp.
  5. The official docs provide client-specific setup for Claude Code/Desktop, Codex CLI/App, Cursor, VS Code, OpenCode, Antigravity CLI, and Devin Desktop.
  6. Verify with get_current_project or a read-only list_features request.
Tools 21

All 21 exact names are listed in DevCycle’s current comprehensive MCP reference. The docs say local and hosted servers share the tool implementation; some write tools can change production and delete tools are destructive.

  • list_features

    List project feature flags with search, pagination, status and type filters.

    01
  • create_feature

    Create a feature flag with associated variable, variations and initial targeting.

    02
  • update_feature

    Update a feature flag.

    03
  • update_feature_status

    Change feature status or static variation.

    04
  • delete_feature

    Delete a feature from all environments.

    05
  • cleanup_feature

    Retrieve the feature cleanup guidance prompt.

    06
  • get_feature_audit_log_history

    Retrieve audit log history for a feature.

    07
  • list_variables

    List project variables with filtering.

    08
  • create_variable

    Create a variable.

    09
  • update_variable

    Update a variable.

    10
  • delete_variable

    Delete a variable from all environments.

    11
  • get_current_project

    Get details for the selected project.

    12
  • select_project

    List or select the project for subsequent operations.

    13
  • install_devcycle_sdk

    Retrieve a language/platform SDK installation guide.

    14
  • get_self_targeting_identity

    Get the current identity used for self-targeting.

    15
  • update_self_targeting_identity

    Set or clear the self-targeting test identity.

    16
  • list_self_targeting_overrides

    List active self-targeting overrides.

    17
  • set_self_targeting_override

    Set a feature/environment variation override.

    18
  • clear_feature_self_targeting_overrides

    Clear overrides for a feature/environment.

    19
  • get_feature_total_evaluations

    Get feature evaluation totals by time period.

    20
  • get_project_total_evaluations

    Get project evaluation totals by time period.

    21
Limitations and notes
  • Feature/variable creation and updates can affect production and require confirmation; deletion tools are destructive and require explicit confirmation.
  • Dedicated environment tools are not exposed; select_project/get_current_project context provides project information.
  • Hosted and local servers share schemas/tools but differ in transport, authentication and state storage.
  • Rate limits, permissions and selected project can cause request failures; docs recommend checking credentials, permissions, token validity, project selection and retry behavior.
Original sources
  • official complete tool reference

    Current comprehensive reference documents the 21 feature, variable, project, self-targeting, analytics and SDK-installation tools.

  • official setup guide

    Current guide lists hosted endpoint, HTTP streaming and SSE fallback, OAuth setup and supported clients.

  • official server documentation

    Publisher documentation states local and hosted servers share tools, and warns about production and destructive operations.

Documentation checked 2026-10-28T13:41:09.000Z. Connection has not been runtime tested.

Similar tools