MCP server
AutomatedSEO is AI-native: everything it does is also there for the assistant you already use. Its MCP server lets Claude, ChatGPT and the coding agents you work in read your SEO data and, when you allow it, plan, edit and publish content, all within your workspace's approval rules. Ask about your site's technical health, search performance, keyword gaps and content calendar in plain language, then turn the answer into work: a site check, a growth plan, an article plan or a scheduled post.
Coding agents go a step further. Claude Code, Codex, Cursor, VS Code, Gemini CLI, Muse Code and Devin Desktop can fix the issues AutomatedSEO finds in your codebase, and build the endpoint that lets a custom site publish your articles.
https://automatedseo.app/api/mcpAdd this URL to your assistant, then sign in and choose a workspace when it asks. You only need an access token if your app can't sign in. Every connection belongs to one workspace and can only see the websites in it. Pick your assistant to get set up:
Using something else? Any client that connects to remote MCP servers over Streamable HTTP with OAuth works too. See Other MCP clients.
Before you start
- An AutomatedSEO account with a workspace and at least one website. Create one if you don't have it yet.
- Search performance needs Google Search Console connected, and publishing needs a connected CMS. Every other tool works without them.
- What you can do through the assistant is limited by your role in the workspace, the same as in the app.
Connect Claude
Add the connector once on the web or in the desktop app, and it works in Claude on mobile too. Every plan can add one, including Free, which allows one custom connector.
- 1In Claude, open Customize, then Connectors. Select Add, then Add custom connector.
- 2Name it AutomatedSEO, paste the server URL
https://automatedseo.app/api/mcpand select Continue. - 3Under OAuth client, choose Register automatically, then select Add.
- 4Select Connect. Sign in to AutomatedSEO, choose the workspace the connector may use, and approve the permissions it asks for.
- 5In a chat, turn the connector on from the + menu under Connectors, and ask a question about your site.
Claude runs read tools straight away and asks you before it runs a tool that publishes or rolls back content.
Connect ChatGPT
Install AutomatedSEO from the plugin directory, or add the server yourself on ChatGPT on the web. Adding your own server with every tool works on Business, Enterprise and Edu plans, where an admin may need to allow it. Pro can add it with read tools only.
- 1Open Plugins. Find AutomatedSEO and select Install plugin, or select +, then Add custom MCP server.
- 2For a custom server, name it AutomatedSEO, paste the server URL
https://automatedseo.app/api/mcpunder Connection and choose OAuth. Accept the warning and select Create as a plugin. - 3Select Connect, sign in to AutomatedSEO, choose a workspace and approve the permissions.
- 4In a chat, type
@and pick AutomatedSEO, or mention it in your message.
Connect Grok Bot
Works in the Grok Bot apps for desktop, iOS and Android. Once one Bot has AutomatedSEO, every Bot on your account can use it.
- 1Open Connect apps: in the sidebar on desktop, or from your avatar on mobile. Add a server by URL and paste
https://automatedseo.app/api/mcp. Or ask any Bot to “add the MCP server https://automatedseo.app/api/mcp”. - 2Select Authorize, sign in to AutomatedSEO, choose a workspace and approve the permissions.
- 3Ask a Bot about your site.
Connect Claude Code
Add the server from your terminal:
claude mcp add --transport http automatedseo https://automatedseo.app/api/mcpThen run /mcp inside Claude Code, choose automatedseo and sign in. Your browser opens the AutomatedSEO sign-in and workspace picker, then returns you to the terminal.
The server is added to the current project. Add --scope user to use it in every project, or --scope project to share it with your team through the repository's .mcp.json. Everyone still signs in with their own account.
Connect Codex
Codex runs in the ChatGPT desktop app, the Codex CLI and the IDE extension. ChatGPT and Codex share one plugin directory, so if you've added AutomatedSEO in ChatGPT, Codex already has it. Otherwise:
- 1Open the Plugins tab in the ChatGPT desktop app, or enter
/pluginsin the Codex CLI. - 2Find AutomatedSEO and install it, then sign in, choose a workspace and approve the permissions.
- 3Start a new session and ask about your site.
The IDE extension doesn't support plugins, so add the server directly. The CLI and IDE extension share this configuration:
codex mcp add automatedseo --url https://automatedseo.app/api/mcpCodex opens the AutomatedSEO sign-in and workspace picker in your browser. If it doesn't, run codex mcp login automatedseo. Run /mcp inside Codex to see the server and its tools.
Running Codex where a browser can't open, such as in CI? Create an access token (see Other MCP clients) and pass it through an environment variable instead:
codex mcp add automatedseo --url https://automatedseo.app/api/mcp \
--bearer-token-env-var AUTOMATEDSEO_TOKENConnect Cursor
- 1Add AutomatedSEO to Cursor and select Install. Or add it yourself to
.cursor/mcp.jsonin your project, or~/.cursor/mcp.jsonfor every project. - 2In Cursor Settings, find
automatedseoin the MCP list and select its sign-in button. - 3Sign in to AutomatedSEO in your browser, choose a workspace and approve the permissions.
{
"mcpServers": {
"automatedseo": { "url": "https://automatedseo.app/api/mcp" }
}
}Connect VS Code
Works in agent mode with GitHub Copilot. Add AutomatedSEO to VS Code, or run:
code --add-mcp '{"name":"automatedseo","type":"http","url":"https://automatedseo.app/api/mcp"}'VS Code asks you to sign in the first time the server starts. Allow it, then sign in to AutomatedSEO and choose a workspace in your browser. Run MCP: List Servers from the Command Palette to start, stop or sign in again. In Copilot Chat, switch to Agent and ask about your site.
Connect Gemini CLI
Add the server from your terminal:
gemini mcp add --transport http automatedseo https://automatedseo.app/api/mcpThen run /mcp auth automatedseo inside Gemini CLI. Your browser opens the AutomatedSEO sign-in and workspace picker, then returns you to the terminal. Add --scope user to use it in every project.
Connect Muse Code
Meta's coding agent reads MCP servers from ~/.config/muse/settings.json. Add AutomatedSEO to its mcp_servers block:
{
"mcp_servers": {
"automatedseo": {
"transport": "streamable_http",
"url": "https://automatedseo.app/api/mcp"
}
}
}Then sign in from your terminal:
muse mcp login automatedseoChoose a workspace in your browser, then start a new session. Muse Code loads servers when a session starts.
Connect Devin Desktop
Devin Desktop is what Windsurf is now called. Open ~/.config/devin/mcp_config.json (on Windows, %APPDATA%\devin\mcp_config.json), or create it, and add the server:
{
"mcpServers": {
"automatedseo": { "serverUrl": "https://automatedseo.app/api/mcp" }
}
}Refresh the server list in Devin Desktop's MCP settings, then sign in to AutomatedSEO and choose a workspace when your browser opens. On Enterprise plans, an admin may need to turn MCP on first.
Other MCP clients
MCP Inspector and any other client that supports remote MCP servers over Streamable HTTP can connect with the same URL and sign in through OAuth.
If a client can't sign in, use a personal access token instead. In AutomatedSEO, open Integrations, find AI assistants at the bottom and select App doesn't support sign-in? Use an access token. Choose Read only or Read and act and how long it lasts, then select Create token. Copy the config shown with the token, which already includes it, into your client's MCP settings. It looks like this:
{
"mcpServers": {
"automatedseo": {
"url": "https://automatedseo.app/api/mcp",
"headers": { "Authorization": "Bearer aseo_pat_..." }
}
}
}Things to try
Ask in your own words. These show what you can get done, which tools the assistant reaches for, and what comes back.
In any assistant
Claude, ChatGPT and every other client can do these. The assistant brings its own skills too, so it can draw a chart or write a summary from what AutomatedSEO returns.
A Monday briefing
Give me my Monday SEO briefing: how search did last week, what went live, what's due this week and anything broken.
Clicks, impressions and anomalies from Search Console, the articles that published and the ones due next, and the pages with open issues, in one reply.
list_websitesget_search_performanceget_content_calendarget_site_healthTraffic, charted
Chart our daily clicks since we connected Search Console, and mark the days our buying guides went live.
A chart the assistant draws in the conversation from your Search Console data, with publish dates marked, so you can see which articles moved traffic.
get_search_performancelist_articlesPage two to page one
Which keywords do we rank 11 to 20 for? Plan articles for the three with the most searches.
The keywords you're closest to winning, from measured rankings and search volume, and an article plan for each, waiting for your approval before research starts.
get_keyword_opportunitiescreate_article_planYour competitors' keywords
Which keywords should we write about next? Prefer ones competitors rank for and we don't.
A shortlist built from measured search volume and difficulty, with the competitor gaps marked.
get_keyword_opportunitiesA brief before a launch
Our trail range launches on the 14th. Make sure next week's articles mention it, and move “Trail vs road shoes” to launch day.
Instructions on each upcoming article that hasn't been written yet, and the post moved to the launch date if that day is free.
get_content_calendarset_article_instructionsreschedule_articleEdits in plain words
Stop using the word “unlock” in our articles, and make the meta description of my latest draft shorter.
“unlock” joins the phrases every new article avoids, and the draft gets a tighter meta description. Nothing publishes until you approve it.
get_content_settingsupdate_content_settingslist_articlesget_articleupdate_articlePublishing, checked first
Is my latest approved article ready to publish? If it is, schedule it on WordPress for Monday at 9am.
The assistant checks readiness and the connected CMS first, then asks you to confirm before it schedules the post.
list_articlespreview_article_publicationpublish_articleA prospect, researched
I'm pitching acme-plumbing.com tomorrow. How strong is their site, do they rank for “emergency plumber chicago”, and what's broken on their homepage?
Their domain rating and backlink profile, where they rank and who outranks them, and the homepage's failing checks, ready for the call.
analyze_domaincheck_rankingsaudit_page
In a coding agent
Coding agents can do everything above, and work on your codebase as well.
SEO fixes in your code
Fix the pages AutomatedSEO flagged in this codebase, then run a fresh site check.
The agent reviews prioritized findings and repeated page patterns, locates the relevant code in this repository, makes the fixes, and queues a new crawl to confirm them.
get_site_healthrun_site_checkAn audit before you ship
Audit the preview deployment of our new pricing page, with Core Web Vitals, and fix whatever fails before we merge.
A technical audit of the public preview URL, and the fixes made on your branch while the change is still open.
audit_pageA custom site that publishes
Connect this codebase's blog to AutomatedSEO so new articles publish here.
Your coding agent adds a publishing endpoint to the site, deploys it, and connects it. AutomatedSEO tests the endpoint before saving it.
list_websitesget_webhook_setupconnect_custom_webhook
Tools
Assistants pick these for you; you don't need to name them. Every tool works on one website in the connected workspace, except the ranking, domain and page checks, which work on any site and come from a weekly allowance.
Read tools (20)
These only read data and never change anything.
| Tool | What it does |
|---|---|
list_websites | Lists the workspace and websites you connected. Assistants call it first to find the IDs every other tool needs. |
get_site_overview | Plan, last crawl, page and article counts, and whether Search Console and a CMS are connected, with a link to fix either. |
get_site_health | A compact, prioritized page of findings from the latest saved crawl, with scores and the number of discovered pages actually checked. Use limit and offset to read more findings. |
list_articles | Article plans and drafts, optionally filtered by editorial status. |
get_article | One article's plan, brief, research sources and publication history. |
get_content_calendar | Scheduled and recently updated articles for a date range (the next 90 days by default). |
get_keyword_opportunities | Measured keyword ideas, competitor gaps and keywords you already rank for. |
get_search_performance | Google Search Console clicks, impressions, CTR and position by day, query and page, plus open anomalies. Compare with the period before to see what's rising or declining (the last 28 synced days by default). |
get_internal_link_opportunities | Articles that mention another article's keyword without linking to it, with the sentence and anchor text, plus published articles nothing links to. |
get_backlinks | Backlink placements pointing at your site and whether each is verified. |
get_backlink_exchange | Your backlink exchange credits, and the links your site has given and received. |
get_ai_citations | The buyer questions you track, and whether ChatGPT, Claude, Perplexity and Gemini cite you, mention you or leave you out of each answer. |
get_autopilot_settings | How much the autopilot may do on its own, its weekly and spend limits, and any publishing pause. |
get_content_settings | The voice, preferred terms, phrases to avoid, audiences, competitors, topics and writing style every new article follows. |
get_job_status | Progress and errors from background work, with both the legacy result string and a parsed structured result when available. |
preview_article_publication | Whether an article is ready to publish, where it can go, and where it has gone before. Changes nothing. |
check_rankings | Where any domain ranks in Google's top 50 for a keyword, in one of 31 countries. Each website in your workspace adds 50 fresh checks a week. |
analyze_domain | Domain rating for any site, a prospect's or a competitor's, with its backlink profile if you ask. 100 ratings and 25 backlink profiles a week for each website. |
audit_page | A technical SEO audit of any public page, with Core Web Vitals if you ask. 100 audits and 50 speed tests a week for each website. |
get_webhook_setup | Everything a coding agent needs to publish your articles into a custom-built site: a setup brief, the exact payload, and any webhooks already connected. |
Action tools (15)
These start work or change your website, so they need a connection with write permission.
| Tool | What it does |
|---|---|
run_site_check | Starts a fresh technical crawl of the website. It reads your site and doesn't change it. |
generate_growth_plan | Starts an evidence-led growth plan for a period. It plans work and publishes nothing. |
research_keywords | Measures up to 30 keywords your assistant suggests: live search volume, difficulty and intent, and which ones an article already covers. Uses your daily research allowance. |
add_ai_question | Tracks a buyer question in your AI citation checks. |
remove_ai_question | Stops tracking a buyer question. Its history stays, and you can add it back. |
run_ai_citation_check | Starts this week's AI citation check on all four assistants. Once a week per website, on an active plan. |
create_article_plan | Adds an article plan for a target query. Research starts once someone approves it in AutomatedSEO, and it publishes nothing. |
update_article | Edits an article's title, meta description, slug, excerpt or body. Editing an approved or live article sends it back for your approval. |
set_article_instructions | Tells the writer what an upcoming article should cover or avoid, before it's written. |
reschedule_article | Moves a planned article to a free day in the content calendar, before it starts being written. |
remove_scheduled_article | Takes an unpublished article off the calendar and puts its keyword back in the queue. |
update_content_settings | Changes the voice, terms, phrases to avoid, audiences, competitors, topics or writing style new articles follow. Business facts and claims stay in the app. |
connect_custom_webhook | Connects the endpoint your coding agent built. AutomatedSEO sends it a test first and saves nothing unless it passes. |
publish_article | Publishes an approved article to a connected CMS, now or at a set time. It can't approve an article for you. |
rollback_cms_change | Reverts a change AutomatedSEO made in your CMS, after checking it's still the version that was applied. |
Permissions and safety
- When you connect, you pick one workspace. The connection can't see or change any other workspace, even ones you belong to.
- A new connection gets read permissions. Action tools also need write permissions, which you approve when your client asks for them; until then the tool says which permission is missing. A Read only token never gets them.
- Your role is checked on every call. If someone is removed from a workspace, their connections stop working immediately.
- Each publish needs a unique request key, so a retried request never publishes twice. Rolling back a CMS change checks it's still the version that was applied.
- Site checks, growth plans and article research run in the background. Ask the assistant to check on them later.
- Each person can make up to 120 calls a minute, and list results are capped at 100 rows.
- Every call is recorded in your workspace's activity log with the tool, website and outcome. We never store chat transcripts. See MCP connections in our privacy policy.
Disconnecting
- Remove the connector or plugin in Claude, ChatGPT or your client's settings to stop it calling AutomatedSEO.
- In a terminal, run
claude mcp remove automatedseo,codex mcp remove automatedseoorgemini mcp remove automatedseo, or remove the entry from your editor's MCP config file. - Revoke personal access tokens in Integrations under AI assistants. A revoked token stops working on its next call.
- To switch workspaces, disconnect and connect again, then pick the other workspace.
Troubleshooting
| Error or symptom | What to do |
|---|---|
| Couldn't reach the MCP server | Check the URL is exactly https://automatedseo.app/api/mcp, with no trailing slash or extra path. |
| Bound to a different workspace | The assistant asked about a workspace you didn't connect. Ask it to call list_websites first, or reconnect and pick the other workspace. |
| Codex lists the server but can't use it | Sign in with codex mcp login automatedseo, then try again. |
| The token does not grant a permission | You connected with read access. Approve the extra permission when your client asks, or create a Read and act token. |
| Rate limit exceeded | Wait a minute and try again. |
| No data in a result | The site may not have been crawled or connected to Search Console yet. Ask the assistant to run a site check, or connect Search Console in the app. |
Still stuck? Email hello@automatedseo.app with the assistant you used and the error you saw. Please don't send tokens or passwords.
Further reading
- What you can do with it: Example conversations, every capability and how it stays within your rules.
- Integrations: Connect Search Console and the CMS you publish to.
- MCP connections: What we record about assistant calls, and what we never store.
- Support: Answers to common questions and how to reach us.