Overview

What is MCP HTTP Demo Server?

It is a simple demo MCP HTTP server designed for use with MCP clients such as claude.ai. It integrates with Pomerium for access control and requires database persistence for client registrations.

How to use MCP HTTP Demo Server?

Configure a Pomerium route with MCP enabled and a domain pointing to the server, set up a PostgreSQL databroker, and deploy the server and its SQLite database using the provided Docker Compose configuration.

Key features of MCP HTTP Demo Server

• Demo MCP HTTP server for MCP clients
• Uses Pomerium for secure access control
• Requires database persistence for client registrations
• Supports SQLite database integration
• Includes Docker Compose deployment configuration

Use cases of MCP HTTP Demo Server

• Demonstrate MCP server functionality with claude.ai
• Test MCP server with a sample SQLite database
• Deploy a secure MCP server using Pomerium authentication

FAQ from MCP HTTP Demo Server

What is the purpose of this server?

It is a simple demo MCP HTTP server for use with compatible MCP clients like claude.ai.

How do I protect access to the server?

Access must be protected using Pomerium, an identity-aware proxy.

Do I need to set up database persistence?

Yes, you need to set up database persistence to keep client registrations and other data.

What database does the server use?

The server uses SQLite; a test database (Northwind) can be obtained from the jpwhite3/northwind-SQLite3 repository.

How do I configure the Pomerium route?

The route must include a domain in the from field, enable MCP, point to the MCP server, and set authentication policies (e.g., domain-based allow rules).