Cloudflare Remote PostgreSQL Database MCP Server + GitHub OAuth

This is a Model Context Protocol (MCP) server that enables you to chat with your PostgreSQL database, deployable as a remote MCP server with GitHub OAuth through Cloudflare. This is production ready MCP.

Key Features

• 🗄️ Database Integration with Lifespan: Direct PostgreSQL database connection for all MCP tool calls
• 🛠️ Modular, Single Purpose Tools: Following best practices around MCP tools and their descriptions
• 🔐 Role-Based Access: GitHub username-based permissions for database write operations
• 📊 Schema Discovery: Automatic table and column information retrieval
• 🛡️ SQL Injection Protection: Built-in validation and sanitization
• 📈 Monitoring: Optional Sentry integration for production monitoring
• ☁️ Cloud Native: Powered by Cloudflare Workers for global scale

Modular Architecture

This MCP server uses a clean, modular architecture that makes it easy to extend and maintain:

• `src/tools/` - Individual tool implementations in separate files
• `registerAllTools()` - Centralized tool registration system
• Extensible Design - Add new tools by creating files in tools/ and registering them

This architecture allows you to easily add new database operations, external API integrations, or any other MCP tools while keeping the codebase organized and maintainable.

Transport Protocols

This MCP server supports both modern and legacy transport protocols:

• `/mcp` - Streamable HTTP (recommended): Uses a single endpoint with bidirectional communication, automatic connection upgrades, and better resilience for network interruptions
• `/sse` - Server-Sent Events (legacy): Uses separate endpoints for requests/responses, maintained for backward compatibility

For new implementations, use the /mcp endpoint as it provides better performance and reliability.

How It Works

The MCP server provides three main tools for database interaction:

1. `listTables` - Get database schema and table information (all authenticated users)
2. `queryDatabase` - Execute read-only SQL queries (all authenticated users)
3. `executeDatabase` - Execute write operations like INSERT/UPDATE/DELETE (privileged users only)

Authentication Flow: Users authenticate via GitHub OAuth → Server validates permissions → Tools become available based on user's GitHub username.

Security Model:

• All authenticated GitHub users can read data
• Only specific GitHub usernames can write/modify data
• SQL injection protection and query validation built-in

Simple Example First

Want to see a basic MCP server before diving into the full database implementation? Check out src/simple-math.ts - a minimal MCP server with a single calculate tool that performs basic math operations (add, subtract, multiply, divide). This example demonstrates the core MCP components: server setup, tool definition with Zod schemas, and dual transport support (/mcp and /sse endpoints). You can run it locally with wrangler dev --config wrangler-simple.jsonc and test at http://localhost:8789/mcp.

Prerequisites

• Node.js 20 LTS (or 18 LTS) installed on your machine
• A Cloudflare account (free tier works)
• A GitHub account for OAuth setup
• A PostgreSQL database (local or hosted)

Getting Started

Step 1: Install Wrangler CLI

Install Wrangler globally to manage your Cloudflare Workers. Wrangler and some of its transitive dependencies have not yet declared support for Node.js 22+, which leads to unsupported engine warnings during installation. Use Node.js 20 LTS (or 18 LTS) to avoid those warnings. If you use nvm, you can switch to Node.js 20 with:

nvm install 20
nvm use 20

Then install Wrangler globally:

npm install -g wrangler

Step 2: Authenticate with Cloudflare

Log in to your Cloudflare account:

wrangler login

This will open a browser window where you can authenticate with your Cloudflare account.

Step 3: Clone and Setup

Clone the repo directly & install dependencies: npm install.

Environment Variables Setup

Before running the MCP server, you need to configure several environment variables for authentication and database access.

Create Environment Variables File

1. Create your `.dev.vars` file from the example:

   cp .dev.vars.example .dev.vars

1. Configure all required environment variables in .dev.vars:

   # GitHub OAuth (for authentication)
   GITHUB_CLIENT_ID=your_github_client_id
   GITHUB_CLIENT_SECRET=your_github_client_secret
   COOKIE_ENCRYPTION_KEY=your_random_encryption_key

   # Database Connection
   DATABASE_URL=postgresql://username:password@localhost:5432/database_name

   # Optional: Sentry monitoring
   SENTRY_DSN=https://[email protected]/project-id
   NODE_ENV=development

Getting GitHub OAuth Credentials

1. Create a GitHub OAuth App for local development:

• Go to GitHub Developer Settings
• Click "New OAuth App"
• Application name: MCP Server (Local Development)
• Homepage URL: http://localhost:8792
• Authorization callback URL: http://localhost:8792/callback
• Click "Register application"

1. Copy your credentials:

• Copy the Client ID and paste it as GITHUB_CLIENT_ID in .dev.vars
• Click "Generate a new client secret", copy it, and paste as GITHUB_CLIENT_SECRET in .dev.vars

