Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Database Mcp Core

FreeNot checked

Engine-agnostic core for database-mcp MCP servers: protocol layer, adapter interface, guardrails, SQL guard

GitHubEmbed

About

Engine-agnostic core for database-mcp MCP servers: protocol layer, adapter interface, guardrails, SQL guard

README

CI License: MIT npm PyPI Node >= 20

MCP servers that give AI clients safe, structured access to SQL databases.

One installable package per database engine, in TypeScript (npm) and Python (PyPI). Every package exposes the same minimal two-tool surface, execute_sql and search_objects, with guardrails on by default: read-only mode, row caps, and statement timeouts.

Packages

Engine TypeScript (npm) Python (PyPI)
SQLite @database-mcp/sqlite npm database-mcp-sqlite PyPI
libSQL @database-mcp/libsql npm database-mcp-libsql PyPI
MySQL @database-mcp/mysql npm database-mcp-mysql PyPI
MariaDB @database-mcp/mariadb npm database-mcp-mariadb PyPI
Postgres @database-mcp/postgres npm database-mcp-postgres PyPI

Both lines are published and pass the same language-agnostic conformance suite against real databases in CI, so behavior is identical regardless of language. Every engine is also listed on the MCP Registry with both install options.

Go and Rust implementations are planned.

Design principles

  • Two tools, no more. A tiny tool surface keeps the model's context window clean. search_objects progressively discloses schema: call it with no arguments to list tables, with a table name to get columns, indexes, and foreign keys.
  • Safe by default. Read-only mode is enforced in two layers: a conservative SQL guard, plus a session-level read-only setting in the database itself. Rows are capped (default 1000) and statements time out (default 30s).
  • Configured at launch, never via chat. Connection details come from flags, a YAML config file, or environment variables. Credentials are never accepted through a tool call.
  • Secrets never appear in logs. Passwords live in non-printable secret types, DSNs are sanitized before logging, and a redaction filter guards the log boundary.

Quick start

Pick your engine's package; each README has the full config surface. SQLite via npm:

{
  "mcpServers": {
    "sqlite": {
      "command": "npx",
      "args": ["-y", "@database-mcp/sqlite", "--dsn", "/absolute/path/to/database.db"]
    }
  }
}

Or via PyPI: use "command": "uvx" and "args": ["database-mcp-sqlite", "--dsn", "/absolute/path/to/database.db"]. Flags, environment variables, and YAML config are identical across both lines.

Networked engines take credentials from the environment (MYSQL_*, MARIADB_*, POSTGRES_*/DATABASE_URL, LIBSQL_URL/LIBSQL_AUTH_TOKEN), *_FILE mounted secrets, or a YAML file via --config. Never from a chat prompt.

Contributing

See CONTRIBUTING.md. The short version: the conformance suite is the definition of done. A change is mergeable only when conformance/run.mjs passes against every affected server.

License

MIT

from github.com/arifulislamat/database-mcp

Installing Database Mcp Core

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/arifulislamat/database-mcp

FAQ

Is Database Mcp Core MCP free?

Yes, Database Mcp Core MCP is free — one-click install via Unyly at no cost.

Does Database Mcp Core need an API key?

No, Database Mcp Core runs without API keys or environment variables.

Is Database Mcp Core hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Database Mcp Core in Claude Desktop, Claude Code or Cursor?

Open Database Mcp Core on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Database Mcp Core with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All data MCPs