🤖 MCP
Install a client
Other clients

Other clients

The server is a standard MCP server. Nothing about it is specific to the clients documented here, so any client that can meet the requirements below will work.

Connecting with a key

RequirementValue
TransportStreamable HTTP
MethodPOST to https://upsell.avada.io/mcp
Protocol version2025-06-18
AuthenticationA request header — Authorization: Bearer aov_mcp_…

The one hard requirement is the header. A client that cannot set an arbitrary request header cannot authenticate this way, and no amount of configuration works around it.

Connecting by signing in

RequirementValue
Addresshttps://upsell.avada.io/oauth/mcp
AuthorizationOAuth 2.1 with PKCE (S256)
Client registrationDynamic — RFC 7591 (opens in a new tab)
DiscoveryRFC 9728 (opens in a new tab) protected-resource metadata, and RFC 8414 (opens in a new tab) authorization-server metadata
Grantauthorization_code only
Scopesread, write, manage — the merchant chooses which one is granted

A client that supports custom MCP connectors over OAuth needs only the address; it registers itself, and the merchant approves the connection in the app with a one-time code.

The two addresses are separate on purpose. A client pointed at the wrong one fails in a way that looks like a bad credential: /mcp never offers a sign-in flow, and /oauth/mcp never accepts a static key.

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.

Clients that are not supported yet

Gemini, Perplexity and Sidekick appear in the app's client list but are not connectable — they are shown so you can see what is coming rather than search for a setup that does not exist. Any of them will work through the generic routes above if the product itself supports custom MCP servers.

Related

Product
Install AppWebsiteAvada Apps
Resources
DocumentationFAQPrivacy Policy
Company
Avada GroupContact
© 2026 Avada Group. All rights reserved.