db-mcp
by wasaga
This is a simple demo MCP HTTP server designed for use with claude.ai or other compatible MCP clients. It requires protection via Pomerium and database persistence for client registrations.
Last updated: N/A
What is db-mcp?
db-mcp is a demo MCP (Message Communication Protocol) HTTP server. It's designed to act as a backend for MCP clients, such as claude.ai, facilitating communication and data exchange.
How to use db-mcp?
To use db-mcp, you need to configure it with a database for persistence and protect it with Pomerium for access control. The provided config.yaml and docker-compose.yml files offer a starting point. You'll need to set up the database connection string and configure the Pomerium routes to point to your db-mcp instance.
Key features of db-mcp
MCP Compatibility
HTTP Interface
Database Persistence
Pomerium Integration
Docker Compose Support
Use cases of db-mcp
Integrating claude.ai with a database
Building custom MCP-based applications
Testing and experimenting with MCP protocols
Providing a secure MCP endpoint for internal services
FAQ from db-mcp
What is MCP?
What is MCP?
MCP stands for Message Communication Protocol. It's a protocol for exchanging messages between different systems.
Why do I need Pomerium?
Why do I need Pomerium?
Pomerium provides secure access control to the db-mcp server, ensuring that only authorized clients can interact with it.
What database systems are supported?
What database systems are supported?
The provided configuration uses PostgreSQL, but other database systems can be used by modifying the databroker_storage_type and databroker_storage_connection_string.
How do I configure the domain name?
How do I configure the domain name?
The domain name is configured in the from field of the Pomerium route. Make sure to replace db-mcp.your-domain.com with your actual domain.
Where can I find a test database?
Where can I find a test database?
A test SQLite database is available at https://github.com/jpwhite3/northwind-SQLite3