forgespec-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGESPEC_DB | No | Full database path | ~/.forgespec/forgespec.db |
| FORGESPEC_DIR | No | Database directory | ~/.forgespec |
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 |
|---|---|
| forgespec_capabilitiesC | Negotiate ForgeSpec coordination mode, schemas, independently versioned features, and limits. |
| forgespec_healthA | Get server health diagnostics, database integrity status, system time, active leases, and version telemetry. |
| tb_audit_logA | Query historical audit trail of authority grants, revocations, and approval decisions. |
| sdd_validateA | Validate an SDD contract against the phase schema. Returns validation result with confidence check and allowed transitions. |
| sdd_saveB | Validate and persist an SDD contract. Records the phase transition for project traceability. |
| sdd_historyA | Get the SDD phase history for a project. Shows all contract transitions in chronological order. |
| sdd_getA | Get a single SDD contract by ID. Returns full contract data. |
| sdd_listA | List all SDD contracts with optional filters by project and phase. |
| tb_create_boardA | Create a new task board for a project. Optionally include tasks inline to create board + all tasks in a single atomic call (avoids N separate tb_add_task calls). |
| tb_add_taskB | Add a task to an existing board. Every task should reference a spec and have acceptance criteria. |
| tb_statusB | Get the current status of a task board with all tasks grouped by status. |
| tb_claimB | Claim a task for execution. Only claims tasks in 'ready' status with all dependencies resolved. |
| tb_set_dependenciesB | Atomically replace a direct-v1 task's normalized same-board dependency set. |
| tb_heartbeatC | Renew an active direct-v1 task attempt lease. |
| tb_recover_claimsB | Recover expired direct-v1 attempts. Tasks require explicit requeue afterward. |
| tb_requeueC | Explicitly requeue a recovered direct-v1 task. |
| tb_approveA | Record an immutable direct-v1 approval decision with asserted provenance for a declared task gate. Asserted provenance is not authentication. |
| tb_grantA | Create an attenuated, expiring task-authority grant. Requires exact task-authority@1.0.0 negotiation. |
| tb_handoffC | Create a reference-only attenuated handoff. Requires exact task-authority@1.0.0 negotiation. |
| tb_revokeA | Append an authority revocation without changing board ownership. Requires exact task-authority@1.0.0 negotiation. |
| tb_queryD | Query a stable, bounded, authorized direct-v1 task snapshot. |
| tb_batch_statusC | Query bounded direct-v1 task status summaries for recovery without messaging. |
| tb_eventsC | Query authorized immutable direct-v1 event deltas in stable revision order. |
| tb_updateA | Update a task's status and/or append notes. Moving to 'done' requires 'in_progress' or 'in_review'. Notes are stored as timestamped entries. |
| tb_unblockedB | List all tasks that are ready to be worked on (no unresolved dependencies). |
| tb_getA | Get full details of a single task by ID. |
| tb_list_boardsA | List task boards, optionally filtered by project. With actor plus direct-v1 context (coordination_mode/api_version/schema_version 1.0.0), also lists direct-v1 boards the actor owns or holds an active grant on. Use this to discover board IDs after context loss. |
| file_reserveA | Reserve files or glob patterns to prevent conflicts between agents. Use check_only=true to check for conflicts without reserving. Reservations expire after TTL. |
| file_releaseB | Release file reservations held by an agent. |
| file_renewB | Renew an active direct-v1 file lease with matching task-attempt authority and revision. |
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 30 tools
Many tools share the tb_ prefix and cover overlapping task/status surfaces (tb_status, tb_batch_status, tb_query, tb_unblocked, tb_get), but descriptions generally carve out distinct purposes: current board status, batch recovery summaries, direct-v1 snapshots, ready work lists, and individual task detail. The authority and recovery tools are also distinguishable, though the high number of task-query variants still leaves real room for mis-selection.
The set consistently uses snake_case domain prefixes (tb_, file_, sdd_, forgespec_), which helps, but the action structure is mixed. Some names are verb+object, while others are bare states or nouns like tb_status, tb_heartbeat, and tb_unblocked, making the surface less predictable than a uniform verb_noun pattern.
At 30 tools, this server is past the 25-tool threshold and packing several separate concerns—task boards, file reservations, SDD contracts, authority grants, audit, health, and capabilities—into one surface. Each tool may serve a purpose, but the aggregate surface feels heavy and harder to navigate for an agent.
The main workflows appear broadly covered: task boards have create/add/update/status/dependency/claim/recovery support; SDD docs have validate/save/get/list/history; and file reservations have reserve/release/renew. Minor gaps, like no explicit board archive/delete or no direct reservation listing, may be intentional for audit-oriented design and agents can work around them.