Quickstart
From zero to your first authenticated request in five minutes.
This guide gets you a token and a working request against
https://api.gummble.com. Skip ahead to MCP setup if you'd
rather wire Gummble into Claude/Cursor/Windsurf.
1. Sign in
Sign in at gummble.com with Google. Your account is provisioned automatically on first sign-in.
2. Get an access token
The simplest path is to copy the token your browser session already holds:
// In the browser devtools while signed in on gummble.com
localStorage.getItem('gummble_access_token')For programmatic access, see Authentication — you can either keep using the browser-issued JWT, or register an OAuth 2.1 client and run the full PKCE dance.
3. Make your first request
curl https://api.gummble.com/api/v1/apps?limit=3 \
-H "Authorization: Bearer $TOKEN"You should see a paginated JSON response like:
{
"data": [
{ "id": "app_…", "name": "Linear", "slug": "linear", … },
…
],
"pagination": { "cursor": "…", "hasMore": true }
}4. Pick your next step
Browse the API
Apps, screens, flows, search.
Set up MCP
Use Gummble from Claude, Cursor, or Windsurf.
Authentication
OAuth 2.1, refresh tokens, scopes.
Troubleshooting
If you get 401 Unauthorized, your token has likely expired. JWTs are
valid for 1 day. See Authentication for
how to refresh.
Rate limits are per-IP for unauthenticated traffic and per-user for authenticated traffic. See Rate limits.