Connect ToolRouter to Grok Bot

Written by Sol Wright, last update:

Grok Bot can use connectors and MCP servers where they are available. ToolRouter gives a compatible Bot one connection to hundreds of specialist tools for research, SEO, leads, images, video and live data.

Current ToolRouter status

ToolRouter is not in the Grok Bot marketplace. We have not completed an end to end ToolRouter acceptance test in a signed-in Grok Bot account. The custom MCP option can vary by account and app release, so use the steps below and confirm setup with one real tool call.

xAI documents that Grok Bot uses plugins and MCP servers, that Grok Bot follows Cursor team MCP policy, and that MCP authentication is shared across Cursor and Grok Bot. The exact individual install surface can vary by account and rollout.

Set up the shared connection

  1. Add ToolRouter to Cursor under Settings > MCP with URL https://api.toolrouter.com/mcp and complete ToolRouter OAuth.
  2. Open Grok Bot Settings > Plugins > Yours.
  3. If ToolRouter appears, enable it for the current Bot.
  4. For a team account, ask an admin to allow https://api.toolrouter.com/mcp under Cursor Team Settings > MCP Configuration and enable the server for the team.
  5. Restart Grok Bot after a policy change.

If ToolRouter does not appear, the current account or app release has not exposed the shared custom server. Use the verified Grok chat connector, Grok Build command, or xAI API setup instead.

Verify the setup

Do not stop at an installed label. In Grok Bot, ask:

Use ToolRouter to discover a free tool that checks a public website, run it on https://example.com, and return the result.

The setup is confirmed only when all of these are true:

  • ToolRouter appears for the Bot
  • OAuth completes or the existing shared authentication is recognized
  • discover returns a catalog result
  • use_tool completes a real free call
  • The result appears in the Grok Bot conversation

What one connection means

ToolRouter remains one remote MCP server even though it searches hundreds of specialist tools. The Bot starts with the compact discover and use_tool gateway instead of loading a separate connection for every provider.

Team controls

Grok Bot follows the team MCP allowlist and denylist from Cursor. A team can block member added servers, require a network allowlist and disable MCP commands globally. An admin gate is a real deployment requirement, not a ToolRouter error.

Sources: xAI Grok Bot for teams and enterprises, xAI Grok Bot settings, last checked 30 August 2026.