The guides in this section cover six clients. Another MCP client can connect too, as long as it meets the three conditions below. This page also lists the clients that cannot sign in to plnnrly yet.
What a client needs
- It connects to remote MCP servers over streamable HTTP.
- It signs in with OAuth and registers itself with plnnrly while doing so (dynamic client registration).
- It returns from the sign-in to an address plnnrly accepts.
Return addresses plnnrly accepts
After you approve the connection, plnnrly sends you back to the client. plnnrly accepts these return addresses:
claude.ai,claude.comandchatgpt.com- an address on your own computer (
localhost,127.0.0.1or[::1]), which desktop and terminal clients use - Cursor's own app link (
cursor://)
A client that asks for any other return address is refused when it registers, before you see the plnnrly sign-in. Its error message mentions invalid_redirect_uri.
Not supported yet
These clients cannot sign in to plnnrly yet:
- VS Code, which signs in through
vscode.dev - Antigravity CLI
- Cursor on the web and Cursor Agents, which return to
cursor.com
They fail at sign-in. This is not a setting you or your administrator can change.
Settings for any client
| Setting | Value |
|---|---|
| Server URL | https://<your-url> |
| Transport | HTTP (streamable) |
| Authentication | Sign in (OAuth), no API key or token |
<your-url> is the address you sign in to plnnrly on, such as acme.plnnrly.com, or your organisation's own domain. The client finds the sign-in endpoints itself through the standard OAuth discovery documents, so there is nothing else to enter.
Personal MCP tokens can no longer be created, so a client that only accepts a fixed token cannot connect.
Want a client added?
Ask plnnrly support. Name the client, and if you can, the address it returns to after signing in.