This article explains how to connect Claude Code, Cursor, Windsurf and other MCP clients to Teamso. The person who will use the assistant does this on their own computer.

These clients connect to Teamso's hosted MCP server without installing anything: the address is https://mcp.teamso.com/v1 and authentication is the Authorization: Bearer <token> header. The server does not store your token; it forwards each request to Teamso on your behalf.

Before you start

You need an MCP access token (Creating an access token).
The client you will use must be installed.

Claude Code, Cursor and VS Code can also connect without a token, by signing in to Teamso in the browser: Connecting with a browser sign-in. This article describes the token setup.

Step by step

In Teamso, create a new token on the MCP access screen. In the Connect your assistant card, pick your client: Claude Code, Cursor, Windsurf or Other. The card shows the Server address and the Header, followed by numbered steps for the client you picked. Copy the command or setup with Copy at the top right of its block; your new token is already in it (Token added). If you created the token earlier, the setup shows a placeholder: replace the highlighted tms_pat_... with your token.
Continue for your client.

Claude Code

In a terminal, run the command you copied for Claude Code:

claude mcp add --transport http teamso https://mcp.teamso.com/v1 --header "Authorization: Bearer tms_pat_..."

To check the connection, run claude mcp get teamso or type /mcp inside Claude Code. The teamso server's status should be connected.

Cursor

In Cursor, open the command palette with Cmd+Shift+P (Ctrl+Shift+P on Windows) and run Open MCP settings.

Add the server to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "teamso": {
      "url": "https://mcp.teamso.com/v1",
      "headers": {
        "Authorization": "Bearer tms_pat_..."
      }
    }
  }
}

Restart Cursor; the Teamso tools appear in the MCP list.

Windsurf

In Windsurf, open Settings > MCP (file: ~/.codeium/windsurf/mcp_config.json).

Add the server. Windsurf expects the address in serverUrl instead of url:

{
  "mcpServers": {
    "teamso": {
      "serverUrl": "https://mcp.teamso.com/v1",
      "headers": {
        "Authorization": "Bearer tms_pat_..."
      }
    }
  }
}

Restart Windsurf.

Other clients

Any client with Streamable HTTP connects to https://mcp.teamso.com/v1 with the Authorization: Bearer tms_pat_... header.
Clients that only speak stdio reach the hosted server through mcp-remote. The ready-made setup appears on the MCP access screen when you pick Other in the Connect your assistant card:

The Teamso MCP Server setup guide shows the settings of all clients in one place:

Result

The client uses the Teamso tools with your permissions. Try it by asking "How many leave days do I have left in Teamso?". Requests go through the hosted server, which forwards your real IP address to Teamso in signed form, so your company's IP restriction applies to you. The hosted server limits the number of requests per token per minute.

Common problems

Symptom: The client says "401 Unauthorized".
Cause: The header is mistyped, or the token is wrong, expired or revoked.
Solution: Check that the header reads exactly Authorization: Bearer tms_pat_... (one space between Bearer and the token). Create a new token if needed.

Symptom: Windsurf cannot connect.
Cause: The address is in url.
Solution: In Windsurf, put the address in serverUrl.

Symptom: The tools do not show up.
Cause: The client has not picked up the new setting without a restart.
Solution: Fully quit and reopen the client; in Claude Code check the entry with claude mcp get teamso.

For other errors: Troubleshooting.

Connecting Claude Code, Cursor, Windsurf and other clients to Teamso