@unihodl/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIHODL_API_KEY | Yes | Your API key for UNIHODL. Use 'uh_test_sandbox_demo_key_v0' for sandbox testing. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resumeA | Fetch a UNIHODL session as Resume Context — the human's open tabs, scroll positions, video timestamps, AI-tagged decision thread, partial conclusions, and intended next step. Read-only and idempotent: it never modifies the session. Use it when you have a session_id (from list_sessions or the user) and need the human's working context before continuing their task; to discover sessions instead, use list_sessions. Returns a prompt-ready text block by default, or the raw Resume Context object with format 'json'. Errors: a malformed session_id is rejected before any network call; an unknown, expired, or revoked session returns an error message stating the reason. |
| list_sessionsA | List sessions in the workspace the configured API key can read, newest first, with cursor pagination. Read-only, no side effects. Returns {sessions: [{session_id, title, summary, captured_at, ai_tags}], next_cursor}. Pass any session_id to the resume tool for the full context; pass next_cursor back as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Demo session — GraphQL migration | Sandbox session showing the full Resume Context shape. |
TDQS
Scored across 2 tools
Each tool has a clear, distinct purpose: list_sessions discovers available sessions, while resume fetches details of a specific session. There is no overlap or ambiguity between them.
Both tools follow a verb_noun pattern (list_sessions, resume), though 'resume' is a single verb without an explicit noun. The naming is mostly consistent and readable.
With only 2 tools, the server is on the lower end of reasonable scope. It covers the basic read operations for sessions but feels minimal; additional tools like searching or filtering might be expected.
The server provides essential read functionality (listing and resuming sessions) but lacks any mutation operations or advanced filtering, leaving notable gaps for full session management.