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 the tools you already work in, with the permissions you already have.
https://mcp.hyphen.ai/Point your client at one URL. Sign in, and start asking.
Hyphen hosts the server, so there is nothing to install or run yourself. Clients that support the MCP OAuth flow sign you in through auth.hyphen.ai; anything else sends an API key as the x-api-key header.
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, behind one connection.
You do not call these yourself. Your assistant picks the ones a request needs, and these are the areas they cover.
Ship from a conversation
The packaged deploy_app workflow reads the repo your coding agent has open, sets up the project, app, and Docker packaging, ships preview-first, watches the run and its logs, and promotes to production only after you confirm.
About DeployManage 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.
About ToggleClean up stale flags
Telemetry-backed tools find the 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.
About AgentShort links and analytics
Create short links and QR codes, then pull clicks, referrers, countries, and devices back to see how a campaign is doing.
Link documentationAnswers from live docs
The server carries an index of this documentation, so platform questions are answered from the current pages rather than from stale training data.
Guided migrations
Move flags off LaunchDarkly, Split, or Unleash, secrets off Doppler or Vault, and links off Bitly, with each step mapped to the tool or hx command that performs it.
Real capability for the agent. Your permissions, on every request.
Enforced by the Hyphen API on each call, not by trusting the model to behave.
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, by 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, and versions, never values.
Frequently Asked Questions
What is the Hyphen MCP server?
MCP (Model Context Protocol) is the open standard AI clients use to call external tools. The Hyphen MCP server exposes 60+ tools for deployments, feature flags, ENV secrets metadata, short links, audit events, agent tasks, and live documentation. Assistants like Claude, Cursor, and VS Code use them to manage your Hyphen organization conversationally.
Hyphen hosts the server at https://mcp.hyphen.ai/, so there is nothing to install or run yourself.
Which AI tools and MCP clients are supported?
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.
How does authentication work?
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.
Can a connected agent read my ENV secret values?
No. Hyphen ENV values are end-to-end encrypted with a key only you hold, so the server can read only secret names, counts, and versions. It cannot read secret values. When you need actual values, use the Hyphen CLI (hx env pull) locally, where decryption happens with your key.
Is it safe to let an agent deploy or change things?
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.
Is the server open source?
Yes. The server is open source at github.com/Hyphen/mcp and published to the official MCP registry as ai.hyphen/mcp.
Connect it in one line.
Add the server, sign in, and ask your assistant who you are in Hyphen. Everything it can do from there, it does as you.