What is Bridgent AI?
Bridgent AI turns the definitions you already have into production-ready MCP servers. Bridgent AI ships four source paths today:
- OpenAPI 3.x specs
- Prisma 6.x schemas
- Drizzle tables
- Hand-written Zod tools
v0.3 adds a tRPC source adapter. GraphQL remains a later roadmap item.
Once exposed, the resulting server is immediately usable from any MCP host — Claude Code, Codex, Cursor, Gemini CLI, the official Inspector, or anything else that speaks the protocol.
Why does this exist?
Writing an MCP server from scratch means learning the SDK, designing JSON schemas, threading auth, and shipping a binary. For most teams the value/effort tradeoff is poor — so they don't ship one, and their data stays invisible to AI agents.
Bridgent AI collapses the effort to zero by reusing the schema you already have:
| You already have | Bridgent AI gives you |
|---|---|
prisma.schema | find / findMany / aggregate / count tools, read-only by default, with optional audited writes |
openapi.json | One MCP tool per operation, read-only by default, with Bearer and API-key auth support |
| Zod schema + function | A complete MCP server, packaged for npm |
| Drizzle tables | Read-only findMany tools with row caps |
| tRPC router | One MCP tool per query procedure, with mutation tools hidden unless allowlisted |
What Bridgent AI is not
- Not another LangChain. No prompts, chains, memory, or agent runtime.
- Not a SaaS. Bridgent AI runs locally next to your code.
- Not locked to a single framework, like nestia. Cross-source by design.
Status
Current alpha ships:
- Sources: Zod (hand-written tools), OpenAPI 3.x specs, Prisma 6.x schemas (read-only by default, audited writes opt-in), Drizzle tables (read-only)
- Transports: stdio, Streamable HTTP, runtime-agnostic Web Standard fetch handler
- CLI:
bridgent init,bridgent dev,bridgent serve,bridgent inspect - Cross-host harness verifying any MCP 1.x compliant client can consume the server
Version history: v0.2.0 added bridgent init, OpenAPI API-key auth, and read-only Drizzle tools; @bridgent/source-prisma@0.2.2 added audited Prisma write tools behind explicit allowlists and preview tokens; @bridgent/source-prisma@0.2.3 added JSONL audit helpers and same-process idempotency; @bridgent/source-prisma@0.2.4 adds one-level relation write inputs. v0.3 adds @bridgent/source-trpc, source capability metadata, and inspect-time source/capability hints. Next planned work is local policy enforcement for generated tool surfaces.