Workspace-local — searches your actual codebase on disk, not a remote index.
← MCP server registry
Developer toolsPublic source
Code Search MCP Server
Semantic code search, symbol lookup, call graphs, dependency graphs, ownership maps, and context pack generation for ADK-Rust Enterprise agents. Provides 8 MCP tools that work against any local workspace.
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Multi-language — supports Rust, TypeScript, Python, Go, Java, JavaScript.
Structural awareness — understands symbols, call graphs, dependencies, and ownership.
Context packs — gather related files, deps, and tests for LLM context windows.
Zero config — point at a directory and search. No indexing step required.
Registry-ready — ships with mcp-server.toml for ADK-Rust Enterprise onboarding.
Architecture
How Code Search MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
01
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
02
MCP client
Discovers schemas, sends calls, and receives typed content.
03
Code Search MCP Server
Validates the request and owns 8 documented tool contracts.
04
Domain system
Keeps the API, data, credentials, and business rules behind the server.
From the project documentation
The server’s published architecture
Tool catalog
What can an agent ask Code Search MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
8 named tools
semantic_searchSemantic code search — find code by meaning, not just text matching
read onlylookup_symbolLook up a symbol definition (function, struct, trait, const, type)
read onlyfind_referencesFind all references to a symbol across the codebase
read onlycall_graphGet the call graph for a function (who calls it, what it calls)
read onlydependency_graphGet the dependency graph for a module or crate
read onlycodeownersGet CODEOWNERS for a file or directory path
read onlycontext_packBuild a context pack — gather related files, dependencies, and tests
read onlyexplain_symbolExplain a symbol — definition, signature, doc comments, usage count
read onlyGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
8 read only
- The registry manifest declares read only tool risk classes.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcpRegistry manifest
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
Install
cargo install mcp-code-searchMCP client configuration
export CODE_SEARCH_WORKSPACE=/path/to/your/projectCommands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in developer tools.
A2A Remote Agent MCP ServerAgent-to-Agent protocol management for ADK-Rust Enterprise. Discover remote agents, send tasks, stream results, and manage push notifications — across any framework that implements the A2A protocol.11 toolsACP Workspace MCP ServerEnterprise control plane for ACP (Agent Client Protocol) sessions in ADK-Rust Enterprise. Provides 9 MCP tools for managing coding delegates — permission gates, patch review, session lifecycle, and agent exposure.9 toolsCI/CD MCP ServerGive your AI agents visibility into CI/CD pipelines. This MCP server connects to GitHub Actions so agents can check build status, read logs, download artifacts, trigger deployments, and re-run failed jobs — all through…8 tools
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.1.0
- License
- Apache-2.0
- Tools
- 8
- Revision
- 8a24b93a66d3
- Updated
- May 24, 2026
Transportsstdio