Skip to main content
Connect Grok Bot so you can list flows, run them, debug runs, and search Autosana docs from a Grok Bot chat. Grok Bot has no Settings form for a custom MCP URL. Autosana is not in the Grok Bot marketplace. You add it in chat as a custom MCP and sign in with your Autosana account. No API key is needed. That connector stays on your account — it is not a marketplace listing.

​
Setup

  1. In a Grok Bot chat, send:
  1. Approve the confirm card when Grok Bot asks to add the connector
  2. When Grok Bot shows a sign-in link, open it, sign in to Autosana, and click Approve
  3. In the next message, @ Autosana and ask it to list or run a flow — you can do everything from chat
You can also copy the chat line from Settings → Integrations → Grok Bot. Grok Bot uses your active Autosana workspace. Switching workspaces updates its access without reconnecting. The same connector is available to your other agents on this account. It may show up as user-autosana.
Connected Grok Bot with an API key before? Remove that connector, then add Autosana again with the line above. Revoke the old key (named mcp-grok-bot-…) in Settings → API Keys, since it is still in your chat history. Do not paste an x-api-key header.
Do not look for an “add custom MCP” screen under Grok Bot Settings (General, Computer, Usage, Updates). Plugins is the marketplace for packaged apps, not a paste-URL form. Listing under Plugins → Yours can be flaky — if the chat says the server is connected, you are done.
This is Grok Bot, not Grok chat on grok.com and not Grok Build (grok mcp add). Adding Autosana in Cursor (mcp.json) does not install it in Grok Bot.
See MCP Server for the tools Grok Bot can call after you connect.