zoekt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOEKT_URL | No | The URL of the zoekt-webserver backend | http://localhost:6070 |
| ZOEKT_TIMEOUT | No | HTTP timeout in seconds for requests to the zoekt backend | 30 |
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 | Run a Zoekt query against the indexed corpus. |
| list_reposA | List indexed repositories. |
| get_fileA | Fetch the full contents of a file from an indexed repository. |
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 3 tools
Each tool has a clearly distinct purpose: listing repositories, searching code, and retrieving file contents. No ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_repos, search_code, get_file.
Three tools cover the essential operations for a code search index server (list, search, fetch) without being too few or too many.
The set covers the core workflows well. A minor gap might be listing files within a repository, but the current set is sufficient for common use cases.