muninn-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUNINN_DATA_DIR | No | ChromaDB data directory | ~/.config/opencode/muninn |
| MUNINN_OLLAMA_URL | No | Ollama service URL | http://localhost:11434 |
| MUNINN_PROJECT_ID | No | Force a specific project ID | (auto from git root) |
| MUNINN_EMBED_MODEL | No | Embedding model name | mxbai-embed-large |
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 |
|---|---|
| memory_writeA | Write a memory entry to the current project's memory store. Use this tool to save important context, decisions, code patterns, or next-steps that should be persisted for future sessions. Args: text: The memory content to store (required). memory_type: Type of memory. Must be one of: summary, decision, next-steps, code-pattern, note (default). tags: Comma-separated tags for categorization (optional). |
| memory_searchA | Search the current project's memory store using semantic similarity. Embeds the query and returns the most relevant stored memories. Args: query: The search query text (required). top_k: Maximum number of results to return (default 5). |
| memory_listA | List memories stored in the current project, ordered by creation time (newest first). Args: limit: Maximum number of memories to return (default 20). offset: Number of memories to skip for pagination (default 0). |
| memory_deleteB | Delete a specific memory from the current project by its ID. Args: memory_id: The full or partial ID of the memory to delete (required). |
| global_memory_writeA | Write a memory entry to the global (cross-project) memory store. Global memories are shared across all projects and can be queried regardless of which project the MCP server is running in. Args: text: The memory content to store (required). memory_type: Type of memory. Must be one of: summary, decision, next-steps, code-pattern, note (default). tags: Comma-separated tags for categorization (optional). |
| global_memory_searchA | Search the global (cross-project) memory store using semantic similarity. Embeds the query and returns the most relevant stored memories from all projects. Args: query: The search query text (required). top_k: Maximum number of results to return (default 5). |
| global_memory_listA | List globally stored memories, ordered by creation time (newest first). Args: limit: Maximum number of memories to return (default 20). |
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 7 tools
Tools are clearly separated by scope (global vs. project-specific) using consistent prefixes, and each tool performs a distinct operation (list, search, write, delete). No ambiguity between tools.
All tool names follow a consistent pattern: scope prefix (global_memory_ or memory_) followed by a verb (list, search, write, delete). Naming is predictable and uniform.
With 7 tools covering both global and project memory operations (list, search, write, delete), the count is well-scoped and appropriate for a focused memory store server.
The tool surface is mostly complete for both scopes, but the global scope lacks a delete operation, which is a minor gap. CRUD operations are otherwise covered.