Corporate memory for legacy databases

Give AI agents
a way in to
your data.

CoreBase connects AI agents to SQL Server 2000+, on-prem ERPs, SAP, and air-gapped systems — through an open-source MCP agent that dials out over 443. No inbound ports. No VPN. Read-only by default.

Open source — Apache 2.0
Go binary, zero dependencies
T-SQL aware, fail-closed
2000+
SQL Server versions supported
443
Outbound only — no inbound
2ms
Avg relay latency
AI Agent Layer
Claude Desktop
CoreMCP
coremcp.yaml
Enterprise Data
SQL Server 2000+
Architecture

Every guard enforced
at the database session.

Zero-trust gateway
The agent runs inside the customer's network and dials out over 443 only. No inbound ports. No exposed database. No VPN. Works in air-gapped environments.
T-SQL aware lexer
Custom fail-closed tokeniser strips comments and string literals, then classifies statements. SELECT only. DROP, EXEC, OPENROWSET, and stacked queries are rejected before they reach the DB — no regex workarounds.
PII masking built-in
Credit cards, emails, Turkish IDs, phone numbers, and IBANs are masked by regex before rows reach the model. Full audit log on every query — who asked, what was asked, what came back.
Per-tenant isolation
Every query attributed and isolated. Multi-tenant deployments keep customer data sealed — separate DSNs, separate connection pools, no cross-tenant visibility.
Turkish_CI_AS support
Outbound: Turkish characters inside SQL string literals are folded to ASCII uppercase before the query is sent. Inbound: Windows-1254/Windows-1252 mojibake is auto-corrected. Works out of the box for Turkish ERP databases.
NOLOCK by default
Every SELECT runs under READ UNCOMMITTED. Equivalent to WITH (NOLOCK) on every table reference — never blocks production OLTP. Dirty reads possible; deadlocks impossible.
The primitives

Schema → Tools, not embeddings.

coremcp.yaml
# coremcp.yaml — runs inside the customer's network sources: - name: "erp_db" type: "mssql" dsn: "sqlserver://..." readonly: true no_lock: true pii_masking: true security: max_row_limit: 1000 enable_pii_masking: true egress: mode: "outbound-only" relay: "wss://relay.corebasehq.com"

On startup, CoreMCP connects to every configured source, scans tables and columns, reads key relationships and stored procedures, and extracts column comments (MS_Description on MSSQL). The result is exposed as MCP tools the model can call — no ETL, no reindex cron, no embeddings to manage.

Every query the model runs is stored in Query Memory. The agent learns which queries work against your schema — schema relationships, foreign key paths, and what "active customer" means in your world. The more queries it sees, the more accurate every next answer.

Deploy anywhere

Four ways to run.

01
Cloud-direct
Paste a DSN into the CoreBase panel. Data flows through CoreBase Cloud.
02
Cloud-relay
CoreMCP on-prem dials out to CoreBase Cloud over 443.
03
Self-hosted
Run CoreMCP inside your VPC. Your keys. Your network.
04
Air-gap
Enterprise container, fully isolated. No external connections.
Integrations

Connect your stack.

CoreBase speaks to the systems your enterprise actually runs on — legacy databases nobody else supports, REST APIs your team built in 2009, ERP modules your CFO still opens daily.

MSSQL
SQL Server 2000–2022
stable
PG
PostgreSQL 11+
stable
FB
Firebird (Delphi-era ERP)
in progress
REST
REST API adapter
stable
GQL
GraphQL adapter
stable
MCP
Claude Desktop, Cursor, Cline, Zed
stable

The data that runs
your enterprise
shouldn't be locked out

Most AI database tools target modern Postgres. CoreBase targets SQL Server 2000, Turkish_CI_AS collations, air-gapped factory networks, and ERP systems nobody wants to migrate.

curl -fsSL get.corebasehq.com | sh