Context File MCP Service
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_sourceB | Add a context file source (local directory or GitHub repository) |
| list_sourcesA | List all configured context file sources |
| list_filesB | List all context files available in a source |
| read_context_fileB | Read the contents of a specific context file |
| read_multiple_context_filesC | Read multiple context files at once |
| search_context_filesC | Search across context files with optional tag filtering |
| list_tags | List all available tags across context files |
| get_files_by_tagB | Get all context files with a specific tag |
| get_file_metadataB | Get metadata (tags, title, description) for a context file |
| refresh_file_listB | Refresh the cached list of files for a source |
| stop_watching | Stop watching a source for file changes |
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 9 tools
Each tool has a clearly distinct purpose: listing, reading (single and multiple), searching, retrieving by tag, fetching metadata, refreshing cache, and managing sources. No overlapping functionalities that would cause misselection.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_files, read_context_file, add_source). The naming convention is uniform and predictable across all 9 tools.
With 9 tools, the set is well-scoped for a context file management service. Each tool covers a necessary operation without redundancy or excessive granularity.
The tool surface covers the full lifecycle for context files: browsing sources, listing files, reading content (single and batch), searching/tagging, retrieving metadata, and refreshing cache. No obvious gaps for the intended read-oriented purpose.