CLI tool
withcoral/coral avatar
withcoral/coral

Coral: one MCP server for every service your agents use

One SQL interface over APIs, files, and live sources — built for agents.

5,025 stars230 forksRustApache-2.0

At a glance

What is it?
Coral is a Rust MCP server that runs agents' short TypeScript programs in a sandbox, adds the credentials, and checks every call against your policy. Coral 1.0 replaced the earlier SQL interface.
Who is it for?
Worth trying if your agents use many services and you want one MCP server that holds the credentials, runs agent programs in a sandbox, checks every call against your policy, and records every run. If you used Coral 0.x, note that 1.0 replaces the SQL interface with TypeScript programs and starts from fresh state without converting what 0.x stored.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • withcoral/coral5,025 ★ · +83
Star history
Repository2026-09-232026-11-22
withcoral/coral4.9k5k

83 Stars in the last 60 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One SQL statement replaces the paginated tool call

Coral sits between an agent and the services it uses. Agents write short TypeScript programs; Coral runs them in a sandbox, adds the credentials, and checks every call against your policy. Instead of many MCP servers, a token pasted into each one, and every tool definition loaded into every prompt, the agent searches for the tools it needs and sends one program that can call several tools and return only the fields the answer needs. Coral 1.0 replaced the earlier SQL interface with these TypeScript programs. You run Coral on your laptop or on your own server, and your data, credentials, and usage history stay with you.

A source is a YAML spec plus the credentials you configured

A provider is one service your agents can use. You pick one from the catalog, or bring your own OpenAPI document or MCP server. Coral includes setup recipes for GitHub, Linear, Jira, Notion, Gmail, Stripe, Datadog, Sentry, HubSpot, and more, and you can add any service that has an OpenAPI document or an MCP server.

Cross-source joins run locally after both sides arrive

Because one program can call several tools, a single run can cross from one system to another. The README's example program lists open GitHub pull requests that have no requested reviewers and posts them to Slack. Only the pull request numbers go back to the agent, not the full GitHub response.

The read layer has no write path

Coral is not limited to reads: the README's example program posts a message to Slack. You set each tool to allowed, approval required, or disabled, and a call that needs approval waits until a person approves it. If posting to Slack requires approval, the run pauses there until you approve it. Every run is recorded, and you can review each program and the calls it made in the Coral UI.

coral source discover misses the community specs

There are two ways to add a provider: pick one from the catalog, or bring your own OpenAPI document or MCP server. When a program works, the agent can save it as a function. Saved functions are typed, appear in search alongside provider tools, and later programs call them as `coral.functions.<name>()`.

Credentials come from the environment or an --interactive prompt

Agents never hold credentials. Coral stores your tokens and adds them to each call, and programs run in an isolated sandbox with no secrets, no network access, and no imports. Each workspace in Coral has its own MCP URL, which you copy from the Coral UI and add to your MCP client:

bash
claude mcp add --scope user --transport http coral <your-mcp-url>   # Claude Code
codex mcp add coral --url <your-mcp-url>                            # Codex

The vendor benchmark shows the smallest gap on the simplest tasks

The README makes the efficiency case without benchmark numbers: the agent searches for the tools it needs instead of loading them all up front, sends one program that can call several tools, and gets back only the fields the answer needs. When a program works, the agent saves it as a function and calls it in one step next time.

Building from the checkout asks for Rust 1.97 and a locked cargo install

Installing from source is a Rust job with an explicit toolchain. Cargo.toml asks for edition 2024 and rust-version 1.97, and the Makefile install target is the supported route to the CLI.

bash
cargo install --path crates/coral --locked

The lint table in the same file is strict for a project this size, with unsafe_code forbidden and rules such as unwrap_used, print_stdout, and indexing_slicing set to warn. Docker is the other build path: the Makefile builds images with Docker or Podman. End users can skip all of it and download the desktop app for macOS, Linux, or Windows from the releases page. Releases move quickly, with v1.2.0, v1.3.0, and v1.4.0 landing between 2026-10-22 and 2026-10-29, and the last push on main is dated 2026-11-01.

Editorial conclusion

Worth trying if your agents use many services and you want one MCP server that holds the credentials, runs agent programs in a sandbox, checks every call against your policy, and records every run. If you used Coral 0.x, note that 1.0 replaces the SQL interface with TypeScript programs and starts from fresh state without converting what 0.x stored. Before you move anything over, check that the services you need are in the provider catalog or have an OpenAPI document or MCP server.

Frequently asked questions

Does Coral send my company data or credentials to a remote server?

No. Data, credentials, and usage history stay local, and Coral stores your tokens and adds them to each call, so agents never hold credentials.

Which coding tools can talk to Coral over MCP?

Each workspace in Coral has its own MCP URL that you add to your MCP client. The README gives commands for Claude Code and Codex and points to the docs for Cursor, VS Code, OpenCode, and other clients.

Can Coral write back to GitHub, Linear, or Slack?

Yes. The README's example program posts a message to Slack, and you can set each tool to allowed, approval required, or disabled; a call that needs approval waits until a person approves it.

How do I add a data source that Coral does not bundle?

Bring your own OpenAPI document or MCP server; Coral can add any service that has one.

How do I install Coral on a server?

The README links a guide to run a shared server for your team. Building from a checkout uses the Makefile install target, which runs cargo install --path crates/coral --locked, and the workspace asks for Rust 1.97 with edition 2024.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. withcoral/coral on GitHub
Community

Where developers are discussing it

Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 1 in the last 30 days; newest first.

Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/withcoral-coral.svg)](https://hysenlabs.com/projects/withcoral-coral)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/withcoral-coral.svg)](https://hysenlabs.com/projects/withcoral-coral)

Was this useful?