MCP-Forge

Scaffold, extend, install, and distribute MCP servers in seconds.

Generated servers target the official mcp Python SDK 2.x (MCPServer) and the 2026-07-28 protocol revision, and stay compatible with handshake-era clients.

Install

mcp-forge is not on PyPI. The mcp-forge package there is an unrelated project, so install from GitHub:

uv tool install git+https://github.com/iddv/mcp-forge

or

pipx install git+https://github.com/iddv/mcp-forge

Quick Start

# Scaffold a new MCP server project
mcp-forge new my-server
cd my-server

# Add features
mcp-forge add resources prompts annotations

# Package as a Claude Code plugin (with an Agent Skill)
mcp-forge add plugin

# Register in your MCP clients
mcp-forge install

Commands

mcp-forge new <name>

Create a new FastMCP server project with working tests, dependencies, and a ready-to-run example tool.

mcp-forge new my-server
cd my-server

# Install, then run with the MCP Inspector
pip install -e ".[test]"
mcp dev server.py

# Run tests (in-process MCP client, no subprocess)
pytest

mcp-forge add <feature>

Add MCP capabilities to an existing project. Pass one or more features. Adding a feature that is already present does nothing, and features pull in what they depend on (e.g. auth adds http).

mcp-forge add resources completions   # Several at once
mcp-forge add auth                    # Also adds http
mcp-forge features                    # List everything available

mcp-forge install

Register your server in MCP client applications. Auto-detects installed clients or targets a specific one.

# Auto-detect and install in all found clients
mcp-forge install

# Target a specific client
mcp-forge install --client claude
mcp-forge install --client cursor
mcp-forge install --client vscode

Supported Clients

Available Features

Protocol features

Elicitation, sampling and roots use Resolve parameters rather than calling ctx.elicit() directly. That way they work on both stateless 2026-07-28 connections (Multi Round-Trip Requests) and older clients.

Distribution features

Add distribution features after your tools: skill and mcpb record the tools present at generation time. Existing files are never overwritten. Delete a file and re-run add to regenerate it.

Once the project is pushed to GitHub, anyone can install the plugin in Claude Code:

/plugin marketplace add <you>/<repo>
/plugin install <name>@<name>

Use mcp-forge from Claude Code

This repo is itself a Claude Code plugin. Its mcp-forge skill teaches Claude the workflow, the feature catalogue, and SDK 2.x patterns:

/plugin marketplace add iddv/mcp-forge
/plugin install mcp-forge@mcp-forge

Then ask Claude to "build an MCP server that ...", or run /mcp-forge.

Generated Project

my-server/
  server.py           # MCPServer with an example tool
  pyproject.toml       # Dependencies and entry point
  tests/
    test_server.py     # Async tests using an in-process Client
  .env.example
  .gitignore
  README.md

Upgrading from mcp-forge 2.x

mcp-forge 3 generates code for mcp 2.x. Projects created by mcp-forge 2 import mcp.server.fastmcp and declare mcp[cli]>=1.6.0, so a fresh install now resolves mcp 2.x and fails to import. Either pin mcp[cli]>=1.28,<2 in those projects, or migrate them: FastMCP becomes MCPServer from mcp.server.mcpserver. See the SDK migration guide.

Development

git clone https://github.com/iddv/mcp-forge.git
cd mcp-forge
pip install -e ".[test]"
pytest

License

MIT

{
  "name": "mcp-forge",
  "owner": {
    "name": "Ian de Villiers"
  },
  "description": "mcp-forge: build MCP servers with Claude",
  "plugins": [
    {
      "name": "mcp-forge",
      "source": "./",
      "description": "Scaffold, extend, test, and distribute MCP servers with mcp-forge",
      "category": "development"
    }
  ]
}