Teamso

com.teamsoPublished by teamso.comOfficial publisherv1.3.1Updated Nov 4, 2026

Teamso HR in your assistant: leave, approvals, people and payslips, with your own permissions.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Teamso HR server that lets an assistant handle leave, approvals, people records and payslips under the user's own permissions.

What you can do
  • The manifest lists no individual tools, so capabilities come from the registry description only.
  • It presents Teamso HR data and actions inside the assistant: leave, approvals, people and payslips.
  • Actions run with the connecting user's own permissions, so access mirrors what that person may already see or do in Teamso.
When to use it
Useful when an HR team or employee already works in Teamso and wants to check or act on leave, approvals, people records or payslips without leaving the assistant.
Requirements
A remote endpoint at mcp.teamso.com over streamable HTTP; no packages or environment variables are declared. OAuth authentication is required, so a Teamso account with the relevant permissions is needed.
Before you install
The server handles HR data such as people records and payslips, which is sensitive personal and payroll information. Approvals and leave actions may change records, so review anything the assistant proposes before confirming. Access is limited to the connecting user's own permissions.

Installation

In SourceWeft

  1. Open Teamso in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.teamso%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "teamso": {
      "type": "http",
      "url": "https://mcp.teamso.com/v1"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.1LatestNov 4, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.