
Dbmcp
Give your coding agent safe, structured access to MySQL, MariaDB, PostgreSQL, or SQLite so you can inspect schemas, run queries, and debug data issues without leaving the chat.
Overview
ai.haymon/dbmcp is a MCP server for the Build phase that exposes MySQL, MariaDB, PostgreSQL, and SQLite to agents via stdio or streamable HTTP.
What is this MCP server?
- Supports MySQL, MariaDB, PostgreSQL, and SQLite in one MCP server (v0.9.1).
- Ships as Docker OCI (ghcr.io/haymon-ai/dbmcp) with stdio and streamable-http transports.
- HTTP mode binds host/port (default 127.0.0.1:9001) with configurable CORS allowed origins.
- Positional transport args distinguish stdio vs http startup for agent hosts.
- Lets agents reason over real schemas and SQL instead of pasted screenshots or manual CLI hopping.
- Version 0.9.1 on OCI registry ghcr.io/haymon-ai/dbmcp
- Four supported engines: MySQL, MariaDB, PostgreSQL, SQLite
- Two transport modes: stdio and streamable-http (default HTTP port 9001)
Community signal: 26 GitHub stars.
What problem does it solve?
Solo builders waste cycles context-switching to SQL clients and guessing schema state while the agent drafts backend code.
Who is it for?
Indie developers running Docker who want one MCP entry for multiple SQL engines during backend and integration work.
Skip if: Teams that need a managed cloud database console, NoSQL-only stacks, or production write access without strict DB user limits.
What do I get? / Deliverables
After you register dbmcp, your agent can query and inspect the same database engines you develop against with MCP-native tool calls.
- MCP tool access to four SQL engines from one server image
- Optional HTTP MCP endpoint on a configurable host and port
- Agent-ready database inspection without separate GUI clients
Recommended MCP Servers
Journey fit
Database connectivity is a core Build-phase integration task when wiring backends, migrations, and local dev stacks. Catalog shelf fits integrations because the server exposes MCP tools against live database engines rather than UI or shipping gates.
How it compares
Direct database MCP bridge, not an ORM codegen skill or a hosted analytics warehouse.
Common Questions / FAQ
Who is ai.haymon/dbmcp for?
Solo and small-team builders using Claude Code, Cursor, or similar agents who develop against MySQL, MariaDB, PostgreSQL, or SQLite and want MCP-driven schema and query access.
When should I use ai.haymon/dbmcp?
Use it during Build when you are wiring APIs, debugging SQL, validating migrations, or comparing local and staging schemas without leaving the agent session.
How do I add ai.haymon/dbmcp to my agent?
Pull ghcr.io/haymon-ai/dbmcp:0.9.1, run with the stdio positional argument for local agents or http with --host and --port for streamable HTTP, then add the server block in your MCP client config.