- Home
- MCP servers
- Code Search
Code Search
- javascript
6
GitHub Stars
javascript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"raintear94-code-search-mcp": {
"command": "node",
"args": [
"{file}/code-search/index.js"
]
}
}
}You can run this high-performance MCP server locally to explore and locate code across large projects. It processes code in batches, provides panoramic context, and returns precise locations for classes, methods, and definitions to accelerate AI-assisted code understanding.
How to use
Connect your MCP client to the server using the stdio interface described by the server configuration. You will run the server locally and feed it requests for reading multiple files, building project outlines, or locating specific code items in batch. Use the batch tools to read files with dependency context expanded, generate structural outlines with Java annotation awareness, or locate classes, methods, and definitions precisely.
How to install
Prerequisites you need before installing include Node.js version 18.0.0 or later.
npm install
npm run build
Configuration and runtime
To run the MCP server locally, configure the MCP connection using a stdio endpoint. The server runs as a local process and is connected via standard I/O.
"mcpServers": {
"code-search": {
"command": "node",
"args": ["{file}/code-search/index.js"]
}
}
Notes on usage and best practices
- Prefer batch operations that return full context in a single call where possible. - Absolute paths are recommended for stability. - Break complex queries into precise, smaller calls to maximize reliability and reproducibility.
Security and environment
No special environment variables are required to run the server by default. If you introduce environment variables for your deployment, document them in your deployment config and keep them out of version control.
Troubleshooting
If the server fails to start, verify Node.js v18+. Ensure the path to the index script is correct in the mcpServers configuration and that dependencies are installed. Check file permissions and confirm there are no port or I/O restrictions affecting stdio communication.
Available tools
view_files_full_context
Batch read with dependency context auto-expanded to provide panoramic code understanding.
view_files_outlines
Batch outline extraction with Java annotation awareness to generate structural project views.
view_code_items
Batch locate classes, methods, and definitions with precise results for quick navigation.