Skip to main content
You need the URL of the server you want to connect (which one?):
  • Teams server: https://app.hoppier.com/api/mcp/business/v1
  • Gift cards server: https://app.hoppier.com/api/mcp/v1
Opening either URL in a browser shows an authorization error. That’s expected: the URL only works inside an AI assistant’s connector settings.

​
Claude

These steps work in Claude on the web and in the desktop app.
1

Add the connector

Open Settings → Connectors and choose Add custom connector. Enter Hoppier as the name and paste the server URL.
2

Choose how it signs in

If Claude asks how the connector signs in, choose Sign in now, and for the OAuth client choose Register automatically. These can’t be changed later: if you picked something else, remove the connector and add it again.
3

Sign in and approve

Click Connect. Claude opens Hoppier’s sign-in page. Sign in, read what Claude is asking to do, and approve it.
4

Try it

Start a new chat, turn on the Hoppier connector from the tools menu, and ask: “List my Hoppier programs.”
On Claude Team and Enterprise plans, an Owner adds the connector in Organization settings → Connectors. Each member then connects it and signs in to Hoppier themselves.

​
ChatGPT

  1. Open Settings → Connectors and add a custom connector. This needs a ChatGPT plan that supports custom connectors.
  2. Paste the server URL.
  3. Approve the connection and sign in to Hoppier.
  4. In a new chat, turn on the connector from the tools menu and ask: “List my Hoppier programs.”

​
What signing in looks like

You sign in on Hoppier’s own page, so the assistant never sees your password.
  • Teams server: sign in to the Hoppier dashboard. If you’re an admin of more than one company, pick the one to connect; a connection works with one company only. Click Send code, enter the 6-digit code we email you, and approve.
  • Gift cards server: sign in with Google or an emailed code, then approve.
The first time you connect an app, Hoppier emails you to say that a new app was connected to your account.

​
Other MCP clients

Any client that supports remote MCP servers with OAuth can connect with the same URLs.
  • Transport: Streamable HTTP, stateless, with JSON responses. There’s no SSE endpoint.
  • Sign-in: OAuth 2.1 authorization code flow with PKCE (S256 only). An unauthenticated request gets a 401 whose WWW-Authenticate header points to the protected-resource metadata:
    • Teams: https://app.hoppier.com/.well-known/oauth-protected-resource/api/mcp/business/v1
    • Gift cards: https://app.hoppier.com/.well-known/oauth-protected-resource/api/mcp/v1
  • Client registration: dynamic client registration (RFC 7591) at the registration_endpoint in the authorization server’s metadata, so there’s no client id to ask us for. client_name must be printable, at most 120 characters, and must not contain “Hoppier”. Redirect URIs must use https, or http on a loopback address. Client ID metadata documents aren’t supported.
  • Scopes: Teams: business:read, business:programs:write, business:participants:write, business:funds:send. Gift cards: gift_cards:read, gift_cards:send, profile. Leave scope out to ask for all of them.
  • Tokens: send Authorization: Bearer <token>. Access tokens last 1 hour. Refresh tokens last 30 days and change on every use; reusing an old one revokes the connection. A token for one server doesn’t work on the other.
  • Limits: each connection has an hourly request limit, and every MCP request counts, listing tools included. Over the limit you get HTTP 429 with Retry-After.