Context Repo DocsGrok Bot
Connect Grok Bot to your Context Repo workspace through the dedicated MCP endpoint and hosted OAuth sign-in. No API key or client secret is required.
Connect Grok Bot to Context Repo to search, read, create, and organize your prompts, documents, and collections from a Bot conversation. Setup takes about a minute once the Grok Bot app is installed.
This guide is for the Grok Bot desktop and iOS app, not Grok chat on grok.com. For grok.com, use the Grok integration.
Grok Bot does not have a Plugins form for custom MCP servers. You add Context Repo from a Bot conversation.
Connect Context Repo
Ask Grok Bot to add the server
Open a Bot conversation and send:
Add this MCP server: https://contextrepo.com/grok-mcp
If Grok Bot asks you to confirm a name, use Context Repo.
Use /grok-mcp, not the standard /mcp endpoint. This dedicated endpoint starts the OAuth flow Grok Bot needs. You don't need to paste an API key, OAuth client ID, or client secret into Grok Bot.
Complete authorization
When Grok Bot checks the server, it opens the Context Repo sign-in flow in your browser. Sign in with your Context Repo account and approve access.
Verify the connection
In a new message, type @ to attach the Context Repo connector, then ask:
List my Context Repo collections.
Grok Bot should return the collections from the same workspace you see in the Context Repo dashboard. Installed connectors are account-wide, so every Bot on your account can use Context Repo after you connect it once.
What You Can Do
Grok Bot receives the full hosted MCP tool set: 27 Context Repo tools plus the search and fetch retrieval aliases. You can ask Grok Bot to:
- Find context across your prompts, documents, and collections.
- Read documents progressively with Deep Search when a document is too large to load at once.
- Create and update content without leaving the conversation.
- Organize your workspace by creating collections and adding or removing items.
- Review version history and restore earlier prompt or document versions.
- Answer questions with citations drawn from your stored documents.
See the MCP Tools Reference for every available tool.
How Sign-In Works
The Grok Bot connector uses Context Repo's hosted OAuth flow. Grok Bot discovers the sign-in requirements from the dedicated endpoint, opens Context Repo authorization in your browser, and stores the resulting connection after you approve it.
No Context Repo API key is involved. You also don't need to copy credentials from Clerk or another OAuth dashboard into Grok Bot.
Troubleshooting
There is no Add button in Settings → Plugins
That screen lists marketplace plugins and private skills. Custom MCP servers are added from chat, not from that form. Send Add this MCP server: https://contextrepo.com/grok-mcp in a Bot conversation.
The sign-in window doesn't open
Check that the URL is exactly https://contextrepo.com/grok-mcp. If you previously added https://contextrepo.com/mcp, remove that connector and add the dedicated Grok URL instead.
Grok Bot reports an authentication error
Ask Grok Bot to remove the Context Repo connector, then add https://contextrepo.com/grok-mcp again. Complete the Context Repo sign-in flow without closing the authorization window. Sign in with the account that owns the workspace you want Grok Bot to access.
Grok Bot can't find your content
Open the Context Repo dashboard and confirm the content exists in the account you authorized. Then start a new Bot conversation, type @ to attach Context Repo, and try again.
The connector doesn't appear when you type @
Ask Grok Bot to list your MCP servers and confirm Context Repo is connected. If it isn't listed, add https://contextrepo.com/grok-mcp again. New tools become available from your next message.