A Model Context Protocol (MCP) server, written in Go, that exposes SQL databases as MCP tools and prompts. It runs as a single static binary, embeds
A Model Context Protocol (MCP) server, written in Go, that exposes SQL databases as MCP tools and prompts. It runs as a single static binary, embeds its drivers, and talks either stdio (for local MCP clients like Claude Desktop) or an. The coremcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
CoreMCP is the open-source, on-prem gateway component of CoreBase, an AI agent platform for your company's data. Chat with your databases and APIs directly, or let autonomous and event-triggered agents run multi-step automations across them — databases (SQL Server 2000+, PostgreSQL), REST and GraphQL APIs, and 50+ SaaS connectors.
Everything the assistant can do here goes through one of these:
name — "get_daily_sales"Binary — Download from the Releases page — linux/amd64, linux/arm64, darwin/{amd64,arm64}, windows/amd64query_database — The query_database tool exposed by this serverlist_tables — Tables with column counts, primary keys, foreign key countsdescribe_table — Full schema for one table: columns, types, nullability, PKs, FKs, column commentslist_views — The list_views tool exposed by this serverlist_procedures — Stored procedures with parameter names, types, modes (IN/OUT/INOUT), and a ready-to-copy example callexecute_procedure — Calls a stored procedure with named parameters. Only enabled when readonly: false.Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Coremcp's toolset — name, Binary, query_database and 5 more — is a fair guide to whether it matches your workflow. It is maintained by corebasehq; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| name | "get_daily_sales" |
| Binary | Download from the [Releases page](https://github.com/corebasehq/coremcp/releases) — linux/amd64, linux/arm64, darwin/{amd64,arm64}, windows/amd64. |
| query_database | The query_database tool exposed by this server. |
| list_tables | Tables with column counts, primary keys, foreign key counts. |
| describe_table | Full schema for one table: columns, types, nullability, PKs, FKs, column comments. |
| list_views | The list_views tool exposed by this server. |
| list_procedures | Stored procedures with parameter names, types, modes (IN/OUT/INOUT), and a ready-to-copy example call. |
| execute_procedure | Calls a stored procedure with named parameters. **Only enabled when readonly: false.** |
{
"mcpServers": {
"coremcp": {
"command": "/path/to/coremcp",
"args": ["serve", "-c", "/path/to/coremcp.yaml"],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.