NPM · NPX · create-shapemcp-server · shapemcp.com
Create MCP Servers in Seconds
Official CLI for ShapeMCP. Scaffold a typed, Claude-ready MCP server with Streamable HTTP, legacy SSE, or stdio — aligned with the visual builder at https://shapemcp.com/mcp. Export a ZIP from the UI or pull the same config via this package; the CLI defaults to https://shapemcp.com for --from-shapemcp token resolution.
npx -y create-shapemcp-server my-appOr install with npm, then run the CLI:
npm install -g create-shapemcp-servernpm install create-shapemcp-serverAfter npm install -g create-shapemcp-server, run create-shapemcp-server my-app. After a local npm install create-shapemcp-server, use npx create-shapemcp-server my-app. Package name on npm is create-shapemcp-server (unscoped create-mcp-server was already taken). Override the API origin with --shapemcp-api or SHAPEMCP_API.
Why use the CLI
Auto scaffolding
Full project layout: modular tools, AJV validation, transports, and npm scripts (dev, build, start).
Tool schema support
JSON Schema on each tool is validated at runtime and mapped to Zod for MCP registration.
Claude-ready
Uses the official TypeScript SDK — stdio for desktop hosts, HTTP/SSE for remote deployments.
UI ↔ CLI sync
Share links from https://shapemcp.com resolve to the same manifest as the ZIP export, including mcp.nodes.json for round-trip with the builder.
Run locally
# Either: npx -y create-shapemcp-server fraud-agent # Or (global): npm i -g create-shapemcp-server then: # create-shapemcp-server fraud-agent cd fraud-agent npm install npm run dev
Default transport is chosen in the wizard, or pass flags (see below). npm run dev runs the server with tsx in watch mode.
Flags
npx -y create-shapemcp-server my-app --template advanced npx -y create-shapemcp-server my-app --from-shapemcp "https://shapemcp.com/api/mcp-config/v1...." npx -y create-shapemcp-server my-app --config ./mcp.json npx -y create-shapemcp-server my-app --config-url https://example.com/mcp.json npx -y create-shapemcp-server my-app --shapemcp-api https://shapemcp.com
--shapemcp-api defaults to https://shapemcp.com so short tokens from the UI work without extra flags. Long tokens use https://shapemcp.com/api/mcp-config?p=….
Build in UI → Export → Run locally
What you get
server/ tools/ # one module per tool (+ optional example) resources/ # README + your shared resource helpers prompts/ # README + your shared prompt modules transports/ # http.ts, sse.ts, stdio.ts validation/ # AJV helper create-server.ts # registers tools, resources, prompts index.ts # entry — picks transport from MCP_TRANSPORT mcp.config.json mcp.nodes.json package.json tsconfig.json README.md .env.example