Server facts
code-context-provider-mcp
Project
- Author
- AB498
- License
- MIT
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 20
- Last commit
- Data as of
Tags
- context
- mcp
- provider
Overview
A directory map is the starting point for Code Context Provider’s codebase inspection workflow. AI assistants call get_code_context with an absolute directory path to retrieve the project’s structure, with file analysis and symbol inclusion available as separate options that are disabled by default. When enabled, symbol extraction covers JavaScript, JSX, TypeScript, TSX, and Python files. Callers can request functions, classes, variables, imports, exports, or all supported categories; anonymous functions are excluded from the results.
For larger repositories, filePatterns narrows the selection through wildcard patterns, file extensions, or exact filenames, while maxDepth controls directory traversal with a default of 5 levels. Other file types can appear in the directory listing without receiving supported symbol analysis. These controls let an assistant focus on selected source files or a shallower portion of a project when gathering context for a task. Parsing uses WebAssembly Tree-sitter rather than native dependencies. The package runs on Node, communicates over stdio, and is distributed under the MIT license.
code-context-provider-mcp setup notes
- code-context-provider-mcp records stdio only; confirm a network transport upstream before planning remote access.