Skip to content

MCP Tools

Forgeplan ships with 45 MCP tools that an AI agent can call over the Model Context Protocol (stdio transport).

Start the MCP server:

Terminal window
forgeplan serve

Configure your agent (Claude Code, Cursor, etc.) to connect, then invoke any of the tools listed below.

ToolDescription
forgeplan_exportExport all artifacts and relations to a JSON bundle. Returns the exported data directly for programmatic use, or writes to a file path.
forgeplan_importImport artifacts and relations from a JSON export bundle. Set force=true to overwrite existing artifacts.
forgeplan_initInitialize a new .forgeplan/ workspace. Creates LanceDB tables, config, and artifact subdirectories.
ToolDescription
forgeplan_captureCapture a decision from conversation into a Note or ADR artifact. Auto-detects type: simple decisions become Notes, architectural decisions become ADRs. Requires LLM provider.
forgeplan_generateGenerate an artifact using AI from a natural language description. Requires LLM provider configured in .forgeplan/config.yaml. Supports OpenAI, Claude, Gemini, Ollama, and any OpenAI-compatible endpoint.
forgeplan_newCreate a new artifact from template. Generates a sequential ID (e.g., PRD-001), renders the template, stores in LanceDB, and writes a markdown projection.
ToolDescription
forgeplan_blockedShow blocked artifacts and their unmet dependencies. Only draft artifacts block — deprecated and superseded are considered resolved. Uses structural relations only (based_on, refines, supersedes, contradicts).
forgeplan_getRead a full artifact by ID. Returns all metadata and body content.
forgeplan_graphGenerate a mermaid dependency graph of all linked artifacts. Includes explicit links and parent_epic belongs_to edges.
forgeplan_journalShow decision journal — chronological timeline of ADR, Note, Problem, Solution artifacts with R_eff scores and evidence status.
forgeplan_listList artifacts with optional kind/status filters. Returns ID, kind, status, and title for each artifact.
forgeplan_orderShow artifacts in topological order (dependency order). Returns ordered list, ready/blocked classification, and cycle detection. Uses structural relations only.
forgeplan_progressShow checkbox progress for artifacts. Parses markdown checkboxes (- [ ] / - [x]) and computes completion percentages.
forgeplan_searchSmart search across artifacts: BM25 keyword + optional semantic + graph expansion. Supports filters by kind/status/depth/evidence/since and graph expansion toggle.
forgeplan_sessionShow current methodology session state — phase (idle/routing/shaping/coding/evidence/pr), active artifact, depth, enforcement status. Use this to know where in the workflow you are.
ToolDescription
forgeplan_deleteDelete an artifact from LanceDB and remove its markdown projection file.
forgeplan_linkLink two artifacts with a typed relationship. Valid types: informs, based_on, supersedes, contradicts, refines.
forgeplan_updateUpdate artifact metadata (status, title) and/or body. Re-renders markdown projection after update.
ToolDescription
forgeplan_calibrateSuggest depth level (Tactical/Standard/Deep/Critical) for artifacts based on content analysis. Detects security sections, breaking changes, link count, body complexity.
forgeplan_coverageShow decision coverage per code module — which modules have architectural decisions and which are blind spots.
forgeplan_decayShow evidence decay impact on R_eff scores. Lists artifacts where expired evidence has degraded quality scores, with current vs fresh R_eff comparison.
forgeplan_driftCheck for drifted decisions — affected files that changed after ADR/RFC was created.
forgeplan_estimateEstimate effort for an artifact based on FR and Phase items. Returns multi-grade breakdown (Junior/Middle/Senior/Principal/AI) with confidence scoring.
forgeplan_guardCheck if a methodology phase transition is allowed. Use before performing actions to avoid blocked operations. Example: can I go from ‘shaping’ to ‘coding’? Returns allowed=true/false with reason.
forgeplan_reviewReview an artifact — run validation and show lifecycle checklist. Shows MUST/SHOULD findings and whether artifact can be activated.
forgeplan_scoreCompute R_eff quality score for an artifact based on linked evidence. R_eff uses the weakest-link principle: score = min(evidence_scores).
forgeplan_staleDetect stale artifacts with expired valid_until dates. Returns the list of expired artifacts with days since expiry.
forgeplan_validateValidate artifact completeness against schema rules. Checks required sections per artifact kind and depth level. Returns structured findings with severity (MUST/SHOULD/COULD).
ToolDescription
forgeplan_activateActivate an artifact (draft → active). Requires all MUST validation rules to pass.
forgeplan_deprecateDeprecate an artifact (active → deprecated) with a reason.
forgeplan_supersedeSupersede an artifact (active → superseded). Creates link to replacement and notifies dependents.
ToolDescription
forgeplan_decomposeDecompose a PRD into RFC tasks using AI. Analyzes functional requirements and suggests 3-7 RFCs with titles, descriptions, scope, and dependencies. Requires LLM provider.
forgeplan_reasonAnalyze an artifact using FPF ADI reasoning cycle: Abduction (3+ hypotheses) → Deduction (evaluate each) → Induction (synthesize recommendation). Requires LLM provider.
forgeplan_routeSuggest depth level (Tactical/Standard/Deep/Critical) and artifact pipeline for a task description. Uses LLM classification (Level 1) when API key is configured, falls back to rule-based keywords (Level 0).
ToolDescription
forgeplan_blindspotsShow blind spots — decisions (PRD/RFC/ADR/Epic) without linked evidence, and orphan artifacts with no connections.
forgeplan_healthShow project health dashboard — gaps, risks, blind spots, orphans, stale evidence, and recommended next actions. No LLM needed.
forgeplan_statusShow project status dashboard — total artifacts, counts by kind and status.
ToolDescription
forgeplan_fpf_checkCheck which FPF rules match a given artifact, showing all matched rules, the winning rule (first in priority order, same as runtime), and rules that did not match. Use this to understand FPF engine behavior for a specific artifact before acting on it.
forgeplan_fpf_listList all available FPF (First Principles Framework) sections in the knowledge base.
forgeplan_fpf_rulesList active FPF rules from the workspace. By default returns all rules with full condition trees and messages. Parameters allow filtering: action (EXPLORE/INVESTIGATE/EXPLOIT) to show only rules for that action category; name to fetch a single rule by name; summary: true to return only name/priority/action without condition details (useful for quick overviews); source (config/default) for debugging which rule source is active. If workspace has user-defined rules in .forgeplan/config.yaml under fpf.rules, those take precedence; otherwise built-in defaults are returned.
forgeplan_fpf_searchSearch FPF (First Principles Framework) knowledge base. Default is keyword search. Pass semantic: true for vector similarity search via BGE-M3 embeddings (requires the semantic-search build feature). When semantic: true but the feature is not compiled in, the query gracefully falls back to keyword search and the response includes a warning field. Note: the first invocation with semantic: true may take 10–30 seconds if the BGE-M3 model needs to be downloaded (~150MB). Params: query (required, 1..=8192 chars), limit (default 5, max 50), semantic (default false).
forgeplan_fpf_sectionGet full content of a specific FPF section by ID (e.g. ‘B.3’, ‘C.2.2’, ‘A.1’).
ToolDescription
forgeplan_discover_completeComplete a discovery session. Generates a summary report with findings per phase/tier, runs forgeplan health, and marks the session as completed.
forgeplan_discover_findingReport a discovery finding. The agent calls this after analyzing a file/module/git-log during a phase. ForgePlan creates an artifact (note/prd/rfc/problem/evidence) with the finding content, tags it with the source tier, and links it to the discovery session.
forgeplan_discover_startStart a brownfield discovery session. Returns a structured protocol (7 phases: detect/structure/code/git/tests/docs/synthesize) that the AI agent follows to map an existing codebase. ForgePlan provides the protocol; the agent parses code and reports findings via forgeplan_discover_finding.