claude mcp add codesearch-mcp-flupkede -- codesearch mcp
One-liner. Verify with claude mcp list. Remove with claude mcp remove.
Install the Rust binary before registering MCP
Use the author's release archive for your operating system, or build the repository with Cargo. Put the resulting codesearch executable on the PATH used by your client, or use its absolute path as command. The directory slug is not an npm package name.
Register the repository before connecting. The examples below are documentation examples; no package was installed or executed for this guide.
Build from the author repository (optional)
git clone https://github.com/flupkede/codesearch.git
cd codesearch
cargo build --release
Register a repository and check a first query
codesearch index add /absolute/path/to/project
codesearch search "authentication middleware"
codesearch doctor
When to use: When you want to bring Codesearch MCP into your Claude workflow.
Flow
Install the MCP server in your client (see Install tab).
Register the local repository and confirm that its index is available.
Ask Claude to use the new tools.
Use Codesearch MCP to help me with a task.✓ Copied
Outcome: Claude can interact with Codesearch MCP directly from your IDE.
Choose local stdio or a running HTTP server
codesearch mcp defaults to auto mode: it connects to a running serve process or uses a local index. Local mode uses the nearest index from the working directory; launch it from the indexed repository. For several repositories, start codesearch serve and use its /mcp Streamable HTTP endpoint.
If client mode cannot connect, check that serve is running. If a search is empty, check the registered repository and index with codesearch index list and codesearch doctor before changing the query. Ask the agent to use search, then get_chunk for the returned code; do not treat the example replay as a verified result.
Keep one repository local
cd /absolute/path/to/project
codesearch mcp --mode local