# Forgeprint MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.forgeprint%2Fforgeprint
Registry id: `mcp-registry/io.github.forgeprint/forgeprint`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "forgeprint-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "forgeprint-mcp"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add forgeprint-mcp-server -- npx -y forgeprint-mcp
```

## Tools (10)

- `compare_blueprints`: Two to four blueprints side by side with what each is not for
- `get_blueprint`: Manifest and files for a slug with resolved option branches
- `get_crew`: One crew: members in full and install commands for a given agent
- `get_expert`: One expert: manifest, SKILL.md, checklists, references, agent paths
- `get_integration`: One install recipe: pinned upstream, command, secrets needed
- `recommend_experts`: At most one crew or three experts for a task with reasons
- `request_blueprint`: A GitHub issue payload when nothing fits (does not file it)
- `resolve`: Returns questions to ask or one blueprint with rationale
- `search_blueprints`: Scored matches with reasons
- `validate_blueprint`: Schema, taxonomy, setup and duplication checks on a draft

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.