Generate Encryption Key

Generate a secure random encryption key for cookie encryption:

openssl rand -hex 32

Copy the output and paste it as COOKIE_ENCRYPTION_KEY in .dev.vars.

Database Setup

1. Set up PostgreSQL using a hosted service like:

• Supabase (recommended for beginners)
• Neon
• Or use local PostgreSQL/Supabase

1. Update the DATABASE_URL in .dev.vars with your connection string:

   DATABASE_URL=postgresql://username:password@host:5432/database_name

#### Connection String Examples:

• Local: postgresql://myuser:mypass@localhost:5432/mydb
• Supabase: postgresql://postgres:[email protected]:5432/postgres

Database Schema Setup

The MCP server works with any PostgreSQL database schema. It will automatically discover:

• All tables in the public schema
• Column names, types, and constraints
• Primary keys and indexes

Testing the Connection: Once you have your database set up, you can test it by asking the MCP server "What tables are available in the database?" and then querying those tables to explore your data.

Local Development & Testing

Run the server locally:

   wrangler dev

This makes the server available at http://localhost:8792

Testing with MCP Inspector

Use the MCP Inspector to test your server:

1. Install and run Inspector:

   npx @modelcontextprotocol/inspector@latest

1. Connect to your local server:

• Preferred: Enter URL: http://localhost:8792/mcp (streamable HTTP transport - newer, more robust)
• Alternative: Enter URL: http://localhost:8792/sse (SSE transport - legacy support)
• Click "Connect"
• Follow the OAuth prompts to authenticate with GitHub
• Once connected, you'll see the available tools

1. Test the tools:

• Use listTables to see your database structure
• Use queryDatabase to run SELECT queries
• Use executeDatabase (if you have write access) for INSERT/UPDATE/DELETE operations

Production Deployment

#### Set up a KV namespace

• Create the KV namespace:

wrangler kv namespace create "OAUTH_KV"

• Update the wrangler.jsonc file with the KV ID (replace <Add-KV-ID>)

#### Deploy Deploy the MCP server to make it available on your workers.dev domain

wrangler deploy

Create environment variables in production

Deploying on Cloudflare with DigitalOcean Managed PostgreSQL (WordPress)

The steps below walk you through deploying this Worker on Cloudflare while connecting it to a DigitalOcean Managed PostgreSQL cluster that mirrors a WordPress database. The result is a fully authenticated MCP agent that can read from (and optionally write to) your synced content.

1. Prepare your DigitalOcean PostgreSQL cluster

1. Create the cluster from the DigitalOcean control panel (Managed Databases → Create → PostgreSQL). Choose a region close to

your users and enable connection pooling if you expect a high read volume.

1. Migrate or sync your WordPress data into the cluster. Options include:

• Use the DigitalOcean Database Migration tool

with a dump produced by pgloader or plugins such as WP2Static + pgloader that export to PostgreSQL.

• Set up an ETL job (for example with Airbyte or a scheduled script) that keeps the PostgreSQL tables in sync with your

WordPress MySQL source.

1. Create dedicated database roles for the MCP server:

   -- run in psql against the managed cluster
   CREATE ROLE mcp_reader LOGIN PASSWORD 'super-strong-password';
   CREATE ROLE mcp_writer LOGIN PASSWORD 'super-strong-password';

   GRANT CONNECT ON DATABASE wordpress TO mcp_reader, mcp_writer;
   GRANT USAGE ON SCHEMA public TO mcp_reader, mcp_writer;
   GRANT SELECT ON ALL TABLES IN SCHEMA public TO mcp_reader;
   GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO mcp_writer;
   ALTER DEFAULT PRIVILEGES IN SCHEMA public
     GRANT SELECT ON TABLES TO mcp_reader;
   ALTER DEFAULT PRIVILEGES IN SCHEMA public
     GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO mcp_writer;

Give the read-only connection string to all users, and reserve the writer credentials for trusted GitHub usernames listed in ALLOWED_USERNAMES.

2. Configure Cloudflare Worker secrets

1. Authenticate Wrangler (wrangler login) and select the account that will host the Worker.
2. Set the GitHub OAuth and cookie secrets:

   wrangler secret put GITHUB_CLIENT_ID
   wrangler secret put GITHUB_CLIENT_SECRET
   wrangler secret put COOKIE_ENCRYPTION_KEY

1. Store your DigitalOcean PostgreSQL URL. Use the mcp_reader credentials for general access, and optionally create a separate

secret for the writer role if you plan to allow writes:

   # Example connection string from the DO control panel
   wrangler secret put DATABASE_URL
   # postgresql://mcp_reader:super-strong-password@db-postgresql-nyc3-12345-do-user-67890-0.b.db.ondigitalocean.com:25060/wordpress?sslmode=require

