# vurb.ts — TypeScript Framework for MCP Servers

> vurb.ts scaffolds TypeScript MCP servers with file-based tool routing, optional Prisma/n8n/OpenAPI vectors, and one-command deploy targets.

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

## Quick Use

1. Install / set up:
   ```bash
   npx @vurb/core create my-server
   ```
2. Start / smoke test:
   ```bash
   cd my-server && npm run dev
   ```
3. Verify:
   - Add a simple file under `src/tools/` and confirm the tool name appears (e.g., `users.list`) after restart.

## Intro

vurb.ts scaffolds TypeScript MCP servers with file-based tool routing, optional Prisma/n8n/OpenAPI vectors, and one-command deploy targets.

- **Best for:** TypeScript teams building MCP servers who want a scaffold + routing convention agents can follow
- **Works with:** Node.js + npm, MCP clients, deploy targets like Vercel/Cloudflare (optional)
- **Setup time:** 10 minutes

## 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.

## Source & Thanks

> Source: https://github.com/vinkius-labs/vurb.ts
> License: Apache-2.0
> GitHub stars: 251 · forks: 22

---

<!-- ZH -->

## 快速使用

1. 安装 / 设置：
   ```bash
   npx @vurb/core create my-server
   ```
2. 启动 / 冒烟测试：
   ```bash
   cd my-server && npm run dev
   ```
3. 验证：
   - 在 `src/tools/` 下新增一个简单文件并重启，确认工具名出现（例如 `users.list`）。

## 简介

vurb.ts 是一个 TypeScript 的 MCP server 框架：用文件路由组织工具（tools），可选接入 Prisma/n8n/OpenAPI 等向量，并提供一键部署到多平台的路径。

- **适合谁：** 用 TypeScript 写 MCP server、希望有脚手架与清晰路由约定的团队
- **可搭配：** Node.js + npm、MCP 客户端、可选部署到 Vercel/Cloudflare 等
- **准备时间：** 10 分钟

## 实战建议

- 文件路由把 `src/tools/<命名空间>/<文件>.ts` 映射为 `<命名空间>.<文件>` 工具名
- 脚手架支持多种向量/目标（vanilla、Prisma、n8n bridge、OpenAPI→MCP）
- GitHub stars / forks（已核验）：见「来源与感谢」

让 MCP server 可维护的关键是：让“工具面（tool surface）”可预测。

Vurb 的约定很直接：**工具就是文件**。因此：

- diff 一眼能看出哪些工具变了；
- Agent 也更容易按命名空间/文件名生成新工具；
- 审查者只看 `src/tools/` 就能判断改动范围。

给团队做 server 的推荐节奏：

1. 先用 vanilla 脚手架；
2. 一次只加一个命名空间（billing/users/docs）；
3. 护栏写在你自己的代码里：校验 schema、做 allowlist、写操作要显式。

当你需要快速覆盖大量接口时再走 OpenAPI 生成路径，但生成后的工具面仍建议走人工审查。

### FAQ

**它是 MCP server 还是框架？**
答：它是框架 + 脚手架，用来构建并部署 MCP server。

**工具名怎么决定？**
答：按文件路由：目录作为命名空间，文件名作为工具名，组成 `<ns>.<name>`。

**能部署到 Serverless 吗？**
答：可以，README 给出了 Vercel/Cloudflare 等目标平台路径。

## 来源与感谢

> Source: https://github.com/vinkius-labs/vurb.ts
> License: Apache-2.0
> GitHub stars: 251 · forks: 22


---
Source: https://tokrepo.com/en/workflows/vurb-ts-typescript-framework-for-mcp-servers
Author: MCP Hub