mcp-anything

MCP-Anything

One command to turn any codebase into an MCP server. Not just REST APIs. Not just OpenAPI specs.

Get started

pip install mcp-anything

# Generate an MCP server from any codebase
mcp-anything generate /path/to/your/app

# Or from a URL (OpenAPI, GraphQL, gRPC spec)
mcp-anything generate https://api.example.com/openapi.json

# Or directly from a local spec file
mcp-anything generate ./openapi.json

You get a complete, pip-installable MCP server in ./mcp-<name>-server/. Add it to your agent in seconds:

stdio (local, default): add mcp.json to your Claude Code .mcp.json:

{
  "mcpServers": {
    "my-app": { "command": "mcp-my-app", "args": [] }
  }
}

HTTP (remote/shared, recommended): start the server and point your agent at it:

mcp-anything generate /path/to/app --transport http
mcp-my-app  # server runs on http://localhost:8000/sse

{
  "mcpServers": {
    "my-app": { "url": "http://localhost:8000/sse" }
  }
}

Use inside Claude Code

Prefer to run mcp-anything from inside your Claude Code session? Install the plugin from the built-in marketplace:

/plugin marketplace add Type-MCP/mcp-anything
/plugin install mcp-anything@type-mcp

Then drive the pipeline with slash commands:

• /mcp-anything:generate <path-or-url> — full 5-phase pipeline
• /mcp-anything:analyze <path-or-url> — detection dry run, no code written
• /mcp-anything:serve <output-dir> — run a generated server directly
• /mcp-anything:status <output-dir> — inspect a pipeline manifest

The plugin wraps the mcp-anything CLI, so the pip install mcp-anything step above is still required — the slash commands will remind you if the binary is missing from PATH.

Targets

By default, mcp-anything generates a Python / FastMCP server. Use --target=mcp-use to generate a TypeScript / mcp-use server instead:

mcp-anything generate /path/to/app --target mcp-use

The TypeScript server uses the mcp-use SDK and ships with a built-in inspector.

	--target fastmcp (default)	--target mcp-use
Language	Python	TypeScript
SDK	FastMCP	mcp-use
Transport	stdio / HTTP	HTTP (port 3000)
Inspector	External	Built-in at /inspector
Install	pip install -e .	npm install && npm run dev

What's supported

mcp-anything detects and wraps source code across 8 ecosystems — REST frameworks, CLI tools, API specs, and protocol-based services.

Ecosystem	Framework / Source	Confidence
Python	argparse CLI	0.90
	Click CLI	0.90
	Typer CLI	0.85
	Flask	0.95
	FastAPI	0.95
	Django REST Framework	0.95
Java / Kotlin	Spring Boot (Java + Kotlin)	0.95
	Spring MVC (Java + Kotlin)	0.85
	JAX-RS / Quarkus (Java + Kotlin)	0.90
	Micronaut	0.90
JavaScript / TypeScript	Express.js	0.95
Go	Gin	0.95
	Echo	0.95
	Chi	0.95
	Fiber	0.95
	gorilla/mux	0.90
	net/http	0.85
Ruby	Rails	0.95
Rust	Actix-web	0.95
	Axum	0.95
	Rocket	0.95
	Warp	0.90
API Specs	OpenAPI 3.x / Swagger 2.x	0.88
	GraphQL SDL	0.95
	gRPC / Protobuf	0.95
Protocol / IPC	WebSocket (JSON-RPC)	0.85
	MQTT / paho-mqtt	0.90
	ZeroMQ	0.90
	XML-RPC / raw socket	0.90
	D-Bus	0.90

Pass a URL directly for API specs: mcp-anything generate https://api.example.com/openapi.json

---

Scoping: control what gets exposed

Large codebases can have hundreds or thousands of endpoints. You don't want all of them as MCP tools. Three mechanisms let you control scope:

Quick filter with --include / --exclude:

# Only expose /api/v2 endpoints
mcp-anything generate ./my-app --include "/api/v2/*"

# Exclude internal and debug routes
mcp-anything generate ./my-app --exclude "/internal/*" --exclude "debug_*"

Review mode — curate before generating:

# Step 1: analyze and pause
mcp-anything generate ./my-app --review

# Step 2: edit the generated scope.yaml (enable/disable per capability)
vim mcp-my-app-server/scope.yaml

# Step 3: resume generation with your curated scope
mcp-anything generate ./my-app --resume