mimry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_COLOR | No | Set to 1 to turn off colour output. | |
| MIMRY_LOCK_TIMEOUT_SECONDS | No | Lock waits are bounded to 10 seconds by default; set MIMRY_LOCK_TIMEOUT_SECONDS to raise the bound. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
MIMRY is a local index of this repository: files, symbols and how they connect. Start a repository task with mimry_preflight and the task in your own words, then read the context pack it names before opening files; it ranks the files the task likely touches and says why. Use mimry_find for a focused search and mimry_symbol for a function or class by name. For an exact string you already know, use rg or git grep instead. Results are navigation, not proof: check the source before relying on them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mimry_statusB | Return MIMRY initialization and index freshness for a root. Freshness trusts unchanged file metadata, like git; |
| mimry_preflightD | Fast readiness check and task context, matching CLI preflight. |
| mimry_findC | Search files, optionally with bounded live-source snippets. Pass offset=0 on page one. |
| mimry_relatedC | Return files related to a query by graph-aware ranking. |
| mimry_symbolA | Search indexed symbols by name, falling back to file names. Set relations to "callers" (what calls the symbol) or "callees" (what it calls), with depth 1 to 3 for how many calls away to follow. file picks one symbol when several share the name, and file may end in ":N" to pick by line; line picks the symbol that starts on that line, or else spans it. Without relations this only searches. |
| mimry_pathC | Find a relationship path between two files/symbols/queries. |
| mimry_impactA | What a change touches: callers, importers, referencing files and tests to run. target is a symbol name (file picks one when several share it, and line picks by the line it starts on or spans) or a repo-relative file path. changed=True uses the working tree against HEAD instead. depth is 1 to 5, how many calls back to follow. |
| mimry_whyC | Explain why a file or symbol ranked for a task query. |
| mimry_feedbackC | Record local agent usage feedback for future ranking. |
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 9 tools
Most tools target clearly distinct operations: symbol search, file search, change impact, path finding, status, and feedback. However, mimry_find (search files) and mimry_related (related files by graph ranking) can be confused since both take a query and return files, and mimry_status vs mimry_preflight both read as readiness checks. The descriptions do differentiate them, but the boundaries are slightly soft.
Every tool follows the same mimry_ prefix with a single concise snake_case noun/verb, e.g. mimry_find, mimry_symbol, mimry_impact, mimry_path. The pattern is completely predictable and readable throughout.
Nine tools sit comfortably in the well-scoped range for a code-graph intelligence server. Each maps to a distinct query type (search, relations, impact, path, ranking, status, feedback) with no filler.
The surface covers search (find, symbol), graph relationships (related, impact, path, why), freshness (status, preflight), and feedback, giving strong end-to-end graph-query coverage. A minor gap is the absence of an explicit index/init or reindex operation, since freshness verification seems confined to status.