1. (Optional) Add Sentry DSN or other monitoring secrets the same way.

3. Bind the OAuth KV namespace

After creating the namespace (wrangler kv namespace create "OAUTH_KV"), add it to wrangler.jsonc (or wrangler-simple.jsonc for the demo) under kv_namespaces. This KV store keeps transient OAuth approvals so the consent dialog can be skipped on subsequent logins.

4. Deploy and verify the Worker

1. Run wrangler deploy to publish the Worker.
2. Visit https://<your-worker>.workers.dev/authorize?client_id=<mcp-client-id>&redirect_uri=<...> via the MCP Inspector or your

MCP client to complete the OAuth handshake.

1. Once authenticated, use the listTables and queryDatabase tools to confirm the Worker can read from the DigitalOcean

cluster. If you granted write access to any GitHub usernames, test the executeDatabase tool from one of those accounts.

5. Keep the WordPress sync healthy

• Schedule regular health checks that compare row counts between MySQL and PostgreSQL or verify recent post IDs.
• Use DigitalOcean alerts to track connection

saturation and query latency. Cloudflare Workers reuse outbound connections automatically, but you can lower latency further by enabling Workers Dedicated Egress and allow-listing those IPs on the database.

• If you rotate credentials, update the corresponding Worker secret with wrangler secret put DATABASE_URL and redeploy.

With this setup, your MCP agent can safely access the synchronized WordPress content through Cloudflare Workers while DigitalOcean manages the underlying PostgreSQL infrastructure. Create a new GitHub OAuth App:

• For the Homepage URL, specify https://mcp-github-oauth.<your-subdomain>.workers.dev
• For the Authorization callback URL, specify https://mcp-github-oauth.<your-subdomain>.workers.dev/callback
• Note your Client ID and generate a Client secret.
• Set all required secrets via Wrangler:

wrangler secret put GITHUB_CLIENT_ID
wrangler secret put GITHUB_CLIENT_SECRET
wrangler secret put COOKIE_ENCRYPTION_KEY  # use: openssl rand -hex 32
wrangler secret put DATABASE_URL
wrangler secret put SENTRY_DSN  # optional (more on Sentry setup below)

#### Test

Test the remote server using Inspector:

npx @modelcontextprotocol/inspector@latest

Enter https://mcp-github-oauth.<your-subdomain>.workers.dev/mcp (preferred) or https://mcp-github-oauth.<your-subdomain>.workers.dev/sse (legacy) and hit connect. Once you go through the authentication flow, you'll see the Tools working:

<img width="640" alt="image" src="https://github.com/user-attachments/assets/7973f392-0a9d-4712-b679-6dd23f824287" />

You now have a remote MCP server deployed!

Database Tools & Access Control

Available Tools

#### 1. listTables (All Users) Purpose: Discover database schema and structure Access: All authenticated GitHub users Usage: Always run this first to understand your database structure

Example output:
- Tables: users, products, orders
- Columns: id (integer), name (varchar), created_at (timestamp)
- Constraints and relationships

#### 2. queryDatabase (All Users) Purpose: Execute read-only SQL queries Access: All authenticated GitHub users Restrictions: Only SELECT statements and read operations allowed

-- Examples of allowed queries:
SELECT * FROM users WHERE created_at > '2024-01-01';
SELECT COUNT(*) FROM products;
SELECT u.name, o.total FROM users u JOIN orders o ON u.id = o.user_id;

#### 3. executeDatabase (Privileged Users Only) Purpose: Execute write operations (INSERT, UPDATE, DELETE, DDL) Access: Restricted to specific GitHub usernames Capabilities: Full database write access including schema modifications

-- Examples of allowed operations:
INSERT INTO users (name, email) VALUES ('New User', '[email protected]');
UPDATE products SET price = 29.99 WHERE id = 1;
DELETE FROM orders WHERE status = 'cancelled';
CREATE TABLE new_table (id SERIAL PRIMARY KEY, data TEXT);

Access Control Configuration

Database write access is controlled by GitHub username in the ALLOWED_USERNAMES configuration:

// Add GitHub usernames for database write access
const ALLOWED_USERNAMES = new Set([
  'yourusername',    // Replace with your GitHub username
  'teammate1',       // Add team members who need write access
  'database-admin'   // Add other trusted users
]);

To update access permissions:

1. Edit src/index.ts and src/index_non_sentry.ts
2. Update the ALLOWED_USERNAMES set with GitHub usernames
3. Redeploy the worker: wrangler deploy

Typical Workflow

1. 🔍 Discover: Use listTables to understand database structure
2. 📊 Query: Use queryDatabase to read and analyze data
3. ✏️ Modify: Use executeDatabase (if you have write access) to make changes

