MCP Setup
Connect Claude Code, Cursor, Codex, or any MCP client to your Cygent agent with a scoped, per-user API key.
Overview
Connect Claude Code, Cursor, Codex, or any MCP-compatible client to your Cygent agent. Your IDE's agent gets a set of read tools plus cygent_chat — a conversational tool that routes plain-English requests through the same brain that powers your Slack/Discord/Telegram agent. It can query findings, trigger audits and PR reviews, run dependency scans, and (within scope) change findings — without leaving your editor.
Each key is per user and carries a scope (read / operate / mutate) that bounds everything it can do. There are no confirmation prompts over MCP — the scope you pick at key creation is the guard.
The MCP companion (swarm) is a paid feature. The connection is refused for orgs on a trial, without an active subscription, suspended for non-payment, or over their usage limit.
Step 1 — Create an MCP API key
Open Settings → API Keys
In the dashboard, go to your instance's Settings tab and open the API Keys sub-tab.
Create a key
Click Create Key, give it a name, and pick a scope:
- Read — query findings, projects, dependencies, and the knowledge base. No jobs, no changes.
- Operate — everything in Read, plus triggering audits, PR reviews, triage, and dependency scans.
- Mutate — everything in Operate, plus changing findings and settings.
Start with the lowest scope that does the job — you can always create another key.
Copy the key now
The full cygent_mcp_… key is shown once, at creation. Copy it immediately — only a short prefix is stored afterward, so a lost key must be revoked and replaced. Each user can hold up to 10 keys.
The API Keys card renders ready-to-paste config for each client with your endpoint URL and the new key pre-filled — copy straight from there instead of editing the snippets below by hand.
Step 2 — Configure your client
Replace YOUR_MCP_URL with your instance's MCP endpoint (shown on the API Keys card, e.g. https://your-instance.cygent.app/mcp) and YOUR_API_KEY with the key you just created. Transport is Streamable HTTP.
Choose your path
Run from terminal:
claude mcp add --transport http cygent YOUR_MCP_URL -H "Authorization: Bearer YOUR_API_KEY"
Then run /mcp in a Claude Code session to verify the connection.
Or add manually to ~/.claude/mcp_servers.json (global) or .claude/mcp_servers.json (project-scoped):
{
"cygent": {
"type": "streamable-http",
"url": "YOUR_MCP_URL",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
v1 supports header-auth clients only. Web connectors that require OAuth 2.1 + Dynamic Client Registration (claude.ai, ChatGPT) are a planned fast-follow.
Once your client is configured you'll see cygent_* tools appear in its MCP tool list. Ask your IDE "list my Cygent projects" to smoke-test — it should call cygent_list_projects and return your repos.
Revoking a key
Revoke a key any time from Settings → API Keys — it stops authenticating immediately. A revoked key can then be removed from the list. You manage your own keys; org owners can see and revoke any key on the instance. Use a fresh key per machine or per agent so you can revoke one without disrupting the others.