hasmcp-ce

HasMCP-CE is a backend service that lets you automatically generate MCP Servers from OpenAPI v3+ specs or manually map API endpoints to MCP methods. It includes OAuth2 authentication, per-server endpoint toggles, optional proxy headers to your real API endpoints, and per-server token management alongside real-time call logs and analytics. The recommended deployment is via Docker: you run the container, expose HTTP/HTTPS, and configure the server via a .env file. Once running, you can create MCP configurations by supplying OpenAPI specs (or manual mappings) and HasMCP-CE will present you with an MCP server that translates tool calls into the defined MCP endpoints. You can monitor usage and logs in real time, adjust SSL with Let’s Encrypt if you enable it, and tune authentication tokens per server. The Docker deployment example in the README shows pulling the latest image and running it with a mounted config, while the development workflow in this repository indicates a frontend and a Go-based backend service that you run together during development.

Prerequisites:

• Docker installed on your system
• Basic familiarity with environment variables and Docker Compose (optional)

Installing HasMCP-CE (Docker, recommended):

1. Create a working directory and download the Docker image:

# Optional: stop any existing container
docker stop hasmcp-ce || true
	docker rm hasmcp-ce || true
	docker image prune -f
	docker pull hasmcp/hasmcp-ce:latest

2. Prepare environment variables. The recommended approach is to use an .env file; you can start from the example provided in the repository and customize it:

# Example .env content (adjust as needed)
# Use sqlite by default; enable Postgres only if you want to switch to Postgres
POSTGRES_ENABLED=false
POSTGRES_TIMEZONE=UTC
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_HOST=localhost
POSTGRES_PORT=5432
POSTGRES_DBNAME=postgres

3. Run HasMCP-CE with Docker using the environment file:

docker stop hasmcp-ce || true; \
 docker rm hasmcp-ce || true; \
 docker image prune -f; \
 docker run --env-file .env -p 80:80 -p 443:443 --name hasmcp-ce \
   -v ./_certs:/_certs \
   -v ./_storage:/_storage \
   -d --restart always hasmcp/hasmcp-ce:latest

4. Access the HasMCP-CE UI and API endpoints at http://localhost (or your configured domain). For development builds, you can also run the frontend and backend separately, but the Docker method is the recommended production path.

Tips and common considerations:

• By default HasMCP-CE uses SQLite. If you need production-grade databases, the README shows how to enable Postgres via environment variables (POSTGRES_* vars).
• When using Docker, ensure that port mappings (80, 443) align with your reverse proxy or hosting setup. If you enable SSL with Let’s Encrypt, ensure those ports are reachable.
• For OpenAPI-based MCP creation, provide a valid OpenAPI v3+ spec to automatically generate endpoints. You can also toggle individual endpoints per MCP server and add optional proxy headers to forward requests to your actual backend APIs.
• Real-time logs and analytics are available per MCP server, so monitor usage and adjust tokens or authentication settings as needed.
• If you run into environment-related issues, start with the .env example and verify that the database configuration (sqlite vs Postgres) matches your deployment intention.