MCP Proxy is an MCP server and proxy tool that allows clients to connect to Model Context Protocol servers over HTTP without requiring streaming transport. It is built for developers and platform engineers looking to run MCP services on simplified, standard cloud infrastructure where persistent streaming connections may be complex or unsupported. By handling standard HTTP requests, MCP Proxy sits between AI clients and local or remote MCP servers defined in its configuration. In addition to managing transport, it allows operators to manage environment variables dynamically and apply tool-level security. Administrators can define explicit allow and deny lists to restrict which tools a connected server exposes to the AI client. This makes it straightforward to host multiple MCP tools behind a unified endpoint while isolating sensitive functions, simplifying operational deployment in production environments.
Category: AI & LLM Tooling
Tags: gateway, http, proxy, transport
sh go install github.com/ubie-oss/mcp-proxy 2. Create a configuration file named config.json or config.yaml defining your servers. For example: json { "mcpServers": { "server1": { "command": "npx", "args": ["module1"], "env": { "VAR1": "$SERVER1_VAR1" } } } } 3. Start the proxy server specifying the configuration file and target port: sh go run . -config config.json -port 9090 4. Direct your HTTP-compatible MCP client to the proxy's host and port.Part of MCP Servers
You can install MCP Proxy directly using the Go toolchain by running go install github.com/ubie-oss/mcp-proxy. Ensure that Go is installed and configured in your environment before running the installation command.
MCP Proxy allows clients to communicate with MCP servers over standard HTTP without streaming transport. It can launch configured server commands, interpolate environment variables, and enforce tool filtering via allow and deny rules.
You configure tool filtering under the _extensions.tools section in your JSON or YAML configuration. If specified, only tools in the allow list are permitted, while tools in the deny list are always blocked. The deny list takes precedence.
MCP Proxy supports both JSON and YAML configuration files. The configuration format mirrors standard Claude MCP configuration files, allowing you to define commands, arguments, environment variable replacements, and extension rules.