Skip to main content
This guide is for developers building an app that calls Mobbin’s MCP server on behalf of their users. Each of your users authorizes with their own Mobbin account, and your app makes MCP requests using their access token. If you just want to connect an existing MCP client like ChatGPT or Claude, see Supported Clients.

​
Requirements

Your users need to be on a Mobbin Pro Plan, Team Plan, or Enterprise Plan. There is no separate fee for integrators.

​
Setup

Mobbin uses Dynamic Client Registration (RFC 7591), so no client_id provisioning or redirect URI whitelisting is needed on Mobbin’s side. Follow the steps below to connect your app:
  1. Fetch the protected resource metadata to discover the authorization server:
  2. Fetch the authorization server’s .well-known/oauth-authorization-server to get the full set of OAuth endpoints (authorization, token, registration, JWKS, etc.).
  3. Register your app via the DCR endpoint to obtain a client_id.
  4. Redirect the user to the authorization endpoint with PKCE (S256) and the openid scope.
  5. Exchange the authorization code for an access token and refresh token.
  6. Call the MCP server at https://api.mobbin.com/mcp with a Bearer token.
  7. Use the refresh token to obtain new access tokens as needed.
For the full protocol details, see the MCP authorization specification. We strongly recommend using an MCP SDK that handles the OAuth flow automatically. You typically just need to provide a redirect URI and a token storage hook.