Code Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOEKT_URL | No | Zoekt Web Server URL | http://localhost:6070 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_codeA | 在 Zoekt 已索引的仓库中定位源码文本及其文件位置。 当用户询问符号定义或引用、错误信息来源、配置项用法、接口实现或精确 代码模式时使用。结果包含仓库、仓库内相对路径、从 1 开始的行号和命中 行片段；需要理解周围实现时，再用该结果调用 get_file_context。 query 默认按 Zoekt 查询语法解释。搜索包含空格、连字符或查询运算符的 完整错误信息、服务名或包名时设置 literal=true。已知仓库、语言或路径 范围时应使用对应过滤器，以减少无关结果。该工具只做文本/正则检索， 不执行语义分析，也不保证命中就是定义。 |
| get_file_contextA | 读取一次代码搜索命中位置周围带行号的源码上下文。 应在 search_code 返回候选命中后调用，并原样传入该命中的 repo、path 和
line。适合确认命中属于定义、调用还是配置，以及在回答用户前理解附近
的控制流。返回内容以 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clear, non-overlapping purposes: search_code finds code locations based on text queries, while get_file_context retrieves surrounding source context for a specific hit. No ambiguity exists.
Both tool names follow a consistent verb_noun pattern (search_code, get_file_context) using snake_case. The naming is predictable and clearly conveys the action and object.
With only 2 tools, the server is minimal but focused on a narrow domain: code search and context retrieval. While some might expect additional filtering or browsing tools, the count is appropriate for a targeted utility.
The server covers the core workflow of searching code and retrieving file context. Minor gaps exist (e.g., no direct language-specific filter, no batch operations), but the surface is sufficient for the stated purpose.