home / mcp / mcp gateway mcp server

MCP Gateway MCP Server

Bridges stdio MCP clients with HTTP/SSE MCP servers, enabling Claude Desktop to access diverse MCP services.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "lightconetech-mcp-gateway": {
      "command": "node",
      "args": [
        "/opt/homebrew/lib/node_modules/@mcphub/gateway/dist/src/mcphub-gateway.js"
      ],
      "env": {
        "MCP_SERVER_URL": "https://your-mcp-server.com/api/mcp"
      }
    }
  }
}

You can bridge Claude Desktop’s stdio MCP client with HTTP/SSE MCP servers using a gateway that translates between the two protocols. This lets you connect Claude Desktop to modern MCP services without changing your client setup, enabling seamless access to a wider range of MCP endpoints.

How to use

Start by ensuring the gateway is installed and your Claude Desktop client is configured to run the gateway as its MCP server. You will then point Claude Desktop to the gateway and set the MCP server URL you want to reach. The gateway accepts stdio input from Claude Desktop, forwards requests to the configured MCP server over HTTP/SSE, and translates responses back to stdio for Claude Desktop.

Usage workflow in practical terms: install the gateway, configure Claude Desktop to invoke the gateway with the correct path, set the MCP_SERVER_URL to your target MCP service, and then run Claude Desktop. When you start Claude Desktop, it will communicate through the gateway, enabling you to access MCP capabilities exposed by the HTTP/SSE server.

How to install

Prerequisites: you need Node.js and npm installed on your system.

Install the gateway globally with npm.

Find the global installation path for npm packages.

Configure Claude Desktop to run the gateway as an MCP server.

Set the MCP server URL for the gateway to connect to (optional; fallback is the default MCP Hub URL).

Configuration and troubleshooting

{
  "mcpServers": {
    "gateway": {
      "type": "stdio",
      "name": "gateway",
      "command": "node",
      "args": ["/opt/homebrew/lib/node_modules/@mcphub/gateway/dist/src/mcphub-gateway.js"],
      "env": [
        {"name": "MCP_SERVER_URL", "value": "https://your-mcp-server.com/api/mcp"}
      ]
    }
  }
}

Environment variables to configure the gateway include MCP_SERVER_URL. Set this to the MCP server you want to use, for example https://your-mcp-server.com/api/mcp. If you do not set it, the gateway will attempt to use the default MCP Hub URL unless you override it in your environment.

Common issues and checks: make sure the gateway path in Claude Desktop points to the exact runtime script, confirm Node.js and npm are installed, and verify you can reach the MCP server URL from your machine. If you encounter permission errors during installation, you may need elevated privileges; ensure you follow your operating system’s security best practices when running global npm packages.

Notes

The gateway operates as a stdio MCP server locally, translating to and from HTTP/SSE MCP servers. By configuring a single stdio MCP server entry with the correct gateway command and the MCP_SERVER_URL, you enable Claude Desktop to transparently access any compatible MCP service.