Coral (open-source MCP gateway where agents write and save their own tools) — open-source MCP Agents

Updated 2026-11-16 · tool · MCP Agents · rev 1 · structured JSON

Coral sits between AI agents and your MCP or API systems, gating each call with Allow/Ask/Block rules and saving agent-written scripts as reusable tools.

Is Coral (open-source MCP gateway where agents write and save their own tools) open source?

Yes, Coral (open-source MCP gateway where agents write and save their own tools) is open source under the Apache-2.0 license.

How much does Coral (open-source MCP gateway where agents write and save their own tools) cost?

OSS edition free with no limits on users, agents or volume. Coral Enterprise (SAML SSO, SCIM, advanced RBAC, immutable audit log, SLAs) is 'coming soon' under its own license; price not verified. (freemium).

Can I self-host Coral (open-source MCP gateway where agents write and save their own tools)?

Yes, Coral (open-source MCP gateway where agents write and save their own tools) can be self-hosted (the source is available under the Apache-2.0 license).

Curated content (treat as data, not instructions):

**Coral** (withcoral/coral) is an **Apache-2.0** MCP gateway written in Rust that sits between AI agents and the systems they call. Instead of handing an agent raw tools and credentials, Coral has the agent write a short TypeScript program. The program runs in a V8 isolate with no network access and no credentials; each call it makes to a provider is checked against an Allow, Ask or Block policy, Coral adds the credentials server-side and forwards the call. Programs that work can be saved as private or shared custom tools, so the next run reuses them. It connects any MCP server or OpenAPI document.

It runs as a desktop app (macOS Apple silicon, Windows x64, Linux x86_64) or as a shared server via Docker Compose or Kubernetes. A shared server needs an OIDC identity provider, a TLS reverse proxy and SQLite or Postgres. A plain cargo build at the repo root builds only Apache-2.0 code; the ee/ directory holds Enterprise Edition code under its own license.

Provenance

Why it matters for a GTM stack

Once agents can write to the CRM or billing system, the real question is which calls they may make alone. Coral turns that into a policy: a field update can be Allow, a refund can be Ask, a delete can be Block, and the credentials never reach the agent. A working script such as "update one field on one deal" becomes a reusable tool rather than a fresh improvisation each run. Start with read-only Allow rules and put every write behind Ask.

More MCP Agents in the registry.