MCP OAuth
Get OAuth Server Metadata
OAuth 2.0 authorization server metadata (RFC 8414), which OAuth-capable MCP clients read to find where to register, where to send the user, and where to exchange codes. The authorization_endpoint is the GTM Scoop web app's consent page; the token and registration endpoints are on the API host, under /api/v1/longlat/oauth, which serves the same handlers as /api/v1/gtmscoop/oauth.
In this section
Authentication
No credentials
This route is what issues tokens for everything else, so it takes no auth header.
Parameters
This endpoint takes no parameters or request body.
Mounted at
/api/v1/gtmscoop/oauth
OAuth for MCP clients: exchange an API key for a short-lived access token, or let an OAuth-capable client (Claude, ChatGPT, Cursor, an app on the user's computer) register itself and connect on a user's behalf with authorization code + PKCE. Access tokens are Bearer tokens accepted wherever an API key is, and their calls count toward the account's daily MCP limit.
Try it in the playground
Signed out: 10 free tries a day with names hidden. Log in for live data.
Open playgroundRelated endpoints