MCP & ChatGPT app

AutoPSEO runs one MCP (Model Context Protocol) server at https://app.autopseo.com/mcp. Any assistant that speaks MCP over HTTP can connect, either by signing in to your AutoPSEO account or with an apk_live_ API key, and then works with the same properties, permissions and plan as you. The server registers 72 tools in three groups: Search Console and GA4 reports, research data, and the content engine, through which your own AI can write articles for your site.

Connect by signing in

Tools that support MCP sign-in need no key. Add the address, sign in to AutoPSEO when the tool asks and approve; the tool then keeps and renews its own access.

• Claude Code: run claude mcp add --transport http autopseo https://app.autopseo.com/mcp, then type /mcp, pick autopseo and choose Authenticate.
• Claude on the web or desktop: Settings → Connectors → Add custom connector, paste https://app.autopseo.com/mcp, then Connect and sign in.
• Cursor: add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then use the Connect button Cursor shows beside it.

{ "mcpServers": { "autopseo": { "url": "https://app.autopseo.com/mcp" } } }

Each tool connected this way appears under Signed-in tools on the MCP & API page, where Sign out cuts it off at once. A good first request is "List the Search Console properties on my account": the answer proves the connection works and gives the assistant the exact property names the other tools expect.

ChatGPT

ChatGPT connects through its developer mode, and the MCP & API page walks through it under ChatGPT app. In short: in ChatGPT, open Settings → Apps & Connectors → Advanced settings and enable Developer mode (the app lists ChatGPT Plus, Pro, Business, Enterprise and Edu), choose Create, name the connector, set the MCP server URL to https://app.autopseo.com/mcp and the authentication to OAuth, and sign in to AutoPSEO when ChatGPT asks. ChatGPT's connectors offer only OAuth or no authentication, so API keys do not work there. There is more on the ChatGPT page.

Connect with an API key

Keys are for scripts, scheduled jobs and machines without a browser. On MCP & API → API keys, name the key and choose its scope:

• Read only: query data and run reports; cannot add, change or delete anything.
• Read & write: everything a read key does, plus tools that change data or spend research credits.

The full key, apk_live_ followed by 32 hex characters, is shown once; AutoPSEO stores only its SHA-256 hash. The key list shows when each key was created, when it was last used and how many requests it made, and Revoke stops a key immediately. You can hold up to 25 active keys. Send the key as Authorization: Bearer apk_live_... (an x-api-key header works too):

claude mcp add --transport http autopseo https://app.autopseo.com/mcp --header "Authorization: Bearer apk_live_..."

The page also has snippets for the OpenAI Responses API, raw JSON-RPC with curl (the server uses the Streamable HTTP transport), and the REST API at https://app.autopseo.com/v1, which offers the 19 Search Console and GA4 tools with the same keys and an OpenAPI 3.1 document at /v1/openapi.json.

The tools

The MCP & API page always lists the current tool names; when this page was written there were 72.

Search Console and GA4 (19 tools)

list_properties, search_analytics, top_queries, top_pages, top_countries, compare_periods, content_decay, cannibalization, ctr_benchmark, page_poaching, rank_changes, new_lost_rankings, url_inspection, sitemaps, annotations, create_annotation, ga4_overview, ga4_breakdown and ga4_key_events. They cost no credits. Given no dates, they cover the last 28 settled days against the 28 before, and anyone can try them on the demo property sc-domain:demo.autopseo.app. Despite its name, content_decay belongs in this group: it finds pages that are losing clicks.

Research (33 tools)

• Account and projects: whoami, create_project, get_project_context, update_project_context
• Keywords: research_keywords, get_keyword_metrics, get_ranked_keywords, get_domain_keyword_suggestions, save_keywords, list_saved_keywords
• Domains, results pages and links: get_domain_overview, get_serp_results, find_serp_competitors, get_backlinks_overview, get_backlinks_profile
• Rank tracking: create_rank_tracker, get_rank_tracker, add_rank_tracking_keywords, remove_rank_tracking_keywords, estimate_rank_tracker_cost, run_rank_tracker
• Local search: search_local_businesses, get_local_serp_results, get_local_rank_grid, get_business_profile, get_business_reviews, get_business_updates, get_google_business_questions, list_business_categories
• Site audits: run_site_audit, get_audit_status, get_audit_issues, get_audit_pages

Many of these buy data from DataForSEO and draw on your research credits, so keep requests focused and check before large batches.

Content engine (20 tools)

These let your own AI work through the same queue as AutoPSEO's writer: content_list_tasks, content_claim, content_get_brief, content_submit, content_publish, content_unpublish, content_get_page, content_report, content_find_pages, content_add_topics, content_decline, content_merge, content_cover, content_set_cover, content_get_translation, content_submit_translation, content_instructions, content_propose_value, content_submit_value and content_remove_path. The server also offers five prompts: write-articles, optimize-page, revise-draft, connect-repo and refresh-decayed.

A typical session lists the tasks, claims one (a claim holds it for two hours), reads the brief, writes, submits and fixes whatever the checks send back, and publishes only when you say so. Cover images and translations have tools of their own. Articles written this way pass the same checks as AutoPSEO's own and use none of your article quota, although the first call for a brief reads the live search results on research credits. The whole flow is in Writing with your own AI.

Read, write and paid tools

Each tool has an access class. Read tools only look (33 of them), write tools change your workspace (22), and paid tools only read but buy research data (17). A read-only key can call read tools only. A team member with Read access can also call read tools only, whichever key or sign-in they use, and every member reaches only the properties their invitation named (Sharing & team access).

Limits and errors

Calls are capped at 60 a minute per key and 1,000 an hour per account, across all of its keys. Over either limit the server answers HTTP 429 with a Retry-After header, and most clients wait and retry by themselves; the initialize and ping handshakes do not count. Once a trial ends without a subscription, tools answer "subscription required". An assistant's provider receives your data only for the requests you make; sign a tool out or revoke its key to stop it. More examples are on the Search Console MCP page.