explaingit

withcoral/coral

Analysis updated 2026-05-18

2,247RustAudience · developerComplexity · 3/5Setup · moderate

TLDR

A local SQL query engine that lets you query APIs like GitHub, Linear, and Stripe, plus local files, using familiar SQL syntax and joins.

Mindmap

mindmap
  root((Coral))
    What it does
      SQL over APIs
      Local file queries
      Cross-source joins
    Tech stack
      Rust
      SQL
      MCP
    Use cases
      Join GitHub and Linear
      AI agent data access
      Custom YAML sources
    Audience
      Developers
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Query GitHub issues and Linear tickets together in a single SQL statement.

USE CASE 2

Let an AI coding assistant pull data from multiple APIs through one MCP connection.

USE CASE 3

Join local Parquet or JSONL files with live API data.

USE CASE 4

Define a custom SQL schema for an internal API using YAML config.

What is it built with?

RustSQLMCPYAML

How does it compare?

withcoral/coralorhun/rattyutooland/utoo
Stars2,2472,0822,475
LanguageRustRustRust
Setup difficultymoderatemoderatemoderate
Complexity3/53/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Credentials are stored and used locally only.

In plain English

Coral is a local SQL query engine that lets you query multiple APIs and data files as if they were database tables. SQL (Structured Query Language) is the standard way to ask questions of databases, Coral applies that same familiar syntax to cloud services like GitHub, Linear, Datadog, Sentry, and Stripe, as well as local files in formats like JSONL and Parquet. The problem it solves: AI agents typically query each data source separately with its own unique integration, leading to repetitive code, inconsistent handling, and difficulty combining data from different sources. Coral provides one query layer. Each connected service becomes a SQL schema, for example, GitHub issues become the table github.issues, and you can join data across sources in a single query. Coral handles authentication, pagination, and API calls behind the scenes, returning a clean table of results. You can use it directly from the command line (coral sql "SELECT ...") or expose it to AI coding assistants like Claude Code through MCP (a standard protocol for connecting tools to AI agents). The README reports benchmarks showing Claude was 20% more accurate and 2x more cost-efficient using Coral instead of connecting to each provider separately. Custom sources can be defined with YAML configuration files to connect any HTTP API not already bundled. Credentials are stored and used locally only and never sent anywhere beyond the API being queried. Coral is built in Rust and installs on macOS and Linux. The full README is longer than what was provided.

Copy-paste prompts

Prompt 1
Set up Coral and write a SQL query joining GitHub issues with Linear tickets.
Prompt 2
Use Coral as an MCP server so Claude Code can query my Stripe data.
Prompt 3
Show me how to define a custom Coral data source with a YAML config file.
Prompt 4
Query a local Parquet file alongside live Datadog data using Coral.

Frequently asked questions

What is coral?

A local SQL query engine that lets you query APIs like GitHub, Linear, and Stripe, plus local files, using familiar SQL syntax and joins.

What language is coral written in?

Mainly Rust. The stack also includes Rust, SQL, MCP.

How hard is coral to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is coral for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.