// MCP TOOL REFERENCE

SPEC-DRIVEN DEVELOPMENT MCP SERVER TOOLS

9 tools from the Spec-driven Development MCP Server MCP Server, categorised by risk level.

View the Spec-driven Development MCP Server policy →
// ALL 9 SPEC-DRIVEN DEVELOPMENT MCP SERVER TOOLS
READ 3 tools
Read spec_coding_design_start Start the design documentation phase and provide guidance for creating design documents Read spec_coding_requirements_start Start the requirements collection phase and provide guidance for requirements gathering Read spec_coding_tasks_start Start the task planning phase and provide guidance for creating the task list
WRITE 3 tools
Write spec_coding_design_confirmed Confirm the completion of the design document and proceed to the task planning phase Write spec_coding_requirements_confirmed Confirm the completion of requirements collection and proceed to the design phase Write spec_coding_goal_confirmed Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collectio...
EXECUTE 3 tools
Execute spec_coding_execute_start Start the task execution phase and provide guidance for task execution Execute spec_coding_tasks_confirmed Confirm the completion of task planning and proceed to the execution phase Execute spec_coding_workflow_start Start the specs workflow and begin the goal collection phase

Route Spec-driven Development MCP Server through PolicyLayer and every one of its 9 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the Spec-driven Development MCP Server MCP server have? +

The Spec-driven Development MCP Server MCP server exposes 9 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Spec-driven Development MCP Server tools? +

Route the Spec-driven Development MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Spec-driven Development MCP Server tools fall into? +

Spec-driven Development MCP Server tools are categorised as Read (3), Write (3), Execute (3). Each category has a recommended default policy.

Enforce policy on every Spec-driven Development MCP Server tool call.

Start from Spec-driven Development MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.