cwi-mcp-server
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ledger_state_versionA | Read-only: Gear Ledger version summary (version number, updated_at, repo sha, task count, agent count). No arguments. On machines without the CWI ledger CLI, reads the public CWI gear-ledger repo (no auth, read-only). |
| ledger_state_getA | Read-only: full Gear Ledger state.json document (agents, tasks, presence, handoffs, approvals). Optionally pass |
| ledger_agentsA | Read-only: Gear Ledger agents with their latest presence heartbeat merged in (status, last seen, current task, note). No arguments. On machines without the CWI ledger CLI, reads the public CWI gear-ledger repo (no auth, read-only). |
| ledger_tasksA | Read-only: list Gear Ledger tasks (summaries). Optionally filter by |
| ledger_task_getA | Read-only: full detail of one Gear Ledger task by task_id (including state history and artifacts). On machines without the CWI ledger CLI, reads the public CWI gear-ledger repo (no auth, read-only). |
| trust_verdictA | Score agent trust with the CWI Verdict Engine v1.0.0 (deterministic, evidence-bound). Pass |
| needledrop_verifyA | Verify-only: check the hash-chain integrity of a NEEDLE DROP placement ledger (cwi-needledrop/v1). Recomputes every entry hash, checks prev_hash linkage, chain head, and revision-note consistency. Tampered or corrupt ledgers fail. No signing, no sealing — verification only. Defaults to the vendored example ledger (vendor/needledrop/example-ledger.json); pass an absolute |
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 7 tools
Each tool has a distinct purpose: ledger_state_get returns the full state document, ledger_agents and ledger_tasks are specialized views, ledger_task_get is a detail lookup, and trust_verdict/needledrop_verify cover different verification domains. The only mild ambiguity is that ledger_state_get can also reach agents/tasks via its fields argument, but descriptions make the specialized tools clearly preferable for those cases.
The ledger tools share a useful `ledger_` prefix and snake_case, but verb placement is inconsistent: some names end with `_get` (ledger_state_get, ledger_task_get), others are bare nouns (ledger_agents, ledger_tasks), one is a noun phrase (ledger_state_version), and the non-ledger tools use different forms (trust_verdict, needledrop_verify). The convention is readable but not predictable enough to infer tool names without reading descriptions.
Seven tools is a well-scoped set for this server. It provides the core read-only ledger views, a task detail endpoint, the state version, plus two specialized verification/scoring tools without unnecessary redundancy.
The read-only ledger surface covers the main entities: full state, agents with presence, task summaries, and task detail, plus a version endpoint. The main gap is that handoffs and approvals are only reachable through ledger_state_get rather than dedicated tools, but agents can work around that by requesting the full state or selecting fields.