FreePeak/db-mcp-server
by Various
A powerful multi-database server implementing the Model Context Protocol (MCP) to provide AI assistants with structured access to databases.
MCP
FreePeak/db-mcp-server
Added 1 June 2026
Overview
FreePeak/db-mcp-server is a Go-based server that implements the Model Context Protocol (MCP) to give AI assistants structured access to multiple databases. It acts as a bridge, allowing language models to query and interact with databases through a standardized interface.
Best for
Best for
Developers building AI assistants that need direct, structured database access via the Model Context Protocol
Use cases
- Enabling AI assistants to run SQL queries against production databases
- Providing structured database access for AI-driven data analysis tools
- Integrating database interactions into MCP-compatible AI workflows
Notes
FreePeak/db-mcp-server is a Go-based server that implements the Model Context Protocol (MCP) to give AI assistants structured access to multiple databases. It acts as a bridge, allowing language models to query and interact with databases through a standardized interface.
384 stars on GitHub. Last updated 2026-04-19. Licensed MIT.
Use cases
- Enabling AI assistants to run SQL queries against production databases
- Providing structured database access for AI-driven data analysis tools
- Integrating database interactions into MCP-compatible AI workflows
Pros
- Written in Go, offering good performance and low resource usage
- Supports multiple database types through a single MCP interface
- Open source with a growing community (384 stars)
Cons
- Requires MCP-compatible AI assistants, limiting direct usability
- Documentation may be sparse for advanced configuration
- Not a full ORM; focuses on raw query access
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Written in Go, offering good performance and low resource usage
- Supports multiple database types through a single MCP interface
- Open source with a growing community (384 stars)
Cons
- Requires MCP-compatible AI assistants, limiting direct usability
- Documentation may be sparse for advanced configuration
- Not a full ORM; focuses on raw query access
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.