Client Compatibility
Which MCP clients work with the Pharlo MCP server, and what has actually been tested.
The Pharlo MCP server speaks Streamable HTTP at https://pharlo.io/_mcp and authenticates with
OAuth 2.0 Bearer tokens. Any client that supports remote (HTTP) MCP servers with OAuth 2.0 can
connect. There is no API-key path for /_mcp — the REST API key (ds_live_...) is for the REST API only.
Matrix
| Client | Supported | Tested | Auth | Setup | Notes |
|---|---|---|---|---|---|
| Claude Desktop | Yes | Yes | OAuth 2.0 Bearer | Guide | Add as a remote MCP server; completes the OAuth flow in-app. |
| Cursor | Yes | No | OAuth 2.0 Bearer | Guide | Supports remote MCP servers; not yet verified against Pharlo. |
| Windsurf | Yes | No | OAuth 2.0 Bearer | Guide | Supports remote MCP servers; not yet verified against Pharlo. |
| ChatGPT | Yes | No | OAuth 2.0 Bearer | Guide | Via MCP-compatible connectors that support remote OAuth servers. |
| n8n | Yes | No | OAuth 2.0 Bearer | Guide | Through an MCP client node pointing at the Streamable HTTP endpoint. |
| Generic MCP runtime | Yes | No | OAuth 2.0 Bearer | Overview | Any runtime implementing Streamable HTTP + OAuth 2.0 should work. |
⚠️
"Tested: No" means we have not run an end-to-end verification with that client — not that it is known to be broken. If you connect a client successfully, the determining factor is support for remote (HTTP) MCP servers with OAuth 2.0, not the client brand.
What "Supported" requires
A client must support all of:
- Remote / HTTP MCP servers (not just local stdio servers).
- Streamable HTTP transport.
- OAuth 2.0 authorization, including the browser consent step.
Clients limited to local stdio servers cannot reach https://pharlo.io/_mcp directly.