What this module does
MCP (Model Context Protocol) is an open standard that lets AI assistants call tools in other systems. With the Teamso MCP server you can tell your assistant (Claude Desktop, Claude Code, Cursor, Windsurf or any other MCP client) in plain language "I'd like annual leave from next Monday to Wednesday", see the requests waiting for your approval, manage your goals, open your payslip and search the Teamso how-to guides.
The assistant connects to Teamso with your personal access token and works with your permissions: it cannot do anything you cannot do on screen. No AI model runs on Teamso's side; the assistant you use decides which tool to call and when.
Roles and permissions
Who | Permission | What they can do |
Every user (Admin, Manager, Employee) | No extra permission | Creates and revokes their own tokens on the MCP access screen; through the assistant handles their own leave, goals, payslips and announcements, and searches the guides. |
Manager | The approval permissions they have on screen | Also approves, through the assistant, the leave requests and team goals that are at their approval step. |
Admin | The management permissions they have on screen | Searches the employees they can see on screen and does what their permissions allow. |
The assistant never adds roles or permissions. Who can do what always follows the permission setup in Teamso: Responsibility management.
Before you start
You must be able to sign in to Teamso.
An assistant with MCP support must be installed (Claude Desktop, Claude Code, Cursor, Windsurf or another client).
For Claude Desktop, Node.js 20 or later must be installed on your computer.
To create leave requests, your mobile number must be in your profile and your company must have enough Digital Credits.
First-time setup
The MCP access screen walks you through setup in three steps: Access tokens, Connect your assistant and Try it.
Open MCP connection at the bottom of the left menu, just above Help center (the MCP access screen), and create a token in the Access tokens card (Creating and revoking an access token).
Pick your client in the Connect your assistant card; the setup is filled in with your token. Copy it and add it to your assistant:
Claude Desktop: Connecting Claude Desktop
Claude Code, Cursor, Windsurf and others: Connecting Claude Code, Cursor and Windsurf
Restart your assistant and ask something like "How many leave days do I have left in Teamso?". When the assistant sends its first request, the Try it section changes to Connected; click an example prompt there to copy it (Example uses).
Everyday flows
Role | Common task | Article |
Employee | Asking for the leave balance, creating a leave request (with the SMS code), opening their own payslip, entering goals and sending them for approval | |
Manager | Going through the leave requests waiting for their approval one by one, approving team goals | |
Everyone | Asking "how do I ...?" against the Teamso guides |
Tools that create or change records are marked as "write" tools in Teamso; assistants usually ask for your confirmation before calling them, and the Teamso ready-made prompts require your confirmation at every write step. Creating and cancelling a leave request is verified with the SMS code sent to your phone, just like in the web app.
Statuses and what they mean
Token statuses on the MCP access screen:
Status | On screen | Meaning |
Active | A row without a label in the Access tokens list (a newly created one has a New label) | The token can be used; the assistant connects with it. |
Expired | In the Expired and revoked section | The validity you chose has ended; requests with the token are rejected. Click Renew to create a new one with the same name. |
Revoked | In the Expired and revoked section | You revoked the token; requests with it are rejected immediately. |
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.
Notifications
MCP has no notifications of its own. Actions taken through the assistant produce the same notifications as on screen: for example, a leave request you create with the assistant reaches your approver through the usual channels (Approval process). Changes made with a token are recorded in the audit log with MCP as the source.
Mobile differences
The MCP access screen is in the web app; it also opens in your phone's browser. On a narrow screen the cards stack, and after you create a token the Go to the connection setup link in the box takes you to the setup steps. The MCP connection does not depend on the mobile app; you set it up on whichever device runs your assistant.
Common mistakes and FAQ
The assistant says I lack permission. The token works with your permissions. What you cannot do on screen the assistant cannot do either, and some sensitive operations (passwords, security settings, integration keys and the like) are never available with a token (Security and permissions).
I lost my token. A token is shown only once, when it is created, in the box in the Access tokens card. Revoke the old one and create a new one.
Does Teamso run AI on my behalf? No. Your own assistant understands the question and decides which tool to call. Teamso only performs the call the assistant makes, with your permissions.
Does it use Digital Credits? Only operations that need SMS confirmation (creating and cancelling a leave request) use credits, as in the web app. Read and help tools use none (Digital Credits).
For other problems: Troubleshooting.