Grok: connecting AutoPSEO through MCP

Grok reaches AutoPSEO through the same MCP server as every other assistant, at https://app.autopseo.com/mcp. Nothing Grok-specific needs installing: xAI lets you attach remote MCP servers in three places, on grok.com, in the Grok Build terminal agent and in the xAI API, and AutoPSEO works in each with the tools, permissions and plan of your account. This page gives the steps for each, and what to check when a connection fails.

Grok on the web

xAI's connector guide sets out custom connectors in three steps:

1. Go to grok.com/connectors.
2. Choose New Connector, then Custom.
3. Enter https://app.autopseo.com/mcp as the MCP server URL and complete the sign-in. AutoPSEO's sign-in and approval page opens; approve with the account that holds your properties.

xAI says connectors are open to all Grok users, and that on Business and Enterprise a team admin has to provision a connector before members can use it. Once connected, ask Grok to "list the Search Console properties on my account" to confirm it reached the right account and learned the exact property names.

Grok Build

Grok Build, xAI's terminal agent, adds a remote server with one command (xAI's MCP guide):

grok mcp add --transport http autopseo https://app.autopseo.com/mcp

The first time a tool is used, Grok Build opens the sign-in in your browser and stores the token itself. On a machine without a browser, pass an API key instead and keep it in an environment variable:

grok mcp add --transport http autopseo https://app.autopseo.com/mcp --header "Authorization: Bearer ${AUTOPSEO_API_KEY}"

Grok Build also loads servers configured for Claude Code (~/.claude.json), for Cursor (.cursor/mcp.json) and in the project's .mcp.json, so an AutoPSEO server you already added there appears without another step. In its interface, /mcps lists the servers and lets you authenticate one.

The xAI API

Agents built on the xAI API can call AutoPSEO as a remote MCP tool. xAI supports this in its native SDK and its OpenAI-compatible Responses API over Streamable HTTP, with server_url, server_label and an optional authorization value for the token (remote MCP tools). An entry in the tools array looks like this:

{
  "type": "mcp",
  "server_label": "autopseo",
  "server_url": "https://app.autopseo.com/mcp",
  "authorization": "apk_live_..."
}

xAI does not support the Responses API's require_approval parameter, so nothing pauses for approval before a tool runs. Give agents a Read only key unless they must change something: AutoPSEO refuses a read-only key for every tool that writes or spends research credits.

Which access to give Grok

Connections made by signing in appear on MCP & API under Signed-in tools, where you can sign one out, and keys are revoked on the same page. The tool groups, access classes and limits are described in MCP & ChatGPT, and the Grok connection guide has example prompts.

Troubleshooting

• Grok cannot reach the server. xAI requires a server that is reachable over the public internet, which AutoPSEO's is, so check the address: enter https://app.autopseo.com/mcp exactly, including /mcp.
• No properties appear. Ask for the whoami tool to see which AutoPSEO account the connection uses. If it is the right one, connect Search Console there first.
• A tool is refused. A read-only key cannot write or spend credits, and a team member with Read access can only read.
• HTTP 429. The limits are 60 calls a minute per key and 1,000 an hour per account.
• Subscription required. The account's trial has ended; choose a plan under Subscription & billing.

Visits that Grok sends to your site are counted in GA4's LLM Traffic report.