MCP tools

Projects are addressed as organization/project and specs by number.

Your agent finds these tools on your organization's MCP server. Inputs followed by ? are optional.

Discovery

ToolInputWhat it does
get_agent_guideprojectCall it first: the SDD workflow for a project with its rules (your role, who approves specs, inherited principles) and the next step of each spec.
list_projects—The projects you can open, as organization/project, with your role.
list_specsprojectThe specs of a project with number, slug, status, branch and document kinds.
get_active_specprojectThe active spec: the non-archived one with the highest number.
project_statusprojectConstitution version, specs and, for the active spec, task progress, next task and markers.

Reading

ToolInputWhat it does
get_documentproject, number, kindThe current body of a spec document (spec, plan, tasks, research or validation) with its revision.
get_constitutionprojectThe project's constitution with its version, combined with inherited principles when there are any.
get_organization_constitutionorganizationThe organization's constitution with its version; organization members only.
get_templatekindThe global template of a document kind (constitution, spec, plan, tasks or validation).
list_gallery_templateskind?, areas?, programmingLanguage?, query?, stacks?The public gallery of constitution and spec templates, filtered by kind, areas, programming language, text and tags.
get_gallery_templateslugA gallery template with its full markdown body.

Writing

ToolInputWhat it does
create_specproject, slugCreates the next spec: assigns its number, status draft and branch name.
put_documentproject, number, kind, body, message, expected_revision?Writes the full body of a spec document as a new revision; pass expected_revision when the document exists.
put_constitutionproject, body, version, message, expected_revision?Writes the project's own constitution as a new revision and version; owners only.
set_spec_statusproject, number, statusMoves a spec between draft, clarified, approved and archived (archiving: owners only).

Tasks and markers

ToolInputWhat it does
list_tasksproject, number, pending_only?The tasks of a spec with malformed lines reported apart and the active claim of each pending task.
claim_taskproject, number, task_idClaims a pending task so no other agent starts it; the claim is a lease.
release_taskproject, number, task_idReleases your claim on a task; project owners can release any claim.
mark_task_doneproject, number, task_id, commitMarks a task done and records the commit on its line as a new revision.
list_markersproject, numberThe NEEDS CLARIFICATION and NEEDS RESEARCH markers across the documents of a spec.

History

ToolInputWhat it does
list_revisionsproject, number?, kindThe revisions of a spec document or of the constitution, newest first.
get_revisionproject, revision_idThe body of one revision, by id.
The server also offers one MCP prompt per SDD phase and the SDD workflow guide as a resource. get_agent_guide adapts the guide to your project, with your role and the next step of each spec.