Security Features

• SQL Injection Protection: All queries are validated before execution
• Operation Type Detection: Automatic detection of read vs write operations
• User Context Tracking: All operations are logged with GitHub user information
• Connection Pooling: Efficient database connection management
• Error Sanitization: Database errors are cleaned before being returned to users

Access the remote MCP server from Claude Desktop

Open Claude Desktop and navigate to Settings -> Developer -> Edit Config. This opens the configuration file that controls which MCP servers Claude can access.

Replace the content with the following configuration. Once you restart Claude Desktop, a browser window will open showing your OAuth login page. Complete the authentication flow to grant Claude access to your MCP server. After you grant access, the tools will become available for you to use.

{
  "mcpServers": {
    "math": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp-github-oauth.<your-subdomain>.workers.dev/mcp"
      ]
    }
  }
}

Once the Tools (under 🔨) show up in the interface, you can ask Claude to interact with your database. Example commands:

• "What tables are available in the database?" → Uses listTables tool
• "Show me all users created in the last 30 days" → Uses queryDatabase tool
• "Add a new user named John with email [email protected]" → Uses executeDatabase tool (if you have write access)

Using Claude and other MCP Clients

When using Claude to connect to your remote MCP server, you may see some error messages. This is because Claude Desktop doesn't yet support remote MCP servers, so it sometimes gets confused. To verify whether the MCP server is connected, hover over the 🔨 icon in the bottom right corner of Claude's interface. You should see your tools available there.

#### Using Cursor and other MCP Clients

To connect Cursor with your MCP server, choose Type: "Command" and in the Command field, combine the command and args fields into one (e.g. npx mcp-remote https://<your-worker-name>.<your-subdomain>.workers.dev/sse).

Note that while Cursor supports HTTP+SSE servers, it doesn't support authentication, so you still need to use mcp-remote (and to use a STDIO server, not an HTTP one).

You can connect your MCP server to other MCP clients like Windsurf by opening the client's configuration file, adding the same JSON that was used for the Claude setup, and restarting the MCP client.

Sentry Integration (Optional)

This project includes optional Sentry integration for comprehensive error tracking, performance monitoring, and distributed tracing. There are two versions available:

• src/index.ts - Standard version without Sentry
• src/index_sentry.ts - Version with full Sentry integration

Setting Up Sentry

1. Create a Sentry Account: Sign up at sentry.io if you don't have an account.

1. Create a New Project: Create a new project in Sentry and select "Cloudflare Workers" as the platform (search in the top right).

1. Get Your DSN: Copy the DSN from your Sentry project settings.

Using Sentry in Production

To deploy with Sentry monitoring:

1. Set the Sentry DSN secret:

   wrangler secret put SENTRY_DSN

Enter your Sentry DSN when prompted.

1. Update your wrangler.toml to use the Sentry-enabled version:

   main = "src/index_sentry.ts"

1. Deploy with Sentry:

   wrangler deploy

Using Sentry in Development

1. Add Sentry DSN to your `.dev.vars` file:

   SENTRY_DSN=https://[email protected]/project-id
   NODE_ENV=development

1. Run with Sentry enabled:

   wrangler dev

Sentry Features Included

• Error Tracking: Automatic capture of all errors with context
• Performance Monitoring: Full request tracing with 100% sample rate
• User Context: Automatically binds GitHub user information to events
• Tool Tracing: Each MCP tool call is traced with parameters
• Custom Error Handling: User-friendly error messages with Event IDs
• Context Enrichment: Automatic tagging and context for better debugging

How does it work?

#### OAuth Provider The OAuth Provider library serves as a complete OAuth 2.1 server implementation for Cloudflare Workers. It handles the complexities of the OAuth flow, including token issuance, validation, and management. In this project, it plays the dual role of:

• Authenticating MCP clients that connect to your server
• Managing the connection to GitHub's OAuth services
• Securely storing tokens and authentication state in KV storage

#### Durable MCP Durable MCP extends the base MCP functionality with Cloudflare's Durable Objects, providing:

• Persistent state management for your MCP server
• Secure storage of authentication context between requests
• Access to authenticated user information via this.props
• Support for conditional tool availability based on user identity

#### MCP Remote The MCP Remote library enables your server to expose tools that can be invoked by MCP clients like the Inspector. It:

• Defines the protocol for communication between clients and your server
• Provides a structured way to define tools
• Handles serialization and deserialization of requests and responses
• Maintains the Server-Sent Events (SSE) connection between clients and your server

Testing

This project includes comprehensive unit tests covering all major functionality:

npm test        # Run all tests
npm run test:ui # Run tests with UI

The test suite covers database security, tool registration, permission handling, and response formatting with proper mocking of external dependencies.