hypernmnesia-mcp-viz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | The URL of the shared Cortex PostgreSQL database. Defaults to postgresql://127.0.0.1:5432/cortex. | |
| CORTEX_VIZ_NO_DB | No | Skip the database probe entirely. When Cortex's database isn't reachable, the server starts in no-DB mode automatically. Set CORTEX_VIZ_NO_DB=1 to skip the probe. |
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 |
|---|---|
| open_visualizationA | Open the bundled Cortex visualization in the user's default browser — a force-directed neural graph combining methodology profiles, memory nodes, and the knowledge graph, plus the Wiki, Atlas, Emotion, Board, Pipeline, and Knowledge views. Starts the local HTTP server on 127.0.0.1:3458 if not already running and auto-shuts-down after 10 minutes of idle. Use this for visual exploration, screenshots, or presenting Cortex state. Distinct from |
| get_methodology_graphA | Build the methodology map as JSON graph data {nodes, edges, meta} suitable for force-directed visualization. Nodes: domains, concepts, memories, entities. Edges: cross-domain bridges, co-activation strengths, semantic relationships. Output is capped (200 nodes / 500 edges, highest-quality first) so the payload stays embeddable in a single MCP response. Use this to feed a CUSTOM client visualizer. Distinct from |
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 2 tools
The two tools are unmistakably distinct: one launches the bundled browser visualization with side effects, the other returns JSON graph data for a custom client. The descriptions even provide explicit contrasts, so an agent should not confuse them.
Both names follow the same lowercase snake_case verb_noun pattern: open_visualization and get_methodology_graph. The verb choice maps cleanly to each tool's behavior (open vs. get).
Two tools is at the thin end of the scale, though each is broad and covers a distinct access path (human-facing UI vs. JSON data). The descriptions reference list_domains and get_causal_chain, which are not exposed here, making the set feel like a slice of a larger system.
The core visualization workflows are covered: launch the full browser UI and fetch the methodology graph as JSON for a custom client. Minor gaps include no JSON endpoints for the other bundled views and no explicit stop/status API, though auto-shutdown mitigates the latter.