MCP server
by ab498
Analyze JavaScript, TypeScript, and Python projects with Code Context Provider—advanced static code analysis and source
Analyzes project directories to extract code structure and symbols from JavaScript, TypeScript, and Python files using Tree-sitter parsers. Generates directory trees and provides detailed code analysis for AI assistants.
Code Context Provider is a community-built MCP server published by ab498 that provides AI assistants with tools and capabilities via the Model Context Protocol. Analyze JavaScript, TypeScript, and Python projects with Code Context Provider—advanced static code analysis and source It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.
You can install Code Context Provider in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Code Context Provider is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Code Context Provider has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: Code Context Provider surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Code Context Provider against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, Code Context Provider benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Code Context Provider into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Code Context Provider into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Code Context Provider surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Code Context Provider has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Code Context Provider is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Code Context Provider benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 62
To install Code Context Provider for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @AB498/code-context-provider-mcp --client claude
{
"mcpServers": {
"code-context-provider-mcp": {
"command": "cmd.exe",
"args": [
"/c",
"npx",
"-y",
"code-context-provider-mcp@latest"
]
}
}
}
{
"mcpServers": {
"code-context-provider-mcp": {
"command": "npx",
"args": [
"-y",
"code-context-provider-mcp@latest"
]
}
}
}
OR install globally with npm:
npm install -g code-context-provider-mcp
Then use it by running:
code-context-provider-mcp # if you're not using @latest, you may want to clear the cache for latest version using `Remove-Item -Path "$env:LOCALAPPDATA
pm-cache\_npx" -Recurse -Force` for windows and `rm -rf ~/.npm/_npx` for linux/macos
get_code_contextAnalyzes a directory and returns its structure along with code symbols (optional).
Parameters:
absolutePath (string, required): Absolute path to the directory to analyzeanalyzeJs (boolean, optional): Whether to analyze JavaScript/TypeScript and Python files (default: false)includeSymbols (boolean, optional): Whether to include code symbols in the response (default: false)symbolType (enum, optional): Type of symbols to include if includeSymbols is true (options: 'functions', 'variables', 'classes', 'imports', 'exports', 'all', default: 'all')filePatterns (array of strings, optional): File patterns to analyze (e.g. ['.js', '.py', 'config.*'])maxDepth (number, optional): Maximum directory depth to analyze (default: 5 levels)Note: Anonymous functions are automatically filtered out of the results.
Directory structure for: C:\Users\Admin\Desktop\mcp\context-provider-mcp
Code Analysis Summary:
- Files analyzed: 3
- Total functions: 29
- Total variables: 162
- Total classes: 0
Note: Symbol analysis is supported for JavaScript/TypeScript (.js, .jsx, .ts, .tsx) and Python (.py) files only.
Code analysis limited to a maximum depth of 5 directory levels (default).
├── index.js (39 KB)
│ └── [Analyzed: 22 functions, 150 variables, 0 classes]
│ Functions:
│ - initializeTreeSitter [39:0]
│ - getLanguageFromExtension [107:0]
│ - getPosition [138:24]
You can use the filePatterns parameter to specify which files to analyze. This is useful for complex projects with multiple languages or specific files of interest.
Examples:
["*.js", "*.py"] - Analyze all JavaScript and Python files["config.*"] - Analyze all configuration files regardless of extension["package.json", "*.config.js"] - Analyze package.json and any JavaScript config files[".ts", ".tsx", ".py"] - Analyze TypeScript and Python files (using extension format)The file pattern matching supports:
For very large projects, you can use the maxDepth parameter to limit how deeply the tool will traverse directories:
maxDepth: 2 - Only analyze the root directory and one level of subdirectoriesmaxDepth: 3 - Analyze the root, and two levels of subdirectoriesmaxDepth: 0 - Only analyze files in the root directoryThis is particularly useful when:
Code symbol analysis is supported for:
Using the filePatterns parameter allows you to include other file types in the directory structure, though symbolic analysis may be limited.
# Clone the repository
git clone https://github.com/your-username/code-context-provider-mcp.git
cd code-context-provider-mcp
# Install dependencies
npm install
# Set up WASM parsers
npm run setup
After installation, the package's prepare script automatically runs to download the WASM parsers. If for some reason the download fails, users can manually run the setup:
npx code-context-provider-mcp-setup
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.