mcp-chatgpt-file-store
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP | No | Set to '1' to run in Streamable HTTP mode instead of stdio. | |
| MCP_HTTP_PORT | No | Port for the Streamable HTTP server. Defaults to 3000. | 3000 |
| MCP_AUTH_TOKEN | No | Bearer token required for /mcp requests. If not set, no authentication is enforced. | |
| CHATGPT_FILE_STORE_DIRS | No | Comma-separated list of directories that ChatGPT is allowed to read/write. Defaults to the `chatgpt` folder inside the project. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_allowed_directoriesA | Returns the directories ChatGPT is allowed to read from and write to. Call this first. |
| list_directoryA | Lists files and folders inside a directory within the allowed store. |
| read_fileA | Reads the full contents of a text file inside the allowed file store. |
| get_file_infoA | Returns metadata (size, modified time, permissions) for a path. |
| search_filesB | Searches the file store for files matching a pattern (supports * and ?). |
| write_fileA | Creates or overwrites a file in the file store. Parent folders are created automatically. Use this to save notes, drafts, summaries, or generated documents. |
| append_fileA | Appends content to an existing file, or creates the file if it does not exist. Use this to keep growing a running log or notes file. |
| create_directoryA | Creates a folder (and any missing parents) inside the file store. |
| move_fileB | Moves or renames a file or folder inside the file store. |
| delete_fileA | Permanently deletes a file or folder (recursively) from the file store. Use with care. |
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 10 tools
Each tool targets a distinct file operation: move, delete, append, read, write, list, search, metadata, directory creation, and allowed-directory listing. There is no functional overlap that could confuse an agent.
All tool names follow the verb_noun pattern in snake_case (e.g., move_file, list_directory, get_file_info). The naming is uniform and predictable across the entire set.
With 10 tools, the server covers the essential file operations without bloat. Each tool serves a clear purpose and the count feels appropriate for a file store MCP server.
The surface covers create, read, update, delete, move, search, and metadata operations. One notable gap is the absence of a copy_file operation, which would round out the file management capabilities, but existing coverage is solid.