We built this because
we needed it.
ZeroMCP is built by the antidrift team. It started as an internal tool to fix our own MCP mess. We open-sourced it because the pain is universal.
The problem we hit
We build antidrift — a workspace that gives AI coding tools full company context. That means MCP connectors. Lots of them. Gmail, Drive, Calendar, Attio, Stripe, GitHub, Jira, Linear, Cloudflare, Vercel, AWS. Eighteen separate packages.
Each one was its own MCP server. Its own dependencies. Its own process. Its own credential handling pattern. Eighteen npm installs. Eighteen config blocks. Eighteen things that could crash, leak memory, or expose secrets.
The codebase was fracturing. Every connector had ~200 lines of boilerplate before a single tool did anything useful. Onboarding a new engineer meant walking them through 18 different server setups. One morning we found 14GB of RAM consumed by orphaned MCP processes.
What we built
We wrote a runtime that replaced all 18 servers with one process. Drop a file in a folder — it's a tool. Credentials injected per directory. Network sandboxed by default. One config. One SIGINT stops everything.
The 262 tools stayed the same. The infrastructure went from 18 packages with 17 dependencies each to one runtime with zero dependencies. The boilerplate went from ~200 lines per connector to 15-30 lines per tool file.
Then we realized: this isn't an antidrift problem. Everyone running MCP servers has this problem. So we made it its own thing.
Why it's independent
ZeroMCP is a separate product with its own repo, its own brand, and its own MIT license. Not a feature of antidrift. Not a framework. Just a runtime that makes MCP tools trivially easy to write and deploy.
We use it inside antidrift as our MCP layer. But you don't need antidrift to use ZeroMCP. You don't need an account. There's no telemetry. It's a tool for developers who are tired of the MCP configuration tax.
Who we are
Reloop Labs, LLC is the company behind antidrift and ZeroMCP. We build tools for teams that work with AI every day — not frameworks that promise autonomy, but workspaces where people do real work with AI in the loop.
We learned the hard way that top-down agent frameworks don't work. We tried it. It failed. What works is giving AI full context about your company and letting automation emerge from that context. That's antidrift. ZeroMCP is the foundation that makes it possible.