mcp-proxy

This MCP server implements a basic proxy for remote MCP servers, providing a Streamable HTTP transport with a stdio-style facade. It is tailored for Imandra Universe MCP servers and supports Imandra Universe authentication. The recommended way to run it is via npx, which ships with npm, allowing you to execute the proxy directly from GitHub. To configure it, supply your Imandra API key and the target MCP server name via environment variables, and optionally specify the remote MCP URL if you’re targeting a custom or dev instance. Once running, clients can connect through the stdio-style interface exposed by the proxy, which then forwards requests to the remote MCP server and streams responses back over HTTP in a compatible format.

Prerequisites:

• Node.js and npm installed on your machine (npx comes with npm).

Installation steps:

1. Ensure Node.js and npm are installed. You can verify with:

   • node -v
   • npm -v

2. No global installation is strictly required since this runs via npx, but you can test by installing the package references locally if needed:

   • npm install -g npm

3. Run the proxy using npx (the recommended approach):

   • npx -y github:imandra-ai/mcp-proxy

4. Alternatively, if you want to point at a fork or a specific branch, you can adjust the npx command accordingly (e.g., npx -y github:your-org/mcp-proxy).

5. Verify the configuration by ensuring the environment variables are set (see mcp_config) and that the proxy starts up without errors.

Notes and tips:

• The proxy relies on Imandra Universe authentication. Set IMANDRA_API_KEY to a valid API key and IMANDRA_MCP_SERVER to the target Imandra Universe MCP server (e.g., reasoner_gateway).
• REMOTE_URL is optional. If omitted, the proxy will default to https://api.imandra.ai/v1beta1/tools/mcp/${IMANDRA_MCP_SERVER}.
• The example configuration uses the server-name imandra-universe/reasoners; you can adjust the server-name to match your deployment naming conventions.
• If you encounter SSH permission issues when npx fetches the repository, ensure your SSH keys are properly configured or switch to an https-based Git URL if supported.
• This proxy focuses on Streamable HTTP transport with a stdio facade; clients must be compatible with that interface. Ensure your client configuration aligns with the Streamable HTTP and stdio transport expectations.
• Monitor environment variables for sensitive values and avoid hard-coding API keys in shared configuration files.