This article explains how to create a personal access token for your assistant on the MCP access screen, how to choose its validity and how to revoke it. Every user does this for their own account; no extra permission is needed.
A token is a secret key that starts with tms_pat_. The assistant connects to Teamso with this key on your behalf and with your permissions. Keep it like a password and never share it.
Before you start
You must be signed in to Teamso with your own account. Tokens cannot be viewed or created during a support session opened by the Teamso support team (Support access).
Decide which assistant will use the token; a separate token per assistant or computer is recommended.
Step by step
Click MCP connection at the bottom of the left menu, just above Help center. The page that opens is MCP access.
The MCP access screen opens. It shows the three setup steps at a glance: Access tokens (1) on the left with Security and limits below it, Connect your assistant (2) in the middle, and Try it (3) on the right with the What the assistant can do card below it, which lists the tool groups the assistant can use. Long content scrolls inside its own card. In narrower windows, Try it, Capabilities and Security are shown as tabs. If you have no tokens yet, the Access tokens card reads Create your first token.
Open the token form. For your first token the form is already open in the card. If you have created tokens before, click New token at the top right of the card; the form opens inside the same card.
In Name, say where the token will be used, for example Claude Desktop, laptop. The name is required and lets you tell tokens apart in the list.
Pick the duration in Validity: 30 days, 90 days (default), 1 year, Custom… or Never (until revoked). With Custom…, type a number of days from 1 to 365 in the field that appears next to it. A shorter validity is safer; when it ends you need a new token.
Click Create token. To back out, close the form with Cancel.
A yellow box at the top of the card shows your token under the heading "Claude Desktop, laptop" created. Click Copy and keep it somewhere safe. The token is shown only in this box, once. If you try to leave the page without copying it, Teamso asks You haven't copied the token; click Stay on page to go back.
The token is filled in automatically in the ready-made setup of the Connect your assistant card (the box says Added to the connection setup; the setup shows a Token added label). Pick your client: Claude Desktop, Claude Code, Cursor, Windsurf or Other (
mcp-remote). The card shows numbered setup steps for the client you pick. The token is shortened in the setup (the eye icon shows it in full); what you copy contains the full token. Copy the setup or command with Copy at the top right of its block and add it to your assistant (Connecting Claude Desktop, Connecting Claude Code, Cursor and Windsurf).
Once you have saved the token, close the box with I've saved it, hide. The token appears at the top of the list with a New label; the list shows only its first characters (for example
tms_pat_Xk4fQ2…). When the box closes or you leave the page, the ready-made setup goes back to thetms_pat_...placeholder.
After you connect and restart your assistant, the Try it section reads Waiting for the first request. As soon as the assistant sends its first request with the token, the section changes to Connected by itself; click Check now if you don't want to wait. Click one of the example prompts in that section to copy it, then paste it into your assistant.
Revoking a token
On the MCP access screen, click the revoke icon (Revoke) at the right of the token's row.
Confirm with Revoke in the Revoke token window.
Assistants using a revoked token lose access immediately; every request with it is rejected. Revoking cannot be undone; create a new token to connect again.
Result
The heading of the Access tokens card shows how many active tokens you have (for example 2 / 10 active).
Each active token row shows its name, its first characters, Last used (when the assistant last used the token, or Not used yet) and its end date (Expires … or Never). When 7 days or fewer are left, the row shows … days left instead.
Expired and revoked tokens are grouped in the Expired and revoked section below the list; click its heading to open it. These rows show an Expired or Revoked label next to the name. Renew on an expired token's row opens the form with the same name, so you can create a new token and update the setup in your assistant. Validity cannot be extended.
The status pill at the top right of the screen shows Connected · last request … if any of your tokens has been used, or Not connected yet if none has.
A user can have at most 10 active tokens at a time. At the limit New token is disabled and the card shows You've reached the active token limit; the tokens unused for longest move to the top of the list.
Common problems
Symptom: The Access tokens card shows Your own session only and 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: New token is disabled and the card says You've reached the active token limit.
Cause: You reached the limit of 10 active tokens.
Solution: Revoke the tokens you do not use and try again.
Symptom: I closed the box or left the page without copying the token.
Cause: For security the token is shown only once; Teamso keeps only a hash of it.
Solution: Revoke this token and create a new one.
Symptom: The Try it section says "No request yet".
Cause: The assistant has not read the setup yet, or the token was pasted incorrectly.
Solution: Fully quit and reopen the assistant, then click Check now. If it still fails, see Troubleshooting.
Symptom: After working for a while, the assistant started returning "401" errors.
Cause: The token expired or was revoked.
Solution: Create a new token and update the setting in your assistant (Troubleshooting).