Code in Cursor with the spec in context.
Atrix is an MCP server for Cursor. Add one URL to .cursor/mcp.json, sign in, and Cursor's agent can read the spec and requirements pages behind an issue, check what the issue actually asks for, and move it on when you are done — within the scopes you approve.
7-day trial · card required · cancel anytime
Once connected
What Cursor's agent can do with Atrix
As of October 2026, Cursor uses MCP tools when they are relevant and asks for approval before each call by default.
Specs and requirements as context
search, pages_list and pages_get pull the spec, requirements page or decision note in full, so the agent codes against what was agreed rather than a paraphrase.
The issue behind the branch
work_get_issue returns the detail, last comments and status history. work_list_issues and project_status show what else is open in the product.
Close the loop
With write scopes, work_set_issue_status moves the issue to IN_REVIEW, work_comment_issue notes what changed and work_create_issue files the bug the agent found.
One server for the tracker and the docs
Issues and the pages that specify them live in the same Atrix workspace, so a single MCP entry gives Cursor both.
Data
Scoped, audited, revocable
Atrix receives only the tool calls Cursor makes, not your codebase or your chat with the agent. Each call is logged by tool, outcome and subject, never by contents.
What Atrix reads
- Only what the granted read scopes cover: work, projects, pages, ideas, CRM, calendar and more
- Deal values, hiring and people records only with both the scope and your permission
- Never pay or compensation, under any scope
What Atrix writes
- Nothing on the first connection, which asks only to read
- With write scopes you approve: issues, comments, statuses, pages and other records
- Feed posts only with the separately named feed.post scope
How to connect
Connect in three steps
To use a personal Atrix token instead of signing in, add "headers": { "Authorization": "Bearer ${env:ATRIX_TOKEN}" } beside the url. Cursor reads ${env:NAME} from your environment, so the token stays out of the file.
- Add the server — Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, containing { "mcpServers": { "atrix": { "url": "https://atrix.dev/api/mcp" } } }.
- Sign in to Atrix — Cursor supports OAuth for remote servers. When it asks you to sign in, pick the workspace in the browser and approve read access.
- Ask the agent — Check atrix is switched on under Customize in Cursor's sidebar, then ask: read the spec for this issue and implement it.
Plans
Cursor works on every plan
Connecting is free on the Atrix side, and Cursor's tool calls do not use Atrix AI runs.
Builder$39/mo
Connect Cursor with any scopes your role allows.
Studio$149/mo
Every one of your 15 seats can connect their own Cursor.
FAQ
Questions, answered
Should I use the project or the global config?
.cursor/mcp.json travels with the repository, so everyone who opens it gets the server and signs in as themselves. ~/.cursor/mcp.json applies to every project on your machine.
Is it safe to commit .cursor/mcp.json?
Yes, with the url only. Each person's OAuth sign-in stays in their own Cursor. If you use a token, reference it as ${env:ATRIX_TOKEN} and never paste it into the file.
Does the agent call Atrix without asking?
By default Cursor asks before each MCP tool call and lets you inspect its arguments. Separately, Atrix limits every call to the scopes you approved and your own permissions.
How does Cursor get permission to write?
The first connection asks only to read. When the agent calls a write tool, Atrix answers 403 insufficient_scope naming the scope it needs, and you approve exactly that scope.
Are there rate limits?
Yes: 120 calls and 30 writes a minute, per token. Over the limit, Atrix returns 429 with a Retry-After header in seconds.
Keep exploring
- Atrix MCP serverOne endpoint that puts your workspace inside Claude, ChatGPT and other MCP clients, with scopes you grant.
- Docs and whiteboardsA block editor with Excalidraw whiteboards inside the page, thirteen templates, version history and slides.
- CodexConnect OpenAI Codex to Atrix over MCP so it reads the issue and the spec, then updates the work as it codes.
- ClaudeUse your Atrix workspace from Claude and Claude Code over MCP, with the scopes you grant.
- PricingBuilder and Studio, compared line by line.
Stop pasting the spec into the chat.
Connect Cursor during the 7-day trial. The developers page has the same config for other clients.
7-day trial · card required · cancel anytime