Mercatus MCP Bridge

Local stdio-to-HTTP bridge for the Mercatus Enterprise MCP Server. This bridge allows standard MCP clients (which communicate via standard input/output) to connect to the HTTP-based Mercatus MCP Server.

How to Configure in AI Clients

Add the following block to your client's configuration file. Select the environment that corresponds to your target MCP server:

1. Local Development (Local MCP Server running on port 5060)

Antigravity / Codex

Config path: ~/.gemini/antigravity/mcp_config.json

{
  "mcpServers": {
    "mercatus-enterprise": {
      "command": "npx",
      "args": ["-y", "mercatus-mcp-bridge"],
      "env": {
        "MCP_SERVER_URL": "http://127.0.0.1:5060/internal/v1/mcp",
        "X_USER_CLIENT_ID": "YOUR_CLIENT_ID",
        "X_USER_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "X_TENANT_ID": "10006"
      }
    }
  }
}

Claude Desktop

Config path: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mercatus-mcp": {
      "command": "npx",
      "args": ["-y", "mercatus-mcp-bridge"],
      "env": {
        "MCP_SERVER_URL": "http://127.0.0.1:5060/internal/v1/mcp",
        "X_USER_CLIENT_ID": "YOUR_CLIENT_ID",
        "X_USER_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "X_TENANT_ID": "10006"
      }
    }
  }
}

2. Staging / Remote Environment

Antigravity / Codex

Config path: ~/.gemini/antigravity/mcp_config.json

{
  "mcpServers": {
    "mercatus-enterprise": {
      "command": "npx",
      "args": ["-y", "mercatus-mcp-bridge"],
      "env": {
        "MCP_SERVER_URL": "https://dev-api-ai.mercatus.com/gateway/gcp-service-mcp-server/v1.0/internal/v1/mcp",
        "X_USER_CLIENT_ID": "YOUR_CLIENT_ID",
        "X_USER_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "X_TENANT_ID": "10006"
      }
    }
  }
}

Claude Desktop

Config path: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mercatus-mcp": {
      "command": "npx",
      "args": ["-y", "mercatus-mcp-bridge"],
      "env": {
        "MCP_SERVER_URL": "https://dev-api-ai.mercatus.com/gateway/gcp-service-mcp-server/v1.0/internal/v1/mcp",
        "X_USER_CLIENT_ID": "YOUR_CLIENT_ID",
        "X_USER_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "X_TENANT_ID": "10006"
      }
    }
  }
}

Local Development & Testing

1. Test running locally (without packing)

node mcp-bridge.js

2. Test package locally using a tarball

# Generate packed tarball (e.g. mercatus-mcp-bridge-1.0.0.tgz)
npm pack

# Test executing the tarball with a mock JSON-RPC initialization request
echo '{"jsonrpc": "2.0", "id": 1, "method": "initialize", "params": {"protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": {"name": "test", "version": "1.0"}}}' | npx ./mercatus-mcp-bridge-1.0.0.tgz

Publishing Updates to NPM

To publish modifications to the NPM registry:

1. Authenticate with NPM (if not already logged in)

npm login

2. Increment the package version

Select the appropriate level based on your changes:

# For bug fixes / patches (e.g., 1.0.0 -> 1.0.1)
npm version patch

# For minor features / non-breaking additions (e.g., 1.0.0 -> 1.1.0)
npm version minor

# For major / breaking API changes (e.g., 1.0.0 -> 2.0.0)
npm version major

3. Publish to NPM

npm publish

(The package is pre-configured to publish publicly automatically).