MCPez Gateway

MCPez manages configured tool servers through a web interface and exposes a combined legacy SSE MCP gateway.

Manage a collection of tool servers

MCPez stores application and server definitions in a web management interface. A configured backend can be a local stdio process or an SSE server. The proxy discovers tools from those backends and serves a combined MCP interface. The management UI also supports exporting and importing configurations, while the playground uses configured model providers to test tool workflows.

Use the generated application route

The Docker deployment serves the web UI on a mapped port. Its documented client route is /mcp/<app_id>/sse on that deployment, with the application identifier taken from the saved configuration. The inspected handlers implement initialization, tool listing and tool calls over legacy SSE and a separate message endpoint. This is not a documented Streamable HTTP route or a single public hosted service.

Check discovery and tool routing

Configure one known backend first, start it through the manager and compare the discovered tools with the original server. Tool names are generated by the proxy during listing, so refresh discovery when testing a changed configuration. Backend credentials belong to the configured server definition. Review imported commands and environment values before enabling a configuration that launches local processes.

Project documentation

Repository and setup guide