MCP Integration
Connection Setup
Windsurf

Connect Pharlo to Windsurf

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

Windsurf (Cascade) supports remote MCP servers. Pharlo's Streamable HTTP + OAuth 2.0 endpoint can be added as a remote server.

⚠️

We have not yet run an end-to-end verification with Windsurf. The configuration below follows Windsurf's documented remote-MCP format; if your version's schema differs, follow Windsurf'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 Windsurf version that supports remote (HTTP) MCP servers with OAuth.

Setup

Add the server via Windsurf → Settings → Cascade → MCP Servers → Add, or edit the MCP config file:

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

On first connection, Windsurf opens the OAuth consent screen in your browser. Enter your ds_live_... key and authorize.

The ds_live_... key is used only on the OAuth consent screen. The server returns short-lived Bearer tokens; there is no static API-key header for /_mcp.

Troubleshooting

  • Server won't connect — confirm your Windsurf version supports remote OAuth MCP servers, not just local commands.
  • 401 on tool calls — re-authorize; verify the URL is exactly https://pharlo.io/_mcp.

Limitations

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

Related docs

Connection Setup overview · Compatibility matrix · Tool reference

CursorChatGPT