Add ScoutRival to Grok.

Grok connects to ScoutRival two ways — through its connectors on grok.com, or with the Grok command-line tool. Both give it the same ScoutRival tools.

3 min read MCP Updated Jul 2026

Grok, from xAI, can use custom MCP servers in two places — the connectors on grok.com and the Grok command-line tool. Both give it the same ScoutRival tools: your brief, your competitors, your AI-visibility, and content. Pick whichever you already use.

// GROK'S CONNECTOR UI IS NEW AND SHIFTS OFTEN

Grok's connector settings are newer than most clients' and the exact screens change between releases. If the steps below look different from what you see, the concept still holds: add a custom MCP server at https://user.scoutrival.com/api/mcp and authenticate with either a sign-in or a bearer token.

On grok.com

Open the connectors settings

On grok.com, go to your settings and find Connectors (sometimes shown as integrations or tools). The exact location and whether custom servers are available depend on Grok's current rollout and your plan.

Add a custom MCP server

Choose the option to add a custom MCP server or connector, and point it at https://user.scoutrival.com/api/mcp.

Authenticate

If Grok offers a sign-in or OAuth option, use it and approve the connection in ScoutRival — no token to copy. If it asks for a header or token instead, paste Bearer sr_mcp_YOUR_TOKEN, using a token you made at Settings → MCP.

In the Grok CLI

The Grok command-line tool reads its MCP servers from a config file. Make a token first, then add ScoutRival as a remote, streamable-HTTP server.

Create a Read-only token

In ScoutRival, open Settings → MCP and create a token. Leave the access level on Read-only to start — it can read your data but spends no credits. The token is shown once, so copy it now. See access tokens.

Add ScoutRival to the config

Add an mcpServers entry with the endpoint URL and an Authorization header carrying your token:

mcpServers config{
  "mcpServers": {
    "scoutrival": {
      "url": "https://user.scoutrival.com/api/mcp",
      "headers": { "Authorization": "Bearer sr_mcp_YOUR_TOKEN" }
    }
  }
}

The exact config file name and field the CLI expects are in Grok's own command-line documentation, but the values are the same everywhere: this URL plus a bearer token. Replace sr_mcp_YOUR_TOKEN with your real token.

Check it worked

Once the connection is added, Grok should list ScoutRival's tools. Ask it a question that uses them to confirm — for example, "List my ScoutRival brands." If it answers with your real data, you're connected. If no ScoutRival tools appear, reconnect or restart Grok so it re-reads the tool list; clients sometimes cache the old list. More fixes are in troubleshooting.

What to ask

"List my ScoutRival brands."
"Give me today's brief for <your brand>."
"How visible am I in AI answers?"

Reading your data is free. Generating content and running checks spend credits and need a token with the Content or Full access level — see scopes and access levels.

Still stuck?

Contact support