Connect Pharlo to Cursor

Status: Supported · Tested: No · Auth: OAuth 2.0 Bearer

Cursor supports remote MCP servers. Pharlo exposes a Streamable HTTP endpoint with OAuth 2.0, so it can be added as a remote server.

⚠️

We have not yet run an end-to-end verification with Cursor. The configuration below follows Cursor's documented remote-MCP format; if Cursor's MCP config schema differs in your version, follow Cursor's current docs and keep the URL and auth type below.

What you need

A Pharlo key (ds_live_...) from Settings → Credentials in the console (opens in a new tab).
A Cursor version that supports remote (HTTP) MCP servers with OAuth.

Setup

Add the server to your MCP config (~/.cursor/mcp.json or via Settings → MCP → Add server):

{
  "mcpServers": {
    "pharlo": {
      "url": "https://pharlo.io/_mcp"
    }
  }
}

On first use, Cursor opens the OAuth consent screen in your browser. Enter your ds_live_... key and authorize. Cursor stores the resulting OAuth tokens and refreshes them automatically.

There is no API-key field for /_mcp. The ds_live_... key is entered only on the OAuth consent screen; the server issues short-lived Bearer tokens in exchange.

Troubleshooting

No consent screen — your Cursor version may only support local stdio servers. Update Cursor or use a client from the compatibility matrix.
401 on tool calls — re-authorize; confirm the URL is exactly https://pharlo.io/_mcp.

Limitations

MCP requests carry a 20% credit surcharge over direct REST calls.

Claude Windsurf