acehoss/mcp-gateway

A flexible gateway server that bridges Model Context Protocol (MCP) STDIO servers to MCP HTTP+SSE and REST API, enabling multi-instance MCP servers to be exposed over HTTP.
## Features
Run multiple instances of the same MCP server type
Configure multiple different MCP server types
Flexible network binding configuration
Clean separation between server instances using session IDs
Automatic cleanup of server resources on connection close
YAML-based configuration
Optional Basic and Bearer token authentication
Configurable debug logging levels
REST API Support
## REST API Support
MCP Gateway now provides a REST API interface to MCP servers, making them accessible to any HTTP client that supports OpenAPI/Swagger specifications. This feature is particularly useful for integrating with OpenAI's custom GPTs and other REST API clients.
### REST API Endpoints
Before making tool calls, you need to get a session ID:
bash
curl "http://localhost:3000/api/sessionid"
# Returns: {"sessionId": " "}
Each tool exposed by an MCP server is available at:
POST /api/{serverName}/{toolName}?sessionId={session-id}
Note: The sessionId query parameter is required for all tool calls.
For example, to call the directorytree tool on a filesystem MCP server:
bash
# First get a session ID
SESSIONID=$(curl -s "http://localhost:3000/api/sessionid" | jq -r .sessionId)
# Then make the tool call
curl -X POST "http://localhost:3000/api/filesystem/directorytree?sessionId=$SESSIONID" \
-H "Content-Type: application/json" \
-d '{"path": "/some/path"}'
### OpenAPI Schema Generation
The gateway can generate OpenAPI schemas for all configured tools, making it easy to integrate with OpenAPI-compatible clients:
bash
# Generate YAML format (default)
npm start -- --schemaDump
# Generate JSON format
npm start -- --schemaDump --schemaFormat json
The generated schema includes:
All available endpoints for each configured server
Tool descriptions and parameter schemas
Request/response formats
Authentication requirements
## Purpose
At the moment, most MCP servers are designed for local execution. MCP Gateway enables HTTP+SSE capable clients to interact with MCP servers running on remote machines. This addresses common deployment scenarios, such as running LibreChat in a containerized environment where certain MCP servers, like the Puppeteer server, may have limited functionality. MCP Gateway provides a robust solution for distributing MCP servers across multiple machines while maintaining seamless connectivity.
## Security Features
MCP Gateway supports two authentication methods that can be enabled independently:
1. Basic Authentication: Username/password pairs
2. Bearer Token Authentication: Token-based authentication
Both methods can be enabled simultaneously, and any valid authentication will grant access.
### Authentication Configuration
Add authentication settings to your config.yaml:
yaml
auth:
basic:
enabled: true
credentials:
username: "admin"
password: "your-secure-password"
# Add more username/password pairs as needed
bearer:
enabled: true
tokens:
"your-secure-token"
# Add more tokens as needed
### Using Authentication
#### Basic Authentication
bash
curl -u username:password http://localhost:3000/serverName