Hyphen MCP Server

Connect Claude, Cursor, VS Code, or any MCP client to your Hyphen organization — deploy apps, manage feature flags, investigate incidents, and operate automations from your AI tools, with the same permissions you have in the app.

Documentation

Connect your client in minutes

Hyphen hosts the server — there is nothing to install or run yourself. Point any MCP client at the endpoint and sign in with OAuth, or use an API key from the Hyphen app.

https://mcp.hyphen.ai/

One command — Claude Code signs you in with OAuth the first time it connects:

claude mcp add --transport http hyphen https://mcp.hyphen.ai/

Open source at github.com/Hyphen/mcp and published to the official MCP registry as ai.hyphen/mcp.

60+ tools across the platform, one connection

Ship From a Conversation

The packaged deploy_app workflow analyzes the repo your coding agent has open, sets up the project, app, and Docker packaging, ships preview-first, watches the run and logs, and promotes to production only after you confirm.

Manage Feature Flags End to End

Create and update toggles and segments, adjust targeting, and verify with a live edge evaluation that returns the same answer a real user would receive.

Clean Up Stale Flags

Telemetry-backed tools find flags that no longer vary, and a guided workflow removes them from your codebase before retiring them in Hyphen.

Investigate Incidents

Search the organization audit log and correlate it with deployment runs, logs, and metrics to answer “what changed right before things broke?”

Operate Agent Tasks

Schedule and inspect Hyphen Agent automations, review their runs, and answer their questions when a run is waiting on input.

Links, Geolocation & Live Docs

Create short links and QR codes, analyze click performance, look up IP geolocation, and answer platform questions from live documentation instead of stale training data.

Built for safe autonomy

Agents get real capability, and you keep control — enforced by the Hyphen API on every request, not by trust in the model.

Your Credential, Your Permissions

Every tool call runs as you. What a connected agent may do is decided per request from your organization membership and roles — the same rules as the Hyphen App.

Permission Prompts on Writes

Tools that modify data are annotated as such, and deletes, deployment triggers, and agent chat carry a destructive hint, so MCP clients ask for your confirmation before running them.

A Production Gate on Deployments

A deployment run that targets a production-type environment is refused unless the call explicitly acknowledges production — and agents are instructed to do that only after you confirm.

Secrets Stay Encrypted

ENV values are end-to-end encrypted with a key only you hold, so the server can only ever read secrets metadata — names, counts, versions — never values.

Frequently Asked Questions

MCP (Model Context Protocol) is the open standard AI clients use to call external tools. The Hyphen MCP server exposes 60+ tools across the Hyphen platform — deployments, feature flags, ENV secrets metadata, short links, audit events, agent tasks, and live documentation — so assistants like Claude, Cursor, and VS Code can manage your Hyphen organization conversationally.
Hyphen hosts the server at https://mcp.hyphen.ai/, so there is nothing to install or run yourself.
Any MCP client that speaks streamable HTTP works, including Claude Code, Claude Desktop, claude.ai, Codex, Cursor, and VS Code. Clients that support the MCP OAuth discovery flow sign you in automatically; everything else can authenticate with an API key sent as the x-api-key header.
The server is authenticated by default — every request needs a Hyphen credential, and your organization is resolved automatically from it. OAuth is recommended: the server points unauthenticated clients at its OAuth discovery metadata and your client signs you in via auth.hyphen.ai. Alternatively, create an API key in the Hyphen app (Settings → API Keys) and send it as the x-api-key header.
If you belong to multiple organizations, pin one by using the https://mcp.hyphen.ai/{organization-id}/ form of the URL.
No. Hyphen ENV values are end-to-end encrypted with a key only you hold, so the server can only ever read secrets metadata — names, counts, and versions — never values. When you need actual values, use the Hyphen CLI (hx env pull) locally, where decryption happens with your key.
Every tool call runs as you, with the same permissions you have in the Hyphen App — organization membership and roles are enforced by the Hyphen API on each request. Tools that modify data are annotated so well-behaved MCP clients ask for your confirmation before running them, and destructive operations carry an additional destructive hint.
Deployments get an extra server-side gate: a run that targets a production-type environment is refused unless the call explicitly acknowledges production, and agents are instructed to do that only after you confirm.
Yes. The server is open source at github.com/Hyphen/mcp and published to the official MCP registry as ai.hyphen/mcp.