Zod
You haveZod schema + function
Bridgent gives youA complete MCP server, packaged for npm
Skip to content{}Shipped APIShipped DBShipped DRShipped RPCNew · v0.3 GQLRoadmap
v0.3 Alpha — tRPC source is liveOne line to expose
One line to expose
any API as MCP
Turn the definitions you already have — OpenAPI specs, Prisma schemas, Drizzle tables, tRPC routers, Zod functions — into a production-ready Model Context Protocol server, instantly usable in Claude Code, Codex, Cursor and Gemini CLI.
Type-safe to the bone
Zod objects are the tool inputs — the same types flow from your code to the host.
One file, zero config
A server file you can read in one sitting. No YAML, no hidden state, no lock-in.
Runs anywhere
stdio for IDE agents, Streamable HTTP for self-hosting, a fetch handler for the edge.
Live architecture
From schema to running MCP
A live pipeline — every stage of exposing your stack as MCP tools, rendered in real time.
01Connect your sources
Point Bridgent at the definitions you already have — no rewrites, no new schema language.
ZodOpenAPIPrismaDrizzletRPC
0 toolsfrom one GitHub spec — 0 lines of schema
0 toolsfrom a 38-line Prisma schema
0 KBcore bundle · 1 runtime dependency
0 mscold start · TypeScript direct
Sources
You already have the schema
Bridgent reuses it instead of asking you to write another one. Each adapter ships with safety defaults baked in.
OpenAPI 3.x
You haveopenapi.json / yaml spec
Bridgent gives youOne tool per operation · Bearer & API-key auth
Prisma 6.x
You haveschema.prisma
Bridgent gives youfind / findMany / aggregate / count · audited writes opt-in
Drizzle
You haveDrizzle table definitions
Bridgent gives youRead-only findMany tools with row caps
tRPC
You haveExisting tRPC router
Bridgent gives youOne read tool per query procedure · mutations allowlisted
GraphQL
You haveGraphQL schema
Bridgent gives youSchema-driven tool generation
Why Bridgent
Production-ready, not a demo
The boring parts — safety, metadata, transports, verification — are the product.
Safe by default
Read-only defaults, row limits, query timeouts and explicit allowlists keep your data layer in check even when an agent goes off-script.
Tool metadata
Source kind, read/write capability and safety flags travel with every generated tool — for hosts, docs and the inspector.
Audited writes
Prisma writes commit through a two-step dryRun / previewToken protocol, with JSONL audit trails and idempotency keys.
Three transports
stdio, Streamable HTTP and a Web Standard fetch handler. Same tool list — switching is changing one factory call.
Zero-compile dev
bridgent dev runs your TypeScript server directly on Node 22.18+ type stripping. No tsx, no build step, no waiting.
Cross-host verified
A protocol-level harness verifies the server against Claude Code, Cursor, Codex and Gemini CLI on every release.
Code
A server file, not a framework
Compose source adapters in plain TypeScript. The CLI does the rest.
import { createStdioServer, defineTool } from '@bridgent/core'
import { z } from 'zod'
await createStdioServer({
name: 'hello',
version: '0.0.1',
tools: [
defineTool({
name: 'add',
description: 'Add two numbers',
inputSchema: z.object({ a: z.number(), b: z.number() }),
run: ({ a, b }) => a + b,
}),
],
})Hosts
Speaks MCP, works everywhere
Verified at the protocol level against the hosts teams actually use.
Claude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x client
Claude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x clientClaude CodeCursorOpenAI CodexGemini CLIMCP InspectorAny MCP 1.x client