Last Bite
Requires Claude Desktop · BYOC bridge until Swiggy whitelists us

Paste your Swiggy MCP token

Be honest about the friction: Last Bite can't run Swiggy's OTP login itself yet because Swiggy hasn't whitelisted our OAuth callback. The bridge is BYOC — you authorize Swiggy inside Claude Desktop once, then paste the bearer token here. We encrypt it at rest and use it only for orders you confirm in the chat. Setup walk-through is below — budget 10–15 minutes if you've never edited a JSON config file.

How do I get the token from Claude Desktop?
  1. 1Install Claude Desktop if you haven't already.
  2. 2Open the config file:~/Library/Application Support/Claude/claude_desktop_config.json(Windows: %APPDATA%\Claude\claude_desktop_config.json)
  3. 3Add the Swiggy Food MCP server and restart Claude Desktop:
    {
  "mcpServers": {
    "swiggy-food": { "url": "https://mcp.swiggy.com/food" }
  }
}
  4. 4Claude Desktop pops up Swiggy's OTP login. Sign in — Claude finishes the OAuth and stores the token locally.
  5. 5Type /mcp in any Claude Desktop chat. You'll see swiggy-food as connected.
  6. 6Open ~/Library/Application Support/Claude, find the OAuth blob, copy the access_tokenvalue (a long eyJ…string), and paste it above.

Tokens last ~24 hours. If Last Bite says "your token expired," pop back into Claude Desktop, run any tool, copy the fresh access_token, and re-paste here.

  • Your token, your accountEach token is scoped to one Swiggy account. Your password and OTP go to Swiggy via Claude Desktop's OAuth — we never receive them.
  • Encrypted at restStored encrypted (AES-256-GCM) with a 30-day TTL. Redacted from every log.
  • Wipe anytimeEmail privacy@lastbite.fun and we'll delete your token + history within 24h. Or just disconnect Swiggy MCP in Claude Desktop — the token rotates.

By continuing, you agree to our privacy policy.