@goldhold/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOLDHOLD_API_KEY | Yes | API key from goldhold.ai/account | |
| GOLDHOLD_RELAY_URL | No | Custom relay URL (default: relay.goldhold.ai) |
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 |
|---|---|
| goldhold_searchB | Semantic search across GoldHold memory. Returns ranked results from past sessions. |
| goldhold_storeB | Save a memory to GoldHold. Stored via relay and synced to Pinecone. |
| goldhold_turnB | Compound: search + store + send in one call. The primary tool for most interactions. |
| goldhold_resumeC | Resume a session. Returns recent context, inbox, and capability card. |
| goldhold_batchB | Multiple operations in one request. Each op has a method and params. |
| goldhold_closeB | Graceful session end with summary. Saves state for next session. |
| goldhold_inboxB | Check the GoldHold message inbox. Returns messages from other agents and the owner. |
| goldhold_sendB | Send a message via GoldHold messaging. Recipients: owner, guardian, or agent name. |
| goldhold_statusA | Check GoldHold connection health, sync state, and system info. |
| goldhold_discoverB | List agents, channels, and capabilities in the GoldHold network. |
| goldhold_agentsA | List all agents in the GoldHold network. |
| goldhold_memory_readB | Read a specific memory packet by ID, or browse a folder's contents. |
| goldhold_memory_namespacesA | List all memory folders and their stats (count, last updated). |
| goldhold_task_listA | List open tasks from the GoldHold task queue. |
| goldhold_task_createA | Create a new task in the GoldHold task queue. |
| goldhold_task_completeC | Mark a task as completed. |
| goldhold_task_updateB | Update a task's status, priority, or assignee. |
| goldhold_channelsB | List communication channels available in the GoldHold network. |
| goldhold_profileC | View or update the agent's profile (display name, description, capabilities). |
| goldhold_checkpointA | Save a checkpoint of current working state. Use at natural breakpoints to enable seamless resume. |
| goldhold_focusA | Set the current focus manifest -- what project is active, what matters now, what to ignore. Also creates ASSET_REF records for each ref. |
| goldhold_restoreA | Restore the current working state: latest checkpoint, focus manifest, asset refs, unresolved items, directives, and corrections. Use at session start instead of generic search. |
| goldhold_plan_createB | Create a new plan with PRD, manifest, tasks, facts, and asset refs in one call. Returns plan_slug and task IDs. |
| goldhold_plan_taskC | Manage tasks within a plan: create, start, block, complete, cancel, update, or reorder. |
| goldhold_plan_checkpointC | Save a plan checkpoint with task counts, active refs, and resume hint. |
| goldhold_plan_restoreA | Restore a plan's working state: manifest, checkpoint, tasks, assets, corrections. Use at session start instead of search. |
| goldhold_plan_factB | Record a fact (SSOT) within a plan. Supersedes previous facts on the same topic. |
| goldhold_plan_decisionB | Record a decision within a plan with rationale and impact. |
| goldhold_plan_closeB | Close a plan: writes final checkpoint, outcome fact, and closed manifest. |
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 29 tools
Most tools have distinct purposes (task, memory, plan, session, communication), and prefixes like goldhold_plan_ and goldhold_task_ reduce confusion. However, compound tools like goldhold_turn and goldhold_batch overlap with individual operations, and goldhold_checkpoint vs goldhold_plan_checkpoint could be misselected without close reading.
All tools share the goldhold_ prefix, and most use verb_noun (task_update, memory_read, plan_create). A few are verb-only (store, send, search) or noun-only (agents, inbox, status), but the pattern remains predictable and readable across the set.
With 29 tools, the server exceeds the 'too many' threshold for a coherent set. While the domain is broad (tasks, plans, memory, communication, session), many tools could be consolidated (e.g., goldhold_plan_* variants or session/checkpoint tools) to reduce cognitive load and selection errors.
The tools cover core lifecycles well: task management (create/list/update/complete), plan management (create/task/checkpoint/restore/fact/close), memory (store/read/search/namespaces), and communication (send/inbox). Minor gaps exist like lack of task deletion or a single tool for both checkpoint and restore, but agents can work around these.