MCP Server & Tools
105 MCP tools across 8 categories, Core, LiveGuard, Watcher, Crucible, Tempering, Bug Registry, Testbed, Forge-Master, plus REST API, WebSocket hub, telemetry, and cost tracking. The integration layer.
MCP (Model Context Protocol) is a standard that lets AI agents call functions. When Copilot needs to run a plan, check costs, or scan for secrets, it calls the MCP server, which executes the command and returns structured results. MCP is the API layer between your AI agent and Plan Forge's capabilities.
Architecture
A single Node.js process runs three subsystems, the nervous system that lets all your tools talk to each other:
105 MCP tools across 8 categories (Core, LiveGuard, Watcher, Crucible, Tempering, Bug Registry, Testbed, Forge-Master) exposed via Model Context Protocol. Copilot, Claude, Cursor call these as function calls.
Dashboard UI, REST API, static files. ~100 endpoints for programmatic access.
Real-time events. Dashboard subscribes for live slice progress.
In This Chapter
This chapter is split across three pages for clarity:
Starting the server, VS Code auto-start, and the essential tools every Forge user needs: forge_capabilities, forge_run_plan, forge_plan_status, forge_smith, and more.
Complete tool tables for all 8 categories (105 tools), REST API endpoints, WebSocket hub events, OTLP telemetry, cost tracking, SDK, and API key configuration.
forge_capabilities before anything else, it returns the full live API surface including tool schemas, config options, available extensions, and per-tool error codes. Always authoritative.
📄 Full reference: capabilities, EVENTS.md on GitHub, tools.json on GitHub