Tools Reference
SpecForge provides 59 MCP tools organized into 8 streams (A–H). Each stream covers a distinct phase of the SDD workflow.
Stream Overview
| Stream | Tools | Purpose |
|---|---|---|
| A — Configuration | 3 | Project setup, locale, Constitution |
| B — Spec Lifecycle | 11 | Create, update, validate, and package specs |
| C — Analysis & Estimation | 10 | Estimate, reverse-engineer, audit, drift |
| D — Design & Planning | 7 | Schema, UI contracts, ADRs, execution plans |
| E–H — Stack, Dev, Infra & Governance | 28 | Stack, agents, tooling, git, governance |
A — Configuration
These tools are typically run once per project to set up the workspace.
set_locale
Change the active locale for messages and spec templates.
When to use: When your team works in Spanish or Portuguese, or when switching languages for a client engagement.
Prompt: "Set locale to es"init_project
Initialize a project — auto-detects language, framework, architecture, and stores project knowledge.
What it detects:
- Language and framework (TypeScript, Python, Go, Rust, Java, Swift, PHP, Ruby, C#, Dart, etc.)
- Package manager (npm/pnpm/yarn, pip/poetry, go mod, cargo, maven/gradle, etc.)
- Architecture style (Clean Architecture, hexagonal, MVC, CQRS, etc.)
- AI-native patterns (inference mode, LLM orchestration frameworks)
- Frontend performance setup (Core Web Vitals, SSR, MFE boundaries)
- K3s/Nomad workload orchestrators
When to use: First thing you do with a new codebase.
Prompt: "Initialize my project at /Users/me/my-app with specforge"Returns a projectId (e.g., proj_abc123) used in all subsequent commands.
init_constitution
Generate the project Constitution — immutable architectural principles extracted from CLAUDE.md, .cursorrules, or other AI agent config files.
When to use: After init_project, before creating any specs. The Constitution is auto-enforced in create_spec, audit, and detect_drift.
Prompt: "Initialize the constitution for project proj_abc123 from my CLAUDE.md"