I will build a production mcp server connecting claude to your API or database

F
fabi_ai_labs
F
fabi_ai_labs
Fabi

About this gig

Most MCP servers on the internet are demos. They run on a laptop, they fall over when an agent calls them forty times in a row, and they hand the model a raw stack trace when something fails.


I build the other kind.


What you get:

Current MCP spec, stdio and streamable HTTP, so it works in Claude Desktop, Claude Code, Cursor, or your own client

Typed tools with schema validated inputs, so the model cannot call them wrong

Real error handling: rate limits, retries, timeouts, failures the model can reason about

Safety boundaries on destructive actions, with confirmation gates where they belong

Auth done properly, OAuth or API key, secrets never in the tool payload

Tests, a README your team can follow, and deployment


Connects to REST and GraphQL APIs, Postgres, Supabase, internal services, or a mix.


TypeScript or Python. You get the source, no lock-in.


I have shipped this. uiverse-mcp serves 3,802 UI components to agents in production, it is in my portfolio.


Tell me what you want the agent to be able to do and I will tell you straight whether it is a three tool job or a real build.

Get to know Fabi

Fabi

Software engineer building production MCP servers and AI systems

  • FromGermany
  • Member sinceApr 2026
  • Avg. response time1 hour
  • Languages

    German, English
Hey, I'm Fabi. Software engineer. I build production MCP servers that connect Claude and other LLMs to real APIs, databases, and internal tools. Typed, schema validated, both transports implemented, with the safety boundaries that stop an agent doing something expensive. Beyond MCP: TypeScript, Next.js, Postgres, self-hosted infrastructure. I built and run Lucid, my own AI companion with persistent memory and a health engine, and I ship client systems solo in days, not quarters. Tell me what you need built.

My Portfolio