Main
- Start with stdio transport for local clients, then switch to HTTP streaming when you need remote access and better large-payload handling.
- Use
inspectearly—debugging tool schemas and outputs is cheaper than iterating via full agent runs. - Leverage built-ins listed in README (sessions, request IDs, auth, CORS, health checks) to avoid rolling your own scaffolding.
Source-backed notes
- README shows
npm install fastmcpand provides a minimal server Quickstart withaddTool(...)+start(...). - README lists a CLI for testing/debugging, including
npx fastmcp dev ...andnpx fastmcp inspect .... - README documents remote options like HTTP streaming and stateless mode for serverless deployments.
FAQ
- Is it an SDK replacement?: No—README says it’s built on top of the official MCP SDK and wraps common patterns.
- Can I run it remotely?: Yes—README includes HTTP streaming transport and related options for remote access.
- What should I validate first?: Tool schemas and outputs via
inspect, then client connectivity, then auth/headers.