MCP / Database / Self-hosted

Turn any database into an MCP server — visually.

Calame is the control plane between your data and your AI clients. Connect Postgres, MySQL or SQLite, sculpt access profiles with PII masking and row-level scoping, then serve them to Claude, Cursor, VS Code — or your own LLM.

Read the quickstart View on GitHub

terminal

$ docker compose up
  ↳ Calame is running on http://localhost:4567

DB engines

auth modes

SaaS lock-in

What's inside

Everything you need between a database and an LLM.

Calame is one binary that ships the schema introspector, the profile editor, the auth layer, the masking engine, and the MCP server runtime. No glue code.

pg · mysql · sqlite

Database connectors

PostgreSQL, MySQL, SQLite. Schema introspection, foreign-key graph, sample rows. Read-only by default — Calame opens connections with SET TRANSACTION READ ONLY.

profile.yaml

Access profiles

Per-table & per-column visibility. Row-level scoping (e.g. restrict to client_email = X). One database, many published views.

auto-detect · custom rules

PII masking

Auto-detection of emails, phones, addresses, card numbers. Per-column or global rules: full redaction, hash, partial mask, or custom regex.

6 modes · MCP-OAuth ready

Pluggable auth

Open, Bearer token, password, OIDC SSO, OAuth 2.1 with Dynamic Client Registration, or external validation URL. Per-user revocation.

BYO LLM

Built-in chat

Query in natural language without leaving the UI. Anthropic, OpenRouter, or any OpenAI-compatible endpoint — including local Ollama, vLLM, LM Studio.

JSON export

Audit, by default

Every query, every actor, every scope — recorded and exportable. Write queue with approval workflow if you ever opt into mutating queries.

How it works

Many sources, one control plane, any client.

Plug Calame to a database, point it at a folder of PDFs and Markdown, and serve everything to your LLM through a single MCP endpoint. Same auth, same masking, same audit log — wherever the data lives.

Databases

Apache

Postgres · MySQL · SQLite

Knowledge bases

BUSL

PDF · Markdown · DOCX

Calame

profiles · auth · PII · audit

MCP client

Claude · Cursor · VS Code · chat

STEP 1

Connect

Databases — Calame introspects schema, columns, foreign keys. Files — point at a folder, Calame parses PDFs, Markdown, DOCX, HTML, CSV and embeds them.

STEP 2

Configure

Pick tables and folders, mask PII, draw row-level scopes, choose an auth mode. Save a profile — it becomes a published MCP endpoint.

STEP 3

Connect again

Drop the URL into Claude Desktop, Cursor, VS Code. They auto-discover both query and retrieval tools via OAuth 2.1 DCR.

Plays well with

Any MCP-compliant client. No custom SDK.

Calame speaks the open Model Context Protocol over HTTP — so any compliant client works out of the box. Drop a URL, optionally an Authorization header, you're done.

Claude Desktop

OAuth · DCR

Cursor

HTTP · token

VS Code

MCP ext.

ChatGPT Desktop

HTTP

Continue

HTTP

Built-in chat

no client needed

New MCP clients ship every month — Calame stays compatible because it implements the spec, not a vendor SDK.

claude_desktop_config.json

example

{
  "mcpServers": {
    "calame": {
      "transport": {
        "type": "http",
        "url": "https://calame.acme.io/mcp/sales",
        "headers": {
          "Authorization": "Bearer ••••••"
        }
      }
    }
  }
}

↳ For OAuth profiles, drop the headers block — Claude Desktop will prompt the user via browser.

Open at the core

Free to self-host. Pay when you need SSO, RAG, or scale.

Calame is dual-licensed. The core — connectors, profiles, MCP runtime, PII masking, chat, audit — is Apache 2.0. The ee/ modules (SSO + RAG) are BUSL 1.1: Pro unlocks them on one instance, Enterprise on as many as you need.

Apache 2.0

Community

Self-host without limits.

All connectors (Postgres, MySQL, SQLite)
Profiles, PII masking, row-level scoping
Bearer / password / OAuth 2.1 auth
Built-in chat, audit log, write queue
Use it in production. Fork it. Modify it.

Read the quickstart

BUSL 1.1 · Pro · Enterprise · Cloud

Paid plans

Unlock SSO + RAG, scale to many instances, or get hosted.

Pro — all features on one instance · $45/mo
Enterprise — unlimited instances + SLA support
Cloud — managed Calame, coming soon
Right to embed ee/ in a paid product (Enterprise)
Each BUSL release converts to Apache 2.0 after 4 years

See pricing

See the full pricing page

From git clone to first MCP query

Ship your data to your AI clients in 15 minutes.

One Docker command. One profile. One MCP URL. Your database stays where it is — Calame just decides what your LLM is allowed to see.

Read the quickstart Talk to us Star on GitHub