When Something Goes Wrong

The Client Says Unauthorized

The request reached this server and carried nothing it would accept. What to do depends on how that client was set up, and the two paths fail for different reasons.

A client you signed in to, such as Claude Desktop, has lost the access you approved, or never came away with it. Open the Access Tokens page and look under Connected Apps. That list shows the apps signed in to the account you are signed in as right now, and only while their access is live.

If the app is not listed, one of four things happened: the approval never completed, somebody revoked it, the grant expired without the client renewing it, or you approved it from a different account of your own and are signed in to the other one here. The remedy is the same for all four. Sign in as the account you want the app to act as, connect it again, and choose Allow Access. If it is listed and still fails, the credential is not the problem, so read the next two sections.

A client holding a token, such as Claude Code, has a token that is revoked, truncated, or sent wrongly. The header value is the word Bearer, one space, then the token, and a token pasted on its own fails exactly like a token that was never valid. Mint a fresh one, copy it with the copy button rather than by hand, and set it again.

If both look right and it still fails, your own account here may have been disabled, which stops every client at once regardless of how it connected.

The Client Cannot Reach the Server

Connection refused, a timeout, or an error naming the address rather than your credentials. The address is not one that client can get to.

A localhost address only works for something running on the same machine. Claude Code qualifies. Claude Desktop does not use one even then, because it requires HTTPS, and ChatGPT is not on your machine at all. If the endpoint you were given starts with http://, it is a development address, and whoever set this up needs to serve the application over HTTPS on a name that resolves from outside. The endpoint printed on your connection page is always the current answer: if it disagrees with what you pasted, paste the new one.

The Connection Says Credentials Rejected

This one is not about your client. Follow Up Boss refused the API key this connection holds, which happens when the key has been deleted or regenerated over there. The status appears the next time an assistant asks for something, because that is the moment the refusal happens.

Get a fresh key, then edit the connection and paste it in. Edit it rather than deleting it and starting over: deleting a connection takes its whole record of tool calls with it, and your clients keep working through the edited one without being touched.

The Assistant Says It Has No Tools

The server is connected and the assistant still answers as though your CRM is not there. A client asks for the list of tools when it connects and then remembers the answer, so one that was running while you finished the setup is working from a list taken before you existed to it.

Restart the client. In Claude Code, claude mcp list tells you whether the server is connected at all, which separates a stale list from a connection that never worked. Asking "who am I connected to?" is the quickest proof once it has reloaded: the answer names the Follow Up Boss account, which only a working tool call can do.

The Client Says Too Many Requests

An error naming 429 or "Too many requests", usually with the words "Wait 1 minute and try again". This server counts how many requests each account makes in a minute and refuses the ones past the ceiling. The refusal is temporary and nothing is broken: the count is forgotten a minute later, and the assistant works again without anybody touching a token or a connection.

You will not reach that ceiling by asking questions. It takes hundreds of calls a minute, which in practice means an assistant that has been set loose on a list and is working through it one record at a time. Wait a minute, then ask for less in one go: a narrower search, or a smaller batch. If it happens while you are doing nothing unusual, say so, because a limit that fires during ordinary work is a limit set wrongly rather than a client behaving badly.

Still Stuck

Write to axel@axelrivera.dev and say which client you are using and what you saw on screen. Never send a token or an API key, and you will not be asked for one.