Practical Notes
A minimal, reliable path is: build one FastMCP server with 1–2 tools, run it in dev mode, then validate with the official inspector. Only after that, add auth/env handling and move to HTTP transports. If you’re using Claude Code, prefer explicit install steps and keep tool inputs narrow and typed.
Safety note: Don’t expose unconstrained exec/file tools over HTTP without an allowlist and auditing; MCP transports are powerful by design.
FAQ
Q: Is this only for servers? A: No. The SDK supports both building servers and writing MCP clients that connect to servers.
Q: Which transport should I pick? A: Use stdio for local tools, and Streamable HTTP for production-like deployments; SSE is also supported.
Q: Do I need uv?
A: No. uv is recommended in docs, but pip works too (pip install "mcp[cli]").