This article explains what to do when your assistant cannot connect to Teamso or cannot complete an action. The assistant usually passes on Teamso's error with an explanation; the end of the error text holds the HTTP status and the Teamso error code (for example OTP_NOT_DONE).
Before you start
Check your token's status on the MCP access screen: active tokens are in the Access tokens list; expired and revoked ones are in the Expired and revoked section with an Expired or Revoked label. Last used on the row shows when the assistant last used the token.
Note the code in the error message.
Step by step: errors and fixes
Symptom: 401 Unauthorized; the assistant cannot connect to Teamso at all, or the connection dropped while working.
Cause: The token is mistyped, expired or revoked, or the user was deactivated or moved to another company.
Solution:
Check the token's status on the MCP access screen. If the token is in the Expired and revoked section, create a new token; on an expired token, Renew opens the form with the same name (Creating an access token).
Check that the header reads exactly
Authorization: Bearer tms_pat_...with no spaces before or after the token. In Claude Desktop the token must be the value ofTEAMSO_ACCESS_TOKEN.Restart the client after updating the setting.
Symptom: 403 ACCESS_DENIED.
Cause: You lack the permission in Teamso, or the operation is never available with a token (passwords, security settings, token and integration key management, SSI credentials, support access, webhook changes and the like).
Solution: Check whether you can do the same on screen. If you cannot, ask your administrator for the permission (Responsibility management). Do the operations blocked for tokens on the Teamso screen, in your own session (Security and permissions).
Symptom: 403 IP_NOT_ALLOWED.
Cause: Your company's IP restriction rejected the request.
Solution: Ask your administrator to add your IP address to the allowlist. With the local package in Claude Desktop, your computer's IP address must be allowed (Security and access settings).
Symptom: 429 Too Many Requests.
Cause: The hosted server limits requests per token per minute; too many requests were sent in a short time.
Solution: Wait for the Retry-After time (in seconds) given in the response, then retry. Ask the assistant not to repeat the same task in a loop.
Symptom: OTP_NOT_DONE; the assistant says the SMS code was not verified.
Cause: The code was mistyped or its 3 minutes ran out.
Solution: Ask the assistant to send a new code and type it within 3 minutes. If no code arrives, check the mobile number in your profile.
Symptom: CREDIT_INSUFFICIENT.
Cause: Creating and cancelling a leave request is verified by SMS and uses Digital Credits; the company balance is too low.
Solution: Ask your company administrator to top up Digital Credits (Digital Credits).
Symptom: The Teamso tools do not show up in the assistant.
Cause: The client has not picked up the new setting; in Claude Desktop, Node.js is missing or too old, or the configuration file is broken.
Solution:
Fully quit and reopen the client. In Claude Desktop closing the window is not enough; use Quit in the menu on macOS (
Cmd+Q) or Quit on the system tray icon on Windows.In Claude Desktop, check that Node.js 20 or later is installed (
node -v) and that the package version is pinned (like@teamso/[email protected]).Copy the setting again from the MCP access screen (Connecting Claude Desktop).
In Claude Code, check the entry with
claude mcp get teamso(Connecting Claude Code, Cursor and Windsurf).
Symptom: The MCP access screen shows Your own session only: "Access tokens can only be managed in the user's own session"; no token can be created.
Cause: You are in a support session opened by the Teamso support team.
Solution: Only the user can manage tokens, in their own session; sign in with your own account.
Symptom: The assistant calls the right tools but the result is empty.
Cause: You are not allowed to see that data, or there is no record (for example no request is at your approval step).
Solution: Check the same list on screen. If you do not see it there, the assistant cannot see it either.
Result
If the problem persists, send the Teamso support team the code in the error message, the time and the client you use (Claude Desktop, Claude Code, Cursor, Windsurf, ...). Do not share your token, not even with the support team.
Common problems
Symptom: I created a new token but the assistant still returns 401.
Cause: The client keeps using the old token.
Solution: Replace the token in the setting and fully restart the client.