Before you start
- A DevTune project on a plan that includes API access. No account yet? Let your agent set one up.
- A Claude account. Free accounts can add one custom connector.
- On Team and Enterprise plans, an owner adds the connector for the organization before members can connect.
- 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
On your own account:- Open Customize > Connectors.
- Select + Add, then Add custom connector.
- Enter
DevTuneas the name. - Paste
https://devtune.ai/api/mcpas the server URL and select Continue. - Review the detected authentication settings and select Continue.
- Under Authentication, select Sign in now.
- Under OAuth client, keep Use Claude’s published identity (Recommended).
- Select Add, then sign in to DevTune, select the project, choose the scopes the connection may use, and approve.
- An owner opens Organization settings > Connectors, selects Add, then Custom, then Web, and follows steps 3 to 8 above.
- Each member opens Customize > Connectors, finds DevTune and selects Connect.
Connect with an API key
Use a key for scripts, scheduled runs and machines without a browser. In the connector form, under Authentication select No sign in, then under Request headers add:
On Team and Enterprise plans everyone who uses the connector shares this key, and every change acts as the member who created it. Prefer sign-in for teams.
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
In a chat, select + at the lower left, then Connectors, and switch DevTune on for the conversation. Then ask Claude:devtune_get_connection_context. If it names the wrong project, connect again and select the right one.
Measure
Ask Claude 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.- Claude 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 Claude runs DevTune tools
Claude asks before it runs a DevTune tool. Choose Allow always only for tools you are happy to run without a prompt. The connector works in Claude on the web, Claude Desktop and Cowork.Limits
- In Research, Claude runs tools without asking. Switch off the DevTune tools that change your project in the Search and tools menu before you start a Research run.
- Free accounts are limited to one custom connector.
- 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
- Claude documentation: how Anthropic 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