Skip to Content
QuickstartInstall CLI

Install CLI

Set up the SpecForge CLI, authenticate, and connect your repository to your project.

The CLI bridges your local environment with the SpecForge platform. It connects the project you created in the webapp (or the terminal) with the coding agent you work with daily.

Install

Run directly with npx — no global install required:

npx @specforge/cli@latest

✅ Create a shell alias for convenience: alias specforge="npx @specforge/cli@latest"

Authenticate

specforge login

This opens your browser for authentication. Once authorized, credentials are stored locally.

Working on a remote server without a browser? Use your API key directly:

specforge login --api-key sf_live_...

Initialize Your Project

Run specforge init at the root of your repository:

specforge init

The interactive setup walks you through project and specification selection. But the real value is what it generates.

SpecForge detects which coding tools you have installed and generates the right configuration for each one.

For Claude Code, it generates:

  • .mcp.json — registers the SpecForge MCP server (22 tools available)
  • CLAUDE.md — anchors the project context so Claude Code knows which SpecForge project and specification it’s working on
  • .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

For Cursor and VS Code with Copilot:

  • .mcp.json — same MCP server registration
  • AGENTS.md — agent instructions adapted for the editor’s agent mode

For Gemini CLI, Codex CLI, OpenCode:

  • Their native config formats (.gemini/settings.json, .codex/config.toml, opencode.json)
  • AGENTS.md — universal agent instructions

One command. Every tool configured. Your coding agent gains access to the full SpecForge toolkit without learning anything new.

💡 Already have a .mcp.json with other servers? specforge init merges the SpecForge entry without touching your existing configuration.

Verify

specforge doctor

A clean run looks like this:

SpecForge Doctor
  API Key         ✓ authenticated
  MCP Server      ✓ registered in .mcp.json
  Project         ✓ proj_abc123 accessible
  Specification   ✓ spec_xyz789 loaded (3 epics, 14 tickets)
  Agent Config    ✓ CLAUDE.md present
  Git             ✓ clean working tree

All checks passed.

📖 For the full list of CLI commands and flags, see CLI Commands Reference. For detailed configuration options, see Configuration Schema.

Next Steps

Your terminal is connected. Now let your coding agent implement the specification autonomously.

Next: Autonomous Implementation →

First SpecificationAutonomous Implementation