Melchizedek
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| M9K_DB_PATH | No | The path to the SQLite database where memories are stored. | ~/.melchizedek/memory.db |
| M9K_RERANKER | No | Whether the cross-encoder reranker is enabled. | false |
| M9K_LOG_LEVEL | No | The logging level for the server. | warn |
| M9K_NO_DAEMON | No | Set to '1' to disable daemon mode. | 1 |
| M9K_EMBEDDINGS | No | Whether semantic embeddings are enabled. | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| m9k_searchA | Search indexed past conversations. Returns compact results with snippets. Results from the current project and session are boosted by default. Use m9k_context or m9k_full to drill down. |
| m9k_contextA | Get a chunk with surrounding context (adjacent chunks in the same session). Use after m9k_search to understand the conversation flow. |
| m9k_fullA | Retrieve full content of chunks by IDs. Use after m9k_search to get complete context. |
| m9k_file_historyB | Find past conversations that touched a specific file. Searches metadata (tool_use file_path) and text content. |
| m9k_errorsA | Find past solutions for an error message. Returns error context + how it was resolved. |
| m9k_similar_workA | Find past work similar to what you're about to do. Use at the start of a complex task to see previous approaches. Unlike m9k_search, this prioritizes chunks with rich metadata (multiple tools used, multiple files touched). |
| m9k_saveA | Manually save a memory note for future recall. Use for important decisions, patterns, or context. |
| m9k_sessionsB | List all indexed sessions, optionally filtered by project. |
| m9k_infoA | Show memory index information: corpus size, search pipeline status, usage metrics, embedding worker state. |
| m9k_configA | View or update plugin configuration. Changes are saved to ~/.melchizedek/config.json and take effect on next server restart. Without arguments, returns current config. |
| m9k_forgetA | Permanently remove a specific chunk from the memory index. Does NOT delete the source JSONL. Use m9k_search() first to find the chunk ID to forget. |
| m9k_delete_sessionA | Delete a session from the index. Removes all chunks and search data. Does NOT delete the source JSONL file. |
| m9k_ignore_projectA | Exclude a project from indexing. Future sessions won't be indexed. Optionally purge existing indexed sessions for this project. |
| m9k_unignore_projectA | Remove a project from the ignore list. Future sessions will be indexed again. Previously purged sessions are NOT restored (requires backfill re-indexation). |
| m9k_restartA | Restart the MCP server. Use after npm run build to load fresh code. The server disconnects; next MCP call auto-reconnects with the new build. |
| __USAGE_GUIDEC | melchizedek v1.0.2 — Persistent memory for Claude Code with hybrid search (BM25 + dual embeddings) + reranking. Corpus: empty (no sessions indexed yet). Available tools (16):
RETRIEVAL PATTERN (use this order):
SPECIALIZED SEARCH:
MANAGE:
|
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 16 tools
Each tool has a clearly distinct purpose: search, context retrieval, session management, configuration, etc. Even overlapping functions like m9k_search and m9k_similar_work are differentiated by description and use case. No two tools are easily confused.
Most tools follow the consistent m9k_verb_noun pattern (e.g., m9k_search, m9k_save). However, the tool __USAGE_GUIDE breaks this pattern with double underscores and all caps, which is a minor deviation from an otherwise uniform naming convention.
With 16 tools, the server is well-scoped for its purpose as a persistent memory system. Each tool covers a distinct function (search, context, save, delete, config, etc.) without being overwhelming or too sparse.
The tool surface covers the main CRUD-like operations (save, retrieve, forget, session delete) and specialized search (file history, errors, similar work). Minor gaps include no way to update existing chunks or list all chunk IDs for a session, but these are not critical for the domain.