mcp_sqlpp

A Model Context Protocol (MCP) server that provides access to the sqlpp database CLI tool through standardized tool interfaces. This enables AI development tools and agents to interact with databases through a secure, controlled interface.

Features

• MCP Protocol Compliance: Full support for the Model Context Protocol specification
• Dual Transport Support: Both STDIO and HTTP+SSE transports for flexible integration
• Database Schema Tools: Access table, view, procedure, and function schemas
• SQL Execution: Execute SQL commands with proper output formatting
• Connection Management: List and manage database connections
• Driver Information: Query available database drivers
• Comprehensive Logging: Multiple log levels with optional file logging and automatic rotation
• Containerized Deployment: Docker support with AWS App Runner deployment
• Production Ready: Comprehensive logging, health checks, monitoring, and extensive test coverage

Architecture

The server acts as a bridge between MCP clients and the sqlpp CLI tool:

MCP Client → mcp_sqlpp → sqlpp CLI (via stdin) → Database

Key Components

• MCP Server: Handles protocol communication and tool registration
• Tool Handler: Manages tool execution and parameter validation
• sqlpp Executor: Wraps sqlpp CLI execution using stdin interface with proper error handling
• Configuration System: Flexible configuration via files, environment variables, and CLI flags

Important: All SQL commands and schema queries are sent to sqlpp via stdin using the --stdin flag. The sqlpp CLI does not accept SQL commands as direct command-line arguments.

For detailed information about sqlpp integration, see SQLPP_INTEGRATION.md.

Installation

Prerequisites

• Go 1.21 or later
• sqlpp CLI tool installed and configured
  • Required: sqlpp version that supports --stdin flag and schema commands (@schema-*)
  • Verify: Run sqlpp --help to ensure --stdin flag is available
  • Test: Verify schema commands work: echo "@drivers" | sqlpp --stdin
  • Integration Details: See SQLPP_INTEGRATION.md for complete setup and configuration
• Docker (for containerized deployment)
• AWS CLI and CDK (for AWS deployment)

Local Development

1. Clone the repository:

git clone https://github.com/stainedhead/gosqlpp-mcp-server.git
cd gosqlpp-mcp-server

2. Install dependencies:

go mod download

3. Build the application:

go build -o mcp_sqlpp ./cmd/server

4. Run with default configuration:

./mcp_sqlpp

Docker Deployment

1. Build the Docker image:

docker build -f deployment/docker/Dockerfile -t mcp_sqlpp .

2. Run the container:

docker run -p 8080:8080 mcp_sqlpp --transport http

Configuration

The server supports multiple configuration methods with the following precedence:

1. Command line flags (highest priority)
2. Environment variables
3. Configuration file
4. Default values (lowest priority)

Configuration File

Create a config.yaml file:

server:
  transport: "stdio"  # or "http"
  host: "localhost"
  port: 8080

sqlpp:
  executable_path: ".bin"  # Directory containing sqlpp executable (default: .bin)
                                   # Relative paths are resolved relative to the MCP server binary location
  timeout: 300

log:
  level: "info"
  format: "text"  # or "json"
  file_logging: false  # Enable file logging with automatic rolling dates

aws:
  region: "us-east-1"
  environment: "development"

Path Resolution

Both executable_path and log files use binary-relative path resolution:

Relative Paths: Resolved relative to the MCP server binary location

sqlpp:
  executable_path: ".bin"        # Resolves to: /path/to/mc

... [View full README on GitHub](https://github.com/stainedhead/gosqlpp-mcp-server#readme)