Renato Marinho

How are you building your MCP Servers? We open-sourced our framework — would love to compare notes

by

MCP adoption is moving fast. But every time I talk to developers, the story is the same: duct tape, custom wrappers, and zero governance out of the box.

We got tired of that and built Vurb.ts — an open-source TypeScript framework designed specifically for production-grade MCP servers. MVA architecture, type-safe tools, Presenter layer, middleware pipeline. Deploy to the global edge in 4 seconds.

Building an MCP server with it looks like this:

npx vurb create my-server

# write your tools

vurb deploy → live in 4 seconds

9 governance modules ship by default — V8 sandbox isolation, zero-trust DLP, SSRF-hardened egress, stateful sessions, token economics, full observability. Zero config.

But I'm genuinely curious how others are doing it:

→ Rolling your own from scratch?

→ Using the official SDK and fighting with infra?

→ Skipping code entirely and going OpenAPI spec?

Would love to hear what's working and what's been painful. Happy to share everything we learned building this.

Framework is Apache 2.0 and free forever → github.com/vinkius/vurb

5 views

Add a comment

Replies

Be the first to comment