Skip to main content
CoreMCP is the on-prem half of CoreBase. It’s a single Go binary that runs on a server inside your perimeter, holds your credentials, and does the work inside your network — querying databases, and calling REST or GraphQL APIs that are only reachable from in there. CoreBase talks to it over the Model Context Protocol — either directly (Claude Desktop, MCP-aware clients) or through CoreBase Cloud as a relay.

​
Responsibilities

Schema discovery

Inspect connected databases (MSSQL today, Firebird coming soon) and produce schema snapshots — table names, columns, foreign keys, indexes, column comments.

Query execution

Receive generated SQL, run it locally with read-only credentials, return rows over MCP. Modern protocol — no custom wire format.

Credential vault

Database secrets stay in coremcp.yaml on your server. CoreBase never sees them.

SQL dialect adaptation

Auto-detects SQL Server 2000 / 2008 and rewrites OFFSET FETCH / LIMIT for T-SQL compatibility. Turkish_CI_AS collation supported.

​
Transports

Configure under server.transport in coremcp.yaml. The same binary handles both.

​
Deployment modes

​
What’s in the binary

Open-source, Go 1.23+, single static binary (~30MB):
  • MCP server (stdio + HTTP)
  • Database drivers: MSSQL stable, Firebird in progress
  • Schema discovery with column-comment introspection
  • Custom query tools — define reusable SQL as MCP tools in YAML
  • Read-only mode by default (readonly: true)

See the source

Audit the protocol, contribute drivers, vendor the binary into your release process.

​
Next

Install

Binary release, from source, Docker, or systemd.

Connect a database

Connection-string playbook + per-driver options.