Other clients
The server is a standard MCP server, so any client that meets the requirements below will work.
With an API key
| Requirement | Value |
|---|---|
| Transport | Streamable HTTP |
| Method | POST to the Server address shown in Settings → MCP connectors |
| Protocol version | 2025-06-18 |
| Authentication | A request header — Authorization: Bearer aov_mcp_… |
https://aov-cart-drawer.firebaseapp.com/mcpThe one hard requirement of this route is the header. A client that cannot set an arbitrary request header cannot use 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 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.
With sign-in
A client that supports remote MCP servers with OAuth can use the OAuth server URL instead, with no key:
https://aov-cart-drawer.firebaseapp.com/oauth/mcp| Requirement | Value |
|---|---|
| Authorization | Authorization code with PKCE (S256) |
| Tokens | Refresh tokens are issued |
| Client registration | Client ID metadata documents. Dynamic client registration is not offered |
| Token endpoint authentication | None (public clients) |
| Scopes | aov.read, aov.write |
When the client opens the sign-in, the app shows a one-time code; enter it under Settings → MCP connectors and approve, as described on the ChatGPT page.
A client that supports neither a custom header nor sign-in cannot connect. The two surfaces are not
interchangeable: use the key with the /mcp address and the sign-in with the /oauth/mcp address.