Troubleshooting

If something's not working, this page covers the most common causes.

"Bearer token required" / 401

Your AI client doesn't have a token yet — the OAuth flow either didn't complete or the token expired. Reconnect from your client's MCP/connectors settings; you'll be sent back to the Picnic consent page.

"Token is invalid or expired"

Same fix as above. Tokens expire periodically; reconnecting refreshes them. If it keeps happening, the passkey behind the token may have been removed from your Picnic account — sign in to the Picnic app and check your passkey list.

"Missing required scope: read:balances" (or similar)

Your AI tried to use a tool whose scope you didn't grant. Disconnect the connector, reconnect, and approve the missing scope on the consent screen.

"Session not found"

The MCP session was lost — usually because the server restarted, or your client cached an old session ID. Restarting the AI client (or simply asking another question, which forces re-initialization) resolves this.

Passkey prompt doesn't appear

This is a browser / passkey-availability issue, not a Picnic one:

• Make sure you're on a device where your Picnic passkey is available (synced via iCloud Keychain, Google Password Manager, etc.).
• Try a different browser. Some browsers' passkey integration is more reliable than others.
• If you've never set up a passkey on this device, sign in to the Picnic app there first.

Still stuck?

Reach out to Picnic support from the app, with:

• which AI client you're using;
• the approximate time the error happened;
• the exact error message text.

That's enough for us to find the request in our logs.