npx create-inherence-mcp my-server generates a TypeScript MCP server with Inherence policy gating baked in from line one. Every tool wrapped in withInherenceGate; every call produces a 128-byte Groth16 receipt; OAuth, deploy configs, mock-gate tests all scaffolded. Compose with whatever else your MCP server needs — Stainless-generated SDKs, hand-rolled tools, Anthropic Connectors. Inherence handles the audit layer.
npx create-inherence-mcp my-server
cd my-server && npm install
npm run devAfter Anthropic acquired Stainless (May 2026), the MCP build-tooling layer consolidates into the model labs. That's good for the ecosystem — fewer MCP servers will be hand-rolled. What it doesn't solve: when an MCP server's tool calls touch regulated data, customer money, or anything an auditor cares about, you still need cryptographic evidence the policy held. That's what this tool produces.
Use Stainless for the SDK. Use this for the policy layer. They compose.
Uses the official @modelcontextprotocol/sdk. TypeScript, Zod schemas, every tool registered with setRequestHandler.
Every tool's execute wrapped in withInherenceGate. The wrapped function routes to mcp.inherencelabs.com, blocks/allows, surfaces the decision as a structured tool error if denied.
Choose HIPAA / SEC 15c3-5 / SOC 2 / AP2 / catastrophe-shield / custom. The YAML compiles end-to-end against Inherence's compiler.
Spins up a local HTTP fixture. Tests run in CI without spending API credits. Same pattern @inherence/mastra uses (13/13 passing).
If your server proxies a third-party API (Google, GitHub, Slack, Notion), the OAuth dance is scaffolded with envelope-encrypted token storage.
Pick one or several: Cloudflare Workers (edge), Fly.io (container), Vercel Functions, bare Node. Each comes with a working config.
The generated server contains zero policy logic. By design. Every tool's execute wraps in withInherenceGate, which captures the call, POSTs to mcp.inherencelabs.com, and acts on the decision. No ROBDD code locally, no Groth16 generation locally, no signing — strictly verification (when wired in v0.2). This is the same architecture as inherence-proxy, @inherence/mastra, and @inherence/middleware-vercel: dumb plumbing on the client side, all policy at the backend. The scaffold preserves the boundary so you can't accidentally violate it.
Community contribution. Not yet on npm; install from GitHub today, npm publish queued for review.
View on GitHub → Start a pilot