Your AI Agents

Grok

Grok as an MCP client against your workspace, and where xAI does and does not appear in Surface's AI traffic and visibility numbers.

Grok comes up in two ways: as an MCP client driving your workspace, and as a reader of your website. Surface covers the first fully and the second only in part.

1. Grok Driving Your Workspace

Surface's MCP server uses the standard transport: Streamable HTTP, one URL, a Bearer token.

URL:     https://app.withsurface.com/mcp
Header:  Authorization: Bearer <your-api-key>

xAI's MCP support differs between the Grok apps, the console and the API. Use whatever MCP entry your Grok surface exposes and give it those two values. If it takes a URL, ?tools= and ?readonly=1 ride it. See Tool bundles.

If you are building against the xAI API, Surface is just an MCP server: use any MCP client library, and every tool in the tool reference is available.

Start read-only. One query parameter removes every write tool:

https://app.withsurface.com/mcp?tools=insights&readonly=1

2. Grok and Your Website

This needs no setup beyond the Surface Tag. Two limits: Surface does not score xAI, and Grok is not one of the engines the AI traffic breakdown is documented to name.

As an answer engine. AI Visibility scores your presence per model, and the four scored today are ChatGPT, Gemini, Perplexity and Claude. Grok is not one of them. The prompt set, competitor set and cited sources are shared across the models that are.

As a referrer. Traffic analytics splits AI referrals out by engine, with an average lead score attached. The engines named in those docs are ChatGPT, Perplexity, Claude and Gemini. Build an ai-referrals segment and read what actually lands in it.

Whether a Grok click-through is broken out under its own engine, folded into another bucket, or absent is not something these docs can tell you. Check the AI traffic breakdown in your own workspace, or ask your Surface contact.

Blocking AI crawlers in robots.txt is right for some businesses and wrong for most B2B ones. Check what yours does rather than inheriting it from a template.

On this page