Integrations
Connect Search Console to Grok
Grok accepts any Model Context Protocol server as a custom connector, so pointing it at AutoPSEO gives it your real numbers instead of an estimate.
Add the connector
Open the connectors page in Grok, choose a new custom connector, and enter https://app.autopseo.com/mcp as the server URL. Grok discovers the tools on connect, so the first thing worth asking is which properties the connection can see.
A persistent SEO bot
A Grok bot keeps its instructions between sessions, which is where the rules that make SEO analysis trustworthy belong: state both periods, keep facts apart from interpretation, prioritise by impact rather than by position movement, and never call a write tool without explicit intent.
Schedule around the data
Search Console settles on a two to three day lag. A weekly routine that runs on Monday for "last week" quietly drops the weekend and reports a decline every single week, so run weekly jobs mid-week and monthly jobs a few days into the month.
Terminal and API
Grok Build takes the same endpoint as an http MCP server in its config file, and the xAI API supports remote MCP tools in both the native SDK and the OpenAI-compatible Responses API.
- Approval callbacks from other vendors are not available on xAI, so gate writes with a read-only key instead
- The same key backs the REST surface at /v1 if you would rather not speak MCP
- Per-key rate limiting applies identically on every surface
Ready to see what your Search Console data is hiding?
Connect a property and every report fills in immediately. No credit card needed.