chatgpt-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATGPT_ACCOUNT_ID | No | ChatGPT account ID (optional, for Team/Enterprise accounts). | |
| CHATGPT_BEARER_TOKEN | Yes | ChatGPT bearer token from browser DevTools. | |
| CHATGPT_CODEX_MCP_ENV_FILE | No | Path to a private env file for credentials. | $HOME/.config/chatgpt-context-mcp/env |
| CHATGPT_CODEX_MCP_CACHE_DIR | No | Override cache directory path. | $HOME/.cache/chatgpt-context-mcp/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| import_chatgpt_urlC | Refresh and import a private ChatGPT /c/{conversation_id} URL into local cache and return bounded context. |
| get_chatgpt_contextA | Read an already imported ChatGPT conversation from local cache. This does not check the remote conversation. |
| list_chatgpt_importsA | List locally cached ChatGPT conversation imports, optionally filtered by a simple text query. |
| verify_chatgpt_authA | Check whether CHATGPT_BEARER_TOKEN is present, unexpired, and accepted by the ChatGPT backend. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct function: fetching cached context, importing/refreshing from URL, listing imports, and verifying authentication. No overlap in purpose.
All tools follow a consistent verb_noun pattern with snake_case and a 'chatgpt_' prefix, making the API predictable and easy to understand.
Four tools cover the core operations for managing ChatGPT context (auth, import, retrieve, list) without being excessive or insufficient for the domain.
The set covers the main workflows (auth, import, read cached, list), but lacks a delete or remote fetch tool, which could be minor gaps in advanced usage.