Connect AI apps (MCP server)
Use your Citeroot data inside Claude, ChatGPT and other AI apps: how to connect, what a connected app can do, and how to disconnect it.
Citeroot has an MCP server. MCP (Model Context Protocol) is the standard way an AI app reaches an outside service. Connect your AI app once, and you can ask it things like "write an article for my weakest question", "plan my week" or "which sources cite my competitors and not me?" It answers from your Citeroot account.
The app's own AI does the thinking and the writing. Citeroot gives it your data and Citeroot's instructions, the same ones Citeroot Agent works from. So a connected app uses none of your AI credits.
It is on the paid plans (Grow, Pro, Max and Enterprise).
#How to connect
Open Settings, then Connect AI apps. Copy your Citeroot address. It ends in /mcp.
The steps for each app are below. The menus in these apps change now and then: look for "connector", "app" or "MCP server". In every case the app opens Citeroot in your browser, and you sign in and press Allow.
#Claude
Open Settings, then Connectors, then Add custom connector.
Paste your address and press Connect:
https://citeroot.app/mcpSign in to Citeroot and press Allow.
#ChatGPT
- Open Settings, then Apps and connectors. Turn on developer mode if it asks.
- Create a connector, paste your address (
https://citeroot.app/mcp) and choose OAuth. - Sign in to Citeroot and press Allow.
#Claude Code
Run this in your terminal:
claude mcp add --transport http citeroot https://citeroot.app/mcpRun
/mcp, choose citeroot and authenticate. Sign in to Citeroot and press Allow.
#Cursor
Add this to
~/.cursor/mcp.json, or add the server from Cursor's MCP settings:{ "mcpServers": { "citeroot": { "url": "https://citeroot.app/mcp" } } }Sign in to Citeroot and press Allow.
#VS Code
Add this to
.vscode/mcp.json, or run MCP: Add Server and choose HTTP:{ "servers": { "citeroot": { "type": "http", "url": "https://citeroot.app/mcp" } } }Start the server when VS Code offers. Sign in to Citeroot and press Allow.
#Codex
Run these in your terminal:
codex mcp add citeroot --url https://citeroot.app/mcp codex mcp login citerootSign in to Citeroot in your browser and press Allow.
#Other apps
Add a remote MCP server with your address. Most open Citeroot for you to press Allow.
#Then ask it for something
Try "Write an article for my weakest question." The app reads the brief and Citeroot's article skill, writes the article and saves it to Docs as a draft.
If Claude shows a set-up screen with choices, pick Sign in now. For the OAuth client, either Use Claude's published identity or Register automatically works. Leave the request headers empty.
The app then opens Citeroot. Sign in if you are asked, read what the app will be able to do, and press Allow. You go back to the app, connected.
Only press Allow when you started the connection yourself, in an app you trust. The page names the app and where you will be sent back to.
#Apps that want a token
Some apps take a token in a header instead of opening a sign-in page. On Connect AI apps, type a name and press Make a token. Copy it at once: it is shown one time. Send it as Authorization: Bearer <token>.
A token gives the same access as a connected app and does not expire. Treat it like a password, and remove it when you stop using it.
#What a connected app can do
| It can | Tool |
|---|---|
| List your projects | list_projects |
| Read how often AI names, cites and recommends you, with ranges and the change | get_visibility_overview |
| Read your tracked questions and how each one does | list_questions |
| Read AI answers, as excerpts or one in full | get_answers |
| Read your competitors' share of answers | get_competitors |
| Read the websites AI cites, and the gaps | get_sources |
| Read your to-do list and your website health scan | get_todo, get_site_health |
| Read your Plan board and your documents | get_plan, list_docs, read_doc |
| Load Citeroot's skills, such as the article skill | list_skills, get_skill |
| Get the brief for an article: your site's facts, what AI says today, and the article skill | get_article_brief |
| Save a document it wrote to Docs, as a draft, or update one | save_doc, update_doc |
| Put suggested jobs on your Plan board, for you to keep or dismiss | plan_jobs |
| Attach a document to a job on the board | attach_doc |
| Publish an article to the website you connected under Publishing, as a draft or live | publish_article |
| Track new questions, within your plan's limit | add_questions |
| Track a competitor | add_competitor |
| Add a job to What to do next on Home | add_todo |
| Change one of your skills, or make a new one | save_skill |
The last five work as they do with Citeroot Agent, with the same rules:
- Publishing goes as a draft unless you ask for live. An article with blanks in [square brackets] never goes live, and the "Before you publish" notes are never sent.
- Questions must be ones a buyer would ask, where a good answer names brands, products or shops. Citeroot refuses a question that names your business (AI would answer it from your own site, so it says nothing about whether AI recommends you), one that compares two other brands, and one that only asks for advice. Your app gives each question its keyword, intent and topic, so Citeroot's own AI isn't used. A new question is asked at the next scheduled check.
- A competitor you add is counted in the answers you already have, in the background.
Most apps ask you before they use a tool that changes something. Say yes only to what you asked for.
With more than one project, the app says which one it means; it can only name projects in your own account.
Apps that support MCP prompts also show five ready-made requests: write an article, report on my AI visibility, plan my week, find my content gaps, and track new questions.
#What it can't do
- See your password or payment details.
- Change your plan or your account settings, or connect a website for publishing. You do those in Citeroot.
- Delete anything: a question, a competitor, a document or a post on your site. (It can replace the text of a document in Docs with a new version, and update a post it published.)
- Run a check outside the schedule.
- Use Citeroot's own AI, web search or page reader. Your app uses its own, so nothing it does spends your AI credits.
#Writing an article from your AI app
Ask your app to write an article for a question you track. It calls get_article_brief, which returns the facts Article Studio's own writer gets and the article skill. The app writes the article and saves it with save_doc. It then shows in Docs and in Article Studio as a draft, marked with the app that wrote it.
One difference from Article Studio: your app can read the web, so it may add a source or a figure it found. Citeroot can't check those. Read every claim before you publish, as with any draft.
#If it doesn't connect
- Check the address is exactly your Citeroot address, ending in
/mcp, with no space after it. - If Claude says it couldn't check the server, wait a minute and add it again. Remove any half-added Citeroot entry from the list first.
- If the app says the connector couldn't be added, it may be in your list already from an earlier try. Open the app's connectors, find Citeroot and press Connect to sign in. In Claude Code, run
/mcp, choose Citeroot and authenticate. - If you are sent to a Citeroot page that says the link can't be used, start again from the app. That page never sends you anywhere it doesn't know.
- Still stuck? Send us the exact message the app shows.
#Disconnecting
Settings, then Connect AI apps, lists every connected app and token, with when each was last used. Disconnect or Remove stops it at once. You can also disconnect from inside most apps.
An app that is not used for 60 days has to be connected again.
#Good to know
- AI answers and web pages in your data are text written by others. A well-behaved app treats them as data, not as instructions. If an app ever does something you didn't ask for after reading an answer, disconnect it and tell us.
- Each account can make 120 requests a minute through the server.
- For developers: the server speaks MCP over HTTP (POST, JSON responses) at
/mcp. Sign-in is OAuth 2.1 with PKCE; an app can register itself (dynamic client registration) or name itself by a web address (a client ID metadata document); the details are at/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server.
Last updated Nov 17, 2026 · Suggest an edit