MCP File Context Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_contextA | Read and analyze code files with advanced filtering and chunking. The server automatically ignores common artifact directories and files:
For large files or directories, use get_chunk_count first to determine total chunks, then request specific chunks using chunkNumber parameter. |
| get_chunk_countA | Get the total number of chunks that will be returned for a read_context request. Use this tool FIRST before reading content to determine how many chunks you need to request. The parameters should match what you'll use in read_context. |
| set_profileC | Set the active profile for context generation |
| get_profile_contextC | Get repository context based on current profile settings |
| generate_outlineC | Generate a code outline for a file, showing its structure (classes, functions, imports, etc). Supports TypeScript/JavaScript and Python files. |
| getFilesC | Retrieve multiple files by their paths, returning content and metadata for each file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bsmi021/mcp-file-context-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server