Skip to Content
IntegrationsClaude CodeOverview

Claude Code

Connect SpecForge to Claude Code with MCP tools and Agent Teams for autonomous parallel implementation.

Claude Code is SpecForge’s deepest integration. The CLI generates not just MCP configuration, but specialized agents, operational skills, and Agent Teams orchestration — everything Claude Code needs to plan, implement, and validate a specification autonomously.

Other agents get MCP access. Claude Code gets the full stack.

Quick Setup

From the root of your repository:

specforge init

The CLI detects Claude Code and generates:

FilePurpose
.mcp.jsonRegisters the SpecForge MCP server — 22 tools available
CLAUDE.mdAnchors the project context — which SpecForge project and specification this repo is connected to
.claude/skills/Operational skills that teach Claude Code how to use SpecForge MCP tools for planning, implementation, and validation
.claude/agents/Specialized agent definitions for orchestrated parallel implementation via Agent Teams
.specforge/config.jsonProject and specification IDs, Agent Teams configuration

If you already have a .mcp.json with other servers, specforge init merges the SpecForge entry without touching your existing configuration.

✅ Run specforge scaffold --target claude-code to regenerate only the Claude Code files without going through the full init flow.

MCP Configuration

The generated .mcp.json:

{
  "mcpServers": {
    "specforge": {
      "command": "npx",
      "args": ["-y", "@specforge/cli@latest"],
      "env": {
        "SPECFORGE_API_KEY": "your-api-key"
      }
    }
  }
}

Claude Code detects this on next startup. All 22 SpecForge tools become available in conversation.

Available Tools

Once connected, Claude Code has access to the full SpecForge toolkit:

  • Planning — Create and manage specifications, epics, tickets, dependencies, and blueprints
  • Queries — Fetch tickets, get dependency trees, find blockers, view critical paths
  • Implementation — Start work sessions, link commits and PRs, review implementations
  • Reports — Generate progress reports, validate specification completeness

All tools are callable naturally in conversation. Tell Claude Code what you want, and it picks the right tool.

What Makes Claude Code Different

Pipeline: specforge init detects Claude Code, generates config files, enables Agent Teams

Beyond MCP tools, specforge init generates specialized agents, operational skills, and Agent Teams orchestration files — giving Claude Code a complete understanding of the SpecForge workflow without any manual configuration.

Deep dives:

  • Agent Teams → — Parallel implementation with orchestrator, workers, and validators
  • Agents & Skills → — Specialized agent definitions and operational skill protocols

Workflow: Planning + Implementation

A typical workflow using Claude Code with SpecForge:

Planning (conversational):

  1. “Create a new specification for user authentication”
  2. Claude Code calls create_specification
  3. “Decompose this into epics and tickets”
  4. Claude Code runs the planning session, creates structure, links dependencies
  5. “Run the planning review”
  6. Claude Code calls review_planning, shows the score and findings
  7. You refine based on feedback, re-run until the gate passes

Implementation (autonomous):

  1. “Implement the active specification”
  2. Claude Code (with Agent Teams) spawns workers, implements in parallel
  3. You monitor from the dashboard or with specforge status
  4. After all tickets complete, Claude Code runs the implementation review
  5. Address any findings, re-run if needed

The transition from planning to implementation is seamless — same tool, same session, same MCP connection.

Two-phase workflow: conversational planning on the left, autonomous implementation on the right

Manual Configuration

If you prefer to configure manually instead of using specforge init:

# Generate only Claude Code files
specforge scaffold --target claude-code

This creates the MCP config, CLAUDE.md, agents, and skills without the interactive project selection flow.

Next Steps

BlueprintsAgent Teams