Other clients
The server is a standard MCP server. Nothing about it is specific to the three clients documented here, so any client that can meet the requirements below will work.
What a client needs
| Requirement | Value |
|---|---|
| Transport | Streamable HTTP |
| Method | POST to https://upsell.avada.io/mcp |
| Protocol version | 2025-06-18 |
| Authentication | A request header — Authorization: Bearer aov_mcp_… |
The one hard requirement is the header. A client that cannot set an arbitrary request header cannot authenticate, and no amount of configuration works around it.
If your client cannot set headers
Use mcp-remote as a bridge, the same way Claude Desktop does. It
takes a --header argument and speaks stdio to the client on the other side, so any client that can
launch a local command can reach the server through it. That path needs Node.js 18 or newer.
ChatGPT and claude.ai in the browser
Neither can connect today.
Both accept a custom MCP server by name and URL only, and expect the server to authenticate through a browser sign-in flow. There is no field for a key, so the credential this server uses has nowhere to go. Adding the URL on its own produces a connector that fails on the first call.
This is a limitation of how the server authenticates, not of those products. Browser sign-in support is planned; until it ships, use a client that can send a header.