Skip to content
Back to search

coral

The execution layer for AI agents. Act across more of your systems with precise controls: safer, faster and more efficient than MCP tools and gateways.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/withcoral/coral with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/withcoral/coral'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/withcoral--coral/badge.svg)](/listings/withcoral--coral)

HTML

<a href="/listings/withcoral--coral"><img src="/api/listings/withcoral--coral/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 250 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. ![Coral, with engraved orange corals](./apps/docs/images/cover.webp)
  2. # Coral
  3. **Execution rails for agents.**
  4. Coral is an open-source, self-hosted gateway that sits between your agents and
  5. the systems they work on. Agents call tools by writing short TypeScript
  6. programs, and save the ones that work as custom tools to reuse. Coral checks
  7. every call against your policy before it adds credentials and forwards the
  8. call.
  9. [![CI](https://github.com/withcoral/coral/actions/workflows/ci.yml/badge.svg)](https://github.com/withcoral/coral/actions/workflows/ci.yml)
  10. [![License](https://img.shields.io/github/license/withcoral/coral)](./LICENSE)
  11. [![Docs](https://img.shields.io/badge/docs-withcoral.com-171717)](https://withcoral.com/docs)
  12. [![Slack](https://img.shields.io/badge/chat-Slack-4A154B?logo=slack&logoColor=white)](https://withcoral.com/slack)
  13. [Quickstart](https://withcoral.com/docs/getting-started/quickstart) ·
  14. [Download](https://withcoral.com/download) ·
  15. [Demo video](https://www.youtube.com/watch?v=p0PKOlHLyVI)
  16. In this example, an agent posts unreviewed pull requests to Slack for the first
  17. time. The agent searches for the GitHub and Slack tools and writes code that
  18. calls them. It cannot post to Slack without approval, so the user approves the
  19. post. The agent then saves its code as a custom tool. The next day, the agent
  20. runs the same task by calling that custom tool.
  21. ![In Claude Code, an agent posts unreviewed pull requests to Slack. It searches Coral for the GitHub and Slack tools, writes code that calls them, and waits for approval before posting. The Coral UI then shows the run, who approved it, and the custom tool the agent saved. The next day, the same request runs by calling that custom tool. A final card compares the two days: 35% fewer tokens and 31% faster, in line with our benchmarks.](./apps/docs/images/demo.gif)
  22. **Control what agents can do.** Most MCP gateways decide only which tools an
  23. agent can see. That is all or nothing: if an agent can call `update_record`, it
  24. can update any record in any way the tool allows. A custom tool is code, so it
  25. can hold a rule that Allow and Block cannot. For example, `closeStaleTicket`
  26. changes one field, and only on tickets with no activity for 30 days. You set
  27. Allow, Ask, or Block on the custom tool like any other tool. Coral still checks
  28. every provider call inside it against your policy.
  29. **Less duplicated agent work.** Agents start every task from scratch. They
  30. re-read tool schemas, retry failed calls, and spend tokens rewriting code for
  31. steps they got right yesterday. With Coral, agents save the code that worked
  32. as custom tools, and call them again in one step. Workspace owners can share
  33. those tools with the whole team.
  34. Thousands of developers at more than 450 companies use Coral for safer, more
  35. efficient agent work. They use it in customer support, SecOps, business
  36. intelligence, SRE, and more.
  37. ## Get started
  38. 1. **Install Coral.**
  39. - To use Coral yourself, download the desktop app from the
  40. [download page](https://withcoral.com/download). It runs on macOS
  41. (Apple silicon), Windows (x64), and Linux (x86_64).
  42. - To use Coral with your team,
  43. [run a shared server](https://withcoral.com/docs/getting-started/self-host)
  44. with Docker Compose or Kubernetes. You need an OIDC identity provider, a
  45. reverse proxy for TLS, and SQLite or Postgres.
  46. 2. **Add a provider.** A provider is one service your agents can use, such as
  47. GitHub or Linear. Pick one from the catalog, or bring your own OpenAPI
  48. document or MCP server. By default, tools that read data run right away and
  49. everything else needs your approval. See
  50. [Add a provider](https://withcoral.com/docs/getting-started/quickstart#add-a-provider).
  51. 3. **Connect your agent.** Copy your workspace's MCP URL from the Coral UI and
  52. add it to your MCP client:
  53. ```bash
  54. claude mcp add --scope user --transport http coral <your-mcp-url> # Claude Code
  55. codex mcp add coral --url <your-mcp-url> # Codex
  56. ```
  57. For Cursor, VS Code, OpenCode, and other clients, see
  58. [Connect an MCP client](https://withcoral.com/docs/getting-started/quickstart#connect-an-mcp-client).
  59. 4. **Ask a question.** Ask your agent something that uses that provider, such
  60. as "What are my open pull requests?"
  61. ## Why Coral
  62. We started Coral while building an AI SRE. To investigate an incident, the
  63. agent had to connect the dots across an ocean of telemetry and undocumented
  64. relationships between internal and external systems. It needed broad
  65. permissions and a lot of tokens, and it started from scratch the next time.
  66. We built Coral so that the agent remembers the route. Once a task succeeds,
  67. the agent saves the steps that worked as a custom tool. Next time, it finds
  68. that tool in the same search as provider tools such as Datadog and Slack.
  69. Coral started with SRE. Teams now use it for agent work across the
  70. organization:
  71. - **SRE.** The agent investigates alerts. Custom tools let it roll back only
  72. the services you name.
  73. - **Customer support.** The agent issues refunds, and escalates to a person in
  74. the cases you define.
  75. - **Business intelligence.** Custom tools aggregate warehouse, CRM, and billing
  76. data, and pass only the metrics to the agent.
  77. - **SecOps.** The agent uses custom tools to isolate devices within approved
  78. groups.
  79. What you get:
  80. - **Precise control.** Set Allow, Ask, or Block for each provider tool and each
  81. custom tool. An approval shows the exact call and its arguments, so Security
  82. approves one refund lookup, not the whole payments API. See
  83. [Roles & Permissions](https://withcoral.com/docs/guides/permissions).
  84. - **Shared tools.** You can set each provider to use the
  85. caller's own account, so teammates share tools without sharing API tokens.
  86. Read how [Slackbot uses this](https://withcoral.com/blog/slackbot-works-better-with-coral).
  87. - **Cheaper models, same accuracy.** With custom tools, a smaller model
  88. performs like a bigger one. For many tasks, this means Opus 5.5 accuracy at
  89. Haiku 5.5 cost.
  90. - **Faster, leaner agents.** Across 34 tasks on GitHub, Linear, and Slack with
  91. Opus 5.5, custom tools cut tokens by 37%, cost by 31%, and time by 29%. See
  92. [every task](https://withcoral.com/docs/examples/custom-tools).
  93. - **Ahead of other MCP gateways.** In blind benchmarks of 100 enterprise
  94. tasks, agents were more accurate and cheaper with Coral than with other MCP
  95. gateways. See the [benchmarks](https://withcoral.com/#benchmarks).
  96. - **Training data you own.** Each run leaves a structured trace of the goal,
  97. the tools used, and the outcome. The trace works well for post-training your
  98. own model.
  99. How Coral fits your stack:
  100. - **Runs on your infrastructure.** Coral is written in Rust. It runs as a
  101. desktop app on your laptop or as a shared server in your own cloud, with
  102. zero data egress.
  103. - **Open source.** Coral is licensed under the Apache License 2.0, with no
  104. limits on users, agents, or volume. Everything in this README outside
  105. [Coral Enterprise](#for-teams-and-enterprise) is in the open-source edition.
  106. - **Any agent, any system.** Coral works with any AI app or agent that
  107. supports MCP. You can connect anything with an MCP server or OpenAPI
  108. document, including more than 5,000 databases and SaaS tools.
  109. ## How Coral works
  110. **Agents write programs.** Coral builds on code mode, and adds custom tools,
  111. policy controls, and managed identities. To use tools, an agent writes a short
  112. TypeScript program. One program can call several tools, filter the results,
  113. and return only what the task needs. Less raw data passes through the model's
  114. context.
  115. **Coral runs them on rails.** Each program runs in a fresh V8 isolate with no
  116. network access, no credentials, and no imports. Coral checks every tool call
  117. against your workspace policy, then adds the credentials and forwards the call
  118. to the provider. A policy can also require a person to approve the call. Coral
  119. attributes every run to the person or agent that started it.
  120. ```mermaid
  121. graph LR
  122. Agent["Your agent"] -->|"exec: run a program"| MCP["Coral MCP server"]
  123. You["You"] -->|"providers, policy, approvals"| UI["Coral UI"]
  124. subgraph Coral["Coral (your laptop or server)"]
  125. MCP --> Run["Program runs in a V8 isolate"]
  126. Run <--> FN["Custom tools (private and shared)"]
  127. UI --> Gate["Policy check and credentials"]
  128. Run --> Gate
  129. Gate -.->|"approval request"| UI
  130. end
  131. Gate --> GH["GitHub"]
  132. Gate --> SL["Slack"]
  133. Gate --> Own["Your OpenAPI or MCP service"]
  134. ```
  135. The agent sends Coral programs through the `exec` tool. A program calls
  136. `coral.search` to find the tools the agent can use and read their
  137. TypeScript signatures. Then the agent sends a program that does the work.
  138. This one finds open pull requests that have no reviewer and posts them to
  139. Slack:
  140. ```ts
  141. const { data: pulls } = await coral.providers.github.pulls.list({
  142. owner: "withcoral",
  143. repo: "coral",
  144. state: "open",
  145. });
  146. const unreviewed = pulls.filter((pull) => pull.requested_reviewers.length === 0);
  147. await coral.providers.slack.chat.postMessage({
  148. channel: "#engineering",
  149. text: unreviewed.map((pull) => `#${pull.number} ${pull.title}`).join("\n"),
  150. });
  151. return unreviewed.map((pull) => pull.number);
  152. ```
  153. If posting to Slack needs approval, the run pauses there until you approve it.
  154. Only the pull request numbers go back to the agent, not the full GitHub
  155. response. The run happens on the Coral server, so it continues even if the
  156. agent disconnects.
  157. **What works becomes a custom tool.** When a program succeeds, the agent saves
  158. it as a private tool. Next time, the agent calls it in one step as
  159. `coral.private.<name>({ ... })`. Agents find custom tools in the same search
  160. as provider tools, and reuse or edit them instead of starting over. A
  161. workspace owner can publish a private tool as a shared tool under
  162. `coral.shared`, so everyone in the workspace can call it.
  163. To learn about providers, accounts, policy, and workspaces, read
  164. [Concepts](https://withcoral.com/docs/guides/concepts).
  165. ## For teams and enterprise
  166. To run Coral for a team, see
  167. [Run a shared server](https://withcoral.com/docs/getting-started/self-host).
  168. Coral Enterprise is coming soon under its own license. It adds
  169. organization-wide governance and support: SSO with SAML, SCIM provisioning,
  170. advanced RBAC, an immutable audit log, and support SLAs. See
  171. [Coral Enterprise](https://withcoral.com/pricing) or
  172. [book a demo](https://withcoral.com/contact).
  173. ## Development
  174. To run Coral from a checkout, follow the
  175. [development guide](./docs/development.md). To contribute, read
  176. [`CONTRIBUTING.md`](./CONTRIBUTING.md). The
  177. [release notes](https://github.com/withcoral/coral/releases) list what changed
  178. in each version.
  179. ## Community
  180. Ask questions, share ideas, and show what you built in our
  181. [Slack community](https://withcoral.com/slack) or on
  182. [GitHub issues](https://github.com/withcoral/coral/issues).
  183. ## Security
  184. Do not report security issues in public issues or pull requests. See
  185. [`SECURITY.md`](./SECURITY.md).
  186. Coral is ISO/IEC 27001:2022 certified. Each program runs in its own V8
  187. isolate, and Coral logs every approval.
  188. ## License
  189. Coral is licensed under the Apache License 2.0. See [`LICENSE`](./LICENSE).
  190. The [`ee/`](./ee) directory holds Enterprise Edition code under its own license,
  191. [`ee/LICENSE`](./ee/LICENSE). A plain `cargo build` at the repository root
  192. builds only code under the Apache License 2.0. [`NOTICE`](./NOTICE) states
  193. which license covers which files.
  194. ## Upgrade from Coral 0.x
  195. Coral v1 replaces the SQL interface with TypeScript programs. It starts from
  196. fresh state and does not convert what 0.x stored. If Coral finds 0.x state, it
  197. tells you at startup. See
  198. [Upgrade from Coral 0.x](https://withcoral.com/docs/getting-started/self-host#upgrade-from-coral-0-x).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.