AI assistant can't connect to Tuppence
The MCP server is for API keys
Likely cause: The assistant is trying to use your dashboard sign-in, not a key.
Create a key under Developers, then API keys, and give the assistant that. See Connect Claude or ChatGPT.
Still stuck? Chat with us in your dashboard — the assistant can bring in our team. Can't sign in? Contact us.
The assistant is refused, or says it isn't signed in
Likely cause: The key was typed wrong, still says YOUR_KEY, or has been revoked.
Check the key in the assistant’s settings. On API keys, check it isn’t under revoked or expired keys. If you’ve lost it, make a new one. Keys are only shown once.
Still stuck? Chat with us in your dashboard — the assistant can bring in our team. Can't sign in? Contact us.
The assistant says it can't refund, or can't see bookings
Likely cause: The key is restricted and doesn't allow that.
Make a new restricted key that includes it (for example, Refunds) and give the assistant the new key. Only add what it needs.
Still stuck? Chat with us in your dashboard — the assistant can bring in our team. Can't sign in? Contact us.
It only sees test data
Likely cause: The key was made in test mode. A key only works in the mode it was made in.
Switch the dashboard to live mode, make a live key, and give the assistant that.
Still stuck? Chat with us in your dashboard — the assistant can bring in our team. Can't sign in? Contact us.
It's refused from one computer but works from another
Likely cause: The key only works from the addresses listed for it.
On API keys, open the key and choose Edit beside IP addresses. Change where it can be used from, or remove the list.
Still stuck? Chat with us in your dashboard — the assistant can bring in our team. Can't sign in? Contact us.