Use DevTune with ChatGPT

Connect ChatGPT to your DevTune project, then ask it what AI platforms say about your product, what to fix next, and whether a shipped fix moved the numbers.

Made by: OpenAI
What it is: ChatGPT on the web, with custom MCP servers as plugins.
Connect with: Sign-in
How we checked: Checked against docs

Before you start

A DevTune project on a plan that includes API access. No account yet? Let your agent set one up.
ChatGPT on the web. If you do not see Add custom MCP server, your workspace admin controls who can add one.

Connect by signing in

Open chatgpt.com/plugins.
Select the plus button, then Add custom MCP server.
Enter DevTune as the name.
Under Connection, paste https://devtune.ai/api/mcp as the Server URL.
Set the authentication to OAuth.
Review the risk warning and select I understand and want to continue.
Select Create as a plugin.
Install the plugin. When ChatGPT asks, sign in to DevTune, select the project, choose the scopes the connection may use, and approve.

The connection reaches the project you select, with your own DevTune permissions.

Check the connection

In a chat, type @ in the prompt box and select the DevTune plugin.

Then ask ChatGPT:

Which DevTune project are you connected to?

It answers with your project's name, read with devtune_get_connection_context. If it names the wrong project, connect again and select the right one.

Measure

Ask ChatGPT what AI platforms say and what AI systems fetch from your site:

What is our share of voice across AI platforms over the last 30 days, and how has it changed?

Which pages and domains do AI platforms cite for our topics, and which competitors get cited where we are not?

What are AI systems fetching from our site, and which pages do they ask for that do not exist?

ChatGPT answers from 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:

List the top five actions DevTune suggests for this project, with the evidence behind each.

Accept the first action, generate its brief and show me the brief.

Mark that action live. The page is published at https://example.com/your-page.

devtune_get_actions lists the queue with its evidence.
devtune_change_action_status accepts an action, and devtune_generate_action_brief writes its brief. Generating a brief spends credits.
ChatGPT 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_status with mark_live and the published URL starts the before/after measurement.

Prove

Which of our shipped actions have results, and what moved?

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 ChatGPT runs DevTune tools

ChatGPT asks you to confirm each DevTune tool that changes something. You can expand a tool call to read exactly what it will send before you approve, and ChatGPT can remember your choice for a tool for the rest of that conversation. A new conversation asks again.

In the ChatGPT desktop app, install the DevTune plugin through Codex instead. See Use DevTune with Codex.

Limits

ChatGPT offers sign-in or no authentication for a custom server, so a DevTune API key cannot be used here.
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

Symptom	What to do
ChatGPT lists no DevTune tools	Check the connection as described above. With an API key, confirm the key is active under API Keys and has not expired.
A tool is missing, or a call is refused with `403`	The connection lacks that tool's scope, or the plan lacks the feature. Ask the agent which scopes the connection has, then edit the key or sign in again with the scope selected.
Changes are refused but reads work	The connection has read scopes only, or the project is paused. Add the scope to the key or sign in again with it selected; resume a paused project in DevTune.
A figure comes back empty or as `Unmeasured`	DevTune has no measurement for that window. Report it as unmeasured, not as zero.

Next steps

ChatGPT documentation: how OpenAI 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

Make AI describe you the way you'd describe yourself.

No card required

All integrations