vurb.ts — TypeScript Framework for MCP Servers

Practical Notes

• File-based routing maps src/tools/<ns>/<file>.ts → <ns>.<file> tool names
• Scaffolds multiple vectors/targets (vanilla, Prisma, n8n bridge, OpenAPI → MCP)
• GitHub stars/forks (verified): see Source & Thanks

The fastest way to make an MCP server maintainable is to make its tool surface predictable.

Vurb’s convention is simple: tools are files. That means:

• Your repo diff shows exactly what tools changed.
• Agents can generate new tools in the right place (namespace + file name).
• Reviewers can reason about blast radius by looking at src/tools/.

If you’re building a server for a team:

1. Start with the vanilla scaffold.
2. Add one namespace at a time (billing/users/docs).
3. Put guardrails in your own code: schema validation, allowlists, and explicit write operations.

Use the OpenAPI generator path when you need wide coverage fast, but keep human review for the generated surface area.

FAQ

Q: Is this an MCP server or a framework? A: It’s a framework + scaffold to build and deploy MCP servers.

Q: How are tool names decided? A: By file routing: namespace folders and filenames become <ns>.<name> tools.

Q: Can I deploy to serverless? A: Yes — the README lists targets like Vercel and Cloudflare workflows.