Python MCP Server Starter Kit: Pro

WHAT THIS IS

A small Python project you copy and rename to start your own Model Context Protocol server, so Claude Desktop, Claude Code, Cursor and other MCP clients can call your code. It's built on the official mcp Python SDK, version 2.x, which uses MCPServer (the class called FastMCP in v1). It was tested with mcp 2.3.0 on Python 3.13 and needs Python 3.11 or newer.

It isn't a framework or a hosted service. It's readable code with tests, so you skip the first afternoon of wiring and guessing.

WHAT'S IN STANDARD (all included in Pro)

- Example server with 3 tools (one returns typed structured output via a Pydantic model), a static resource, a resource template (notes://{name}) and a prompt

- stdio and streamable HTTP transports, selected by env var or --http flag

- Typed settings with pydantic-settings (MCP_* env vars or .env)

- Logging to stderr only (safe for stdio), optional JSON logs

- Error handling with ToolError / ResourceNotFoundError, so clients get clean messages, not stack traces

- 15 pytest tests: tools, resources and prompts through the SDK's in-memory Client, plus a real stdio subprocess round trip

- ruff config, and the code passes ruff check and ruff format

- README with config snippets for Claude Desktop, Claude Code and Cursor

WHAT PRO ADDS

- Bearer-token auth for HTTP (constant-time check, public /healthz), plus notes on when to move to OAuth

- Production ASGI app run by uvicorn

- Dockerfile (slim, non-root, healthcheck, honours $PORT)

- Deploy recipes and configs for Fly.io (fly.toml), Railway (railway.json) and Google Cloud Run (service.yaml + gcloud steps)

- 2 example servers:

- SQLite query server: schema resource, list_tables, and a SELECT-only query tool opened read-only

- REST API wrapper: timeouts, HTTP errors mapped to tool errors, API-key header, trimmed payloads

- GitHub Actions CI: ruff and pytest on Python 3.11, 3.12 and 3.13, then a Docker build and an auth smoke test

- 27 pytest tests, including real-HTTP tests against uvicorn and mocked REST tests

- License: 1 developer or 1 team in one organization

WHAT A TEST LOOKS LIKE

async def test_add(client):

result = await client.call_tool("add", {"a": 2, "b": 3.5})

assert result.structured_content == {"result": 5.5}

HONEST NOTES

- MCP and its SDK move fast. The kit targets mcp 2.x (pinned >=2.3,<3). If you are on mcp 1.x, this isn't a drop-in fit.

- The Docker image and deploy configs follow each platform's documented format, but they weren't deployed to every platform during testing. The test suite covers the app itself.

- Client config formats occasionally change. The README links you to each client's docs.

FAQ

Do I need to know MCP already? Basic Python and async are enough. The README walks through running, connecting and changing it.

Can I use it for client work? Yes, within your license (Standard: 1 developer; Pro: 1 developer or 1 team).

Refunds? Yes, 14-day refund policy: if the kit isn't useful to you, email within 14 days of purchase for a full refund, no questions asked.

Updates? Re-download from your Payhip library when a new version is posted.

Support: goodspress@mail.grokbot.com