While reading the v2 README, I noticed @modelcontextprotocol/fastify is published (packages/middleware/fastify/package.json has "private": false and the same 2.0.0-alpha.2 version as the other middleware packages) but absent from the README in three places:
- Overview (around line 32) — the parenthetical reads "(Express, Hono, Node.js HTTP)"; Fastify is omitted.
- Middleware packages section (around lines 49–52) — the bullet list documents
@modelcontextprotocol/node, /express, and /hono with no /fastify entry.
- Installation (around lines 83–91) —
npm install commands for node, express, and hono, with no fastify line.
The other three middleware packages share the same private: false + 2.0.0-alpha.2 shape and are documented, so this looks like an oversight rather than intentional exclusion. The package already has its own packages/middleware/fastify/README.md.
Happy to send a small docs-only PR adding fastify alongside the other three. Let me know if there's a reason fastify should be excluded from the top-level README at this stage.
While reading the v2 README, I noticed
@modelcontextprotocol/fastifyis published (packages/middleware/fastify/package.jsonhas"private": falseand the same2.0.0-alpha.2version as the other middleware packages) but absent from the README in three places:@modelcontextprotocol/node,/express, and/honowith no/fastifyentry.npm installcommands for node, express, and hono, with no fastify line.The other three middleware packages share the same
private: false+2.0.0-alpha.2shape and are documented, so this looks like an oversight rather than intentional exclusion. The package already has its ownpackages/middleware/fastify/README.md.Happy to send a small docs-only PR adding fastify alongside the other three. Let me know if there's a reason fastify should be excluded from the top-level README at this stage.