1. Home
  2. mcp-proxy
  3. mcp-proxy for Cursor: Setup & Config

Data as of

mcp-proxy for Cursor: Setup & Config

Cursor: mcp-proxy bridges MCP transport mismatches between clients and servers.

What you can do with mcp-proxy in Cursor

Pick it to bridge existing MCP transports and route named local servers without replacing their tools.

  • Route multiple named local servers behind separate URL paths.
  • Pass authentication headers or OAuth2 credentials to an upstream service.

Before you start: mcp-proxy in Cursor

  • mcp-proxy installed using uv or pipx
  • uvx and the mcp-server-fetch package for this documented example
  • An MCP-compatible client

This README example exposes a local fetch stdio server through the proxy. Install mcp-proxy with uv tool install mcp-proxy or pipx install mcp-proxy first. The opposite mode takes an upstream URL; choose --transport=streamablehttp for a Streamable HTTP upstream.

mcp-proxy Cursor configuration

  1. Choose Cursor configuration scope

    For mcp-proxy, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add mcp-proxy to Cursor

    Use the mcp-proxy entry below in mcpServers. Keep mcp-proxy's documented sse connection fields and your other Cursor entries.

  3. Check mcp-proxy in Cursor

    mcp-proxy: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "mcp-proxy": {
      "url": "http://127.0.0.1:8080/sse"
    }
  }
}

Troubleshooting mcp-proxy in Cursor

  • Enable mcp-proxy in Cursor's MCP settings and inspect its tools. For 127.0.0.1:8080, check reachability, transport, and credential expiry if authentication fails.
  • mcp-proxy: check sse connectivity to 127.0.0.1:8080 from Cursor; a stdio command is not a replacement for this endpoint.
  • Transport mismatch: mcp-proxy's catalog lists stdio; the displayed Cursor configuration uses sse.
  • Known limitation: Wrapped server executables and dependencies must be available separately.
  • Known limitation: The default container image does not include uv.
  • Known limitation: Named-server timeout and transportType fields are ignored.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

mcp-proxy — details. Cursor guide

Frequently asked questions

Cursor's mcp-proxy entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's mcp-proxy example uses sse. The mcp-proxy catalog lists stdio; these instructions follow the stored configuration instead.

Cursor connects mcp-proxy to 127.0.0.1:8080 using url.

Yes. Named servers can be configured on the command line or through a JSON file and receive separate URL paths.

No. The README explicitly says uv is not included by default and shows how to extend the image.