io.github.jbacalso24/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.
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mimry_list_adaptersB | List active and planned MIMRY adapter plugins for coding-agent routing. |
| mimry_statusB | Return MIMRY initialization and index freshness for a root. Freshness trusts unchanged file metadata, like git; |
| mimry_reindexC | Rebuild the local MIMRY index for a root; |
| mimry_initC | Initialize MIMRY metadata for a root. |
| mimry_refreshC | Run MIMRY index, semantic index, then status. |
| mimry_preflightD | Fast readiness check and task context generation, matching CLI preflight. |
| mimry_findC | Search indexed files with ranking reasons. |
| mimry_semanticC | Local-only semantic search over bounded MIMRY chunks. |
| mimry_relatedC | Return files related to a query using graph-aware ranking signals. |
| mimry_routeC | Recommend an agent/role, context packs, files, risk gates, and verification for a task. |
| mimry_briefC | Write a role-aware MIMRY agent brief and return its path plus route payload. |
| mimry_symbolC | Search indexed symbols by name. |
| mimry_contextC | Generate a MIMRY context pack and return its path plus selected files. |
| mimry_explainC | Explain top files, symbols, graph evidence, and verification hints for a task. |
| mimry_pathC | Find a graph relationship path between two files/symbols/queries. |
| mimry_whyC | Explain why a file or symbol ranked for a task query. |
| mimry_feedbackD | Record local agent usage feedback for future ranking. |
| mimry_digestC | Return the canonical semantic digest and state metadata for an index generation. |
| mimry_plan_treeC | Return canonical JSON plus deterministic terminal and Markdown projections for a plan tree. |
| mimry_plan_checkC | Validate a stored plan tree without changing it. |
| mimry_plan_digestB | Return the canonical semantic SHA-256 for a stored plan tree. |
| mimry_plan_listC | Return the deterministic local plan inventory for a root. |
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 22 tools
Several tools occupy overlapping search/context/ranking territory, including find, semantic, related, symbol, path, why, explain, context, route, brief, and preflight. The descriptions clarify some boundaries, but the set still leaves meaningful ambiguity about which retrieval/explanation tool to choose.
All tools use a consistent mimry_ prefix with lower_snake_case naming. The main variation is noun vs. verb forms such as mimry_status, mimry_find, and mimry_plan_tree, but the convention is still readable and predictable.
The server exposes 22 tools, which is heavy for an MCP surface even considering the indexing, routing, and planning scope. It sits in the borderline-heavy range where consolidation or stronger grouping would improve usability.
The toolset covers index lifecycle, search, semantic retrieval, routing, context generation, explanations, feedback, digests, and plan tree operations. Minor gaps may exist around explicit reset/delete or plan mutation, but core workflows appear well represented.