Context Repo DocsChatGPT 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`).
The Context Repo ChatGPT Plugin gives ChatGPT direct access to your prompts, documents, and collections. Instead of copying and pasting between tabs, you ask ChatGPT to search your workspace, retrieve a prompt, or create a document — and it calls the right tool automatically.
It uses the same 27 MCP tools available to other clients like Claude, Cursor, and VS Code, plus two ChatGPT-specific Apps SDK aliases (search, fetch) that the Company-Knowledge surface invokes on your behalf — for a total of 29 registered tools on the web-hosted server. Authentication is handled through OAuth, so you sign in with your Context Repo account directly inside ChatGPT.
Add Context Repo from ChatGPT Plugins. ChatGPT will connect the app with OAuth.
Getting Started
Turn on Developer mode
In ChatGPT, open Settings → Security and login and turn on Developer mode. Availability can depend on your account and workspace policy.
Open ChatGPT Plugins
Go to ChatGPT Plugins and select the plus button.
Connect the MCP server
Enter these values:
| Field | Value |
|---|---|
| Name | Context Repo |
| Description | Access your prompts, documents, and collections. Search, create, update, and organize your AI context. |
| MCP Server URL | https://contextrepo.com/mcp |
| Authentication | OAuth |
| OAuth Client ID | (leave blank) |
| OAuth Client Secret | (leave blank) |
Check the "I understand and want to continue" confirmation if ChatGPT shows it, then create the plugin. ChatGPT will connect the app with OAuth. Sign in with the same Context Repo account you use on the dashboard.
No API key is needed for the ChatGPT Plugin. OAuth handles authentication automatically.
Start using your context
Ask ChatGPT anything about your workspace. For example:
- "List my prompts about code review"
- "Search my documents for rate limiting"
- "Create a new prompt called Weekly Standup Notes"
- "Show me version history for my API docs prompt"
ChatGPT picks the right tool and returns results directly in the conversation.
Available Tools
The ChatGPT Plugin has access to all 27 Context Repo MCP tools, organized into 7 categories:
| Category | Tools | What they do |
|---|---|---|
| User Info | 1 tool | Get your account details |
| Prompts | 7 tools | List, get, create, update, delete prompts, plus view and restore version history |
| Documents | 7 tools | List, get, create, update, delete documents, plus view and restore version history |
| Collections | 7 tools | List, get, create, update, delete collections, plus add and remove items |
| Search | 1 tool | Find prompts, documents, and collections by semantic or keyword search |
| Deep Search | 3 tools | Search within document content, read specific chunks, and navigate document hierarchy |
| Reasoning | 1 tool | Get a synthesized, cited answer composed across your documents — with citations, gaps, and conflicts |
For the complete parameter reference, see the MCP Tools Reference.
What You Can Do
The ChatGPT Plugin supports every operation available through the MCP Server. Here are common workflows:
Prompt management
Ask ChatGPT to find, use, or modify your prompt templates:
- "Show me my code review prompts" — uses
search_promptswith a search filter - "Get the full content of my PR Review Assistant prompt" — uses
read_prompt - "Update my deployment checklist prompt with a new security section" — uses
update_prompt - "Restore my API docs prompt to the version from last week" — uses
get_prompt_versionsandrestore_prompt_version
Document search and retrieval
Find exactly what you need across your entire workspace:
- "Search my documents for authentication patterns" — uses
find_itemswith semantic search - "What do my research notes say about caching strategies?" — uses
deep_searchfor content-level results - "Show me more context around that caching section" — uses
deep_expandto navigate surrounding content
Collection organization
Manage your knowledge base structure through conversation:
- "List all my collections" — uses
list_collections - "Add my latest document to the Research collection" — uses
add_to_collection - "Create a new collection called Q1 Planning" — uses
create_collection
How Authentication Works
The ChatGPT Plugin uses a hosted OAuth flow for authentication. Here's what that means in practice:
- When you first use the plugin, ChatGPT redirects you to Context Repo's sign-in page.
- You log in with your existing Context Repo credentials (email, Google, GitHub, or any method you've set up).
- After authorizing, the connection stays active — you don't need to sign in again for subsequent conversations.
This is different from MCP clients like Cursor or Claude Desktop, which use an API key. The ChatGPT Plugin doesn't require you to generate or manage any keys.
The same 27 user-callable tools are available regardless of how you connect (29 registered on the web-hosted server when including the ChatGPT Apps SDK aliases). Whether you use the ChatGPT Plugin (OAuth), an MCP client (API key or OAuth), or the REST API — you're accessing the same workspace and the same capabilities.
Troubleshooting
Sign-in prompt doesn't appear
Try starting a new conversation with the Context Repo plugin. If the sign-in flow still doesn't trigger, clear your ChatGPT browser cache and try again.
"Authentication failed" error
Make sure you're signing in with the same account you use on the Context Repo dashboard. If you have multiple accounts, check which email address is associated with your workspace.
Tools not responding
If a tool call returns an error, verify that your Context Repo account is active. You can test your account by logging into the dashboard directly.
Chrome Extension
Capture any webpage into your Context Repo workspace with one click. Install the free Chrome Extension, connect your API key, and start building your knowledge base.
Grok
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.