Context Repo DocsGrok
Connect Grok 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 to Context Repo to search, read, create, and organize your prompts, documents, and collections from a Grok conversation. Setup takes about a minute and only requires a connector name and the dedicated Grok MCP Server URL.
Connect Context Repo
Open Grok connectors
Go to grok.com/connectors, create a new connector, and choose the custom connector option.
Enter the connector details
Use these exact values:
| Field | Value |
|---|---|
| Name | Context Repo |
| Server URL | https://contextrepo.com/grok-mcp |
Use /grok-mcp, not the standard /mcp endpoint. This dedicated endpoint starts the OAuth flow Grok needs. You don't need to paste an API key, OAuth client ID, or client secret into Grok.
Save and authorize
Save the connector. When Grok checks the server, it opens the Context Repo sign-in flow. Sign in with your Context Repo account and approve access.
Verify the connection
Start a Grok conversation with the Context Repo connector enabled, then ask:
List my Context Repo collections.
Grok should return the collections from the same workspace you see in the Context Repo dashboard.
What You Can Do
Grok receives the full hosted MCP tool set: 27 Context Repo tools plus the search and fetch retrieval aliases. You can ask Grok 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 connector uses Context Repo's hosted OAuth flow. Grok discovers the sign-in requirements from the dedicated endpoint, opens Context Repo authorization, 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.
Troubleshooting
The sign-in window doesn't open
Check that the server URL is exactly https://contextrepo.com/grok-mcp. If you previously created a connector with https://contextrepo.com/mcp, remove it and create a new custom connector with the dedicated Grok URL.
Grok reports an authentication error
Remove the connector, add it again, and complete the Context Repo sign-in flow without closing the authorization window. Sign in with the account that owns the workspace you want Grok to access.
Grok can't find your content
Open the Context Repo dashboard and confirm the content exists in the account you authorized. Then start a new Grok conversation with the Context Repo connector enabled.
MCP Tools Reference
See all 27 Context Repo tools and the two hosted retrieval aliases.
MCP Server Overview
Learn how Context Repo connects your workspace to MCP clients.
Grok Bot
Connect the same workspace to the Grok Bot desktop and iOS app.
ChatGPT Plugin
Connect the same Context Repo workspace to ChatGPT through OAuth.
ChatGPT Plugin
Access your prompts, documents, and collections directly from ChatGPT conversations. The Context Repo ChatGPT Plugin connects with OAuth and gives ChatGPT all 27 MCP tools (29 including ChatGPT Apps SDK aliases `search`/`fetch`).
Grok 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.