Before you start
- A DevTune project on a plan that includes API access. No account yet? Let your agent set one up.
- For the API key route: a project API key from API Keys in the account sidebar. DevTune shows the key once, so copy it when you create it.
Connect by signing in
Add the server to.cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it everywhere:
- In the editor: open Customize in the sidebar, find devtune and switch it on. Sign in to DevTune when Cursor opens the browser.
- In the command-line agent: run
agent mcp login devtune.
Connect with an API key
Use a key for scripts, scheduled runs and machines without a browser. SetDEVTUNE_API_KEY in your shell profile or system environment, then add a header that names it:
agent mcp enable devtune.
Some builds of the command-line agent do not read ${env:DEVTUNE_API_KEY} and ask you to sign in instead. If that happens, put the key itself in ~/.cursor/mcp.json, never in a project file you commit.
A key reaches the one project it was created for, with the scopes you gave it. A change made with a key acts as the member who created it.
Check the connection
Runagent mcp list. A working connection shows devtune: ready. agent mcp list-tools devtune lists the DevTune tools. In the editor, Customize shows the server and its tools.
Then ask Cursor:
devtune_get_connection_context. If it names the wrong project, connect again and select the right one.
Measure
Ask Cursor what AI platforms say and what AI systems fetch from your site:devtune_get_visibility_summary, devtune_get_visibility_diff, devtune_get_competitive_position, devtune_get_top_citation_pages, devtune_get_content_gaps, devtune_get_traffic_summary and devtune_get_404_demand. Measurement windows are 30 or 90 days.
Fix
Ask for the ranked fixes, then work one through:devtune_get_actionslists the queue with its evidence.devtune_change_action_statusaccepts an action, anddevtune_generate_action_briefwrites its brief. Generating a brief spends credits.- Cursor reads the brief with
devtune_get_action_brief. Writing and publishing the page is your work and the agent’s, in your own repository or content system. DevTune drafts and never publishes. devtune_change_action_statuswithmark_liveand the published URL starts the before/after measurement.
Prove
devtune_get_outcomes_ledger returns each measured action as improved, mixed, no clear change, declined, still measuring or unmeasured. Results show what moved after a fix shipped, not what caused it. Results windows are 7, 30, 90 or 365 days.
What needs your approval
- Reading never changes your project or spends credits.
- Accepting an action, changing prompts or competitors, and every other change acts as you. Have the agent say what it will change before it does.
- Briefs, drafts, managed-agent runs, Agent Picks tests and prompt-set analysis spend credits. Approve the spend before the agent starts one.
- DevTune steers suggestions around locked pages and says when it did.
How Cursor runs DevTune tools
Cursor uses DevTune tools on its own when a request calls for them, and asks for approval before each tool by default.Limits
- Remote servers cannot load an
envFile. Set the variable in your shell profile or system environment. - A connection reaches one project. Connect again, or use another key, for a second project.
- Tools your connection has no scope for do not appear in the agent. A connection never gains scopes added later. Edit the key, or disconnect and sign in again.
If something goes wrong
Next steps
- Cursor documentation: how Anysphere documents connecting outside tools
- MCP server: every tool, its inputs and its scope
- Code mode: two tools in place of the full list, for agents short on context
- API authentication: keys and scopes
- Use DevTune with your agent: setup guides for other agents