acheron-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| bridge_save_contextA | Remember something for later. Use this when the user says things like "remember this", "save this", "note this", "keep this for later", "don't forget", or when an important decision, preference, or insight comes up that should persist across conversations. This saves context that will be available in ALL Claude surfaces (Chat, Code, Cowork) — even in future sessions. Use proactively when you recognize something worth remembering: a decision made, a user preference expressed, a lesson learned, a key file identified, or a workflow established. |
| bridge_get_contextA | Retrieve the full details of a previously saved context by its ID. Use this after finding a context via search or list, when the user wants to see the complete content of a specific saved memory. Typically used as a follow-up: "show me that decision", "give me the full details on that one". |
| bridge_search_contextA | Search through everything that has been saved across conversations. Use when the user asks "what did I decide about...", "what do we know about...", "did I save anything about...", "find my notes on...", "what was that thing about...", or any question that might be answered by previously saved context. Also use proactively when the user asks a question that saved context might answer — check before saying "I don't have that information". Searches across all surfaces (Chat, Code, Cowork) and all projects. |
| bridge_list_contextsA | Browse and filter all saved contexts. Use when the user asks "what have I saved?", "show me my decisions", "what do I have for this project?", "list my preferences", "what did we do recently?", "show everything tagged with...", or "what happened in Cowork?". Unlike search (keyword-based), this tool browses by category — filter by project, surface, type, tags, or date. Returns newest entries first. |
| bridge_delete_contextA | Permanently delete a saved context. Use when the user says "forget this", "delete that", "remove that note", "I don't need that anymore", or "that's outdated, remove it". Requires the context ID — use search or list first to find it. |
| bridge_statusA | Show a summary of all saved knowledge: how many contexts are stored, broken down by surface (Chat/Code/Cowork) and type (decisions, preferences, insights, etc.), database size, and date range. Use when the user asks "how much have I saved?", "give me an overview", "what's in my memory?", or "how big is my context database?". |
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 6 tools
Each tool targets a distinct action (save, get, list, search, delete, status) on contexts with no overlap. The descriptions clearly differentiate when to use each.
All tool names follow a consistent pattern: bridge_verb_context (e.g., bridge_save_context, bridge_list_contexts). The verbs are clear and uniform.
Six tools cover the essential operations for a context management system (CRUD plus search and overview) without being excessive or sparse.
The tool set provides create, read, list/ browse, search, delete, and status. An update operation is missing, but contexts may be intended as immutable entries, making the set largely complete.