ChatGPT MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_rootsA | List the approved root names and access modes. Call this before other file tools to discover valid root values; filesystem paths and file contents are not returned. |
| list_filesA | List up to 1,500 immediate files and directories in an approved root, including relative path, type, size and modification time. Use search_files for recursive discovery. Does not change files. |
| file_infoA | Inspect a file or directory in an approved root and return its type, size and modification time without reading its contents. Use read_file for UTF-8 content. Read-only. |
| read_fileA | Read text from an approved local root as UTF-8, truncating at MAX_READ_BYTES (512 KB by default) with a clear truncation marker. Use search_files first to locate passages; binary files are not supported. Read-only. |
| search_filesA | Recursively search filenames and UTF-8 contents inside an approved root with case-insensitive substring matching. Returns relative paths and brief snippets, bounded by max_results and a file scan limit; skips symlinks and build folders. Use read_file for complete text. |
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 5 tools
Each tool has a distinct role: discovering roots, listing directory contents, inspecting one path, reading text, and recursive searching. The only mild overlap is that list_files and file_info both return metadata, but their scope is clearly differentiated by the descriptions.
Four of five tools follow a clear verb_noun convention (list_roots, list_files, read_file, search_files). file_info is noun-based rather than get_file_info, which is a minor deviation but still understandable.
Five tools is well-scoped for a read-only filesystem bridge. Each tool covers a necessary operation—discovery, listing, metadata, reading, and searching—without redundant surface area.
The read-only filesystem surface is coherent and covers discovery, navigation, metadata, reading, and search. It lacks write/create/delete operations, but the descriptions consistently frame the server as read-only, so this is a minor scope gap rather than an internal inconsistency.