Project Context MCP

What ericbrown/project-context-mcp MCP server does

ericbrown/project-context-mcp MCP server turns a project's .context/ directory into a collection of MCP resources that Claude Code can browse and include with @ mentions. It is intended for documentation and other project-specific knowledge that may not be obvious from the source code, such as coding conventions, architecture decisions, database guidance, testing practices, deployment procedures, and known issues.

The directory can contain documentation, configuration or data files, and code examples. Supported extensions include Markdown, plain text, reStructuredText, AsciiDoc, YAML, JSON, TOML, XML, CSV, INI, CFG, CONF, Python, JavaScript, TypeScript, JSX, TSX, HTML, CSS, SQL, and shell files. Hidden files and common generated or repository folders such as __pycache__, node_modules, .git, and .DS_Store are excluded.

How it works

At startup, ericbrown/project-context-mcp MCP server looks for .context/ in the current directory. It scans that directory recursively and returns the discovered files as MCP resources. When Claude Code requests available resources while the user types @, the server supplies each file's name, description, and URI. Selecting a resource fetches its contents for inclusion in the prompt.

Resources use the context:// URI scheme. For example, .context/architecture.md is exposed as context://architecture.md, while a nested file such as .context/api/patterns.md becomes context://api/patterns.md.

Names are generated from file content or filenames. Markdown uses its first level-one heading when available; other files use a title-cased filename. The first paragraph is used as the autocomplete description, helping distinguish resources before opening them.

Setup and configuration

Install the server with uvx through Claude Code:

claude mcp add project-context -s user -- uvx project-context-mcp

The server requires Python 3.10 or newer when installed through the Python package. Create a .context/ directory in the project where the server will run, then place the relevant files inside it. Subdirectories are supported, so documentation can be separated into areas such as API, database, or frontend guidance.

No configuration file or environment variable is required. The repository also lists pip as an alternative installation method, but the documented Claude Code setup uses uvx.

Tools and capabilities

• Exposes eligible .context/ files as MCP resources.
• Recursively discovers files in nested folders.
• Supports selective inclusion through Claude Code @ mentions.
• Generates resource names from Markdown headings or filenames.
• Generates autocomplete descriptions from each file's first paragraph.
• Uses context:// URIs for top-level and nested resources.

Limitations and notes

The server focuses on project context files; it does not describe tools for editing, indexing, or synchronizing documentation. Files must use one of the supported extensions to be exposed, and excluded hidden or generated paths will not appear. Context is selected explicitly with @ mentions, so it is not automatically included in every prompt in the way a single always-loaded project instruction file might be.

The documented integration is with Claude Code. The server checks the current directory for .context/, so the folder must be present in the project context where the MCP process starts.