This article explains the easiest way to connect an AI assistant to Teamso: you add the Teamso MCP address to the assistant and sign in to Teamso in your browser. No token is copied. The person who will use the assistant does this on their own account.

The assistant opens a Teamso page in your browser. There you see which app wants to connect, what it can do and for how long it stays connected, and you click Allow. The app then works with your permissions, like the web app, and you can change or end the connection at any time under MCP connection > Connected apps.

Teamso consent screen opened by the assistant

Before you start

You must be able to sign in to Teamso.
The assistant must support remote MCP servers with sign-in (OAuth): ChatGPT, Claude (web and desktop), Claude Code, Cursor, VS Code and Grok do. In ChatGPT, adding your own MCP server depends on your plan.
The Teamso MCP address is https://mcp.teamso.com/v1. You can copy it from the MCP connection screen too.

Step by step

Add the Teamso address to your assistant (see your client below) and start the connection.
Your browser opens the Teamso page Connect {app} to Teamso (often in a small window). If you are not signed in, Teamso asks you to sign in first, with your password, the SMS or email code, or Google; after signing in you come back to the same page.
Check the app row: the app name and You will return to ... (for an app on your computer: An app on this computer (localhost)). Only continue if this is the app you just started from.
Under What it can do read what the app can see. If the app asked to make changes, Allow changes is on; turn it off if the app should only read.
Check Company and Signed in as. To connect another account, click Use another account: Teamso signs you out and brings you back to this page after the new sign-in.
Choose Stays connected at the bottom (7 days, 30 days, 90 days, 180 days, 1 year or Unlimited; 90 days is preselected) and click Allow. To give up, click Cancel.
Teamso shows {app} is connected with the company, the access (Read or Read and write) and how long it stays connected, then takes you back to the app (Taking you back to ...). If nothing happens, click Continue to ....

ChatGPT

Open chatgpt.com/plugins, click + and choose Add custom MCP server.
Name it Teamso, enter https://mcp.teamso.com/v1 as the address and add it.
ChatGPT opens the Teamso sign-in page. Continue from step 2 above.

Claude (claude.ai and Claude Desktop)

Open Customize > Connectors and choose Add custom connector.
Name it Teamso, enter https://mcp.teamso.com/v1 as the address and add it.
Click Connect on the Teamso connector; the Teamso sign-in page opens.

Claude Code

In a terminal run:

claude mcp add --transport http teamso https://mcp.teamso.com/v1

In Claude Code type /mcp, pick teamso and choose to authenticate. The browser opens the Teamso page.

Cursor

Add the server to ~/.cursor/mcp.json with the address only (no token header):

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

In Cursor's MCP settings the Teamso server asks you to sign in; click it and the Teamso page opens.

VS Code

Add the server to the mcp.json of your workspace (.vscode/mcp.json) or of your user profile:

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

Start the server (for example with Start above it in mcp.json) and allow the sign-in; the Teamso page opens.

Grok

Open grok.com/connectors, choose New Connector > Custom and enter https://mcp.teamso.com/v1.
When Grok asks you to sign in, the Teamso page opens.

Connected apps

Every app you allow is listed on the MCP connection screen under Connected apps.

Open MCP connection at the bottom of the left menu and choose Connected apps at the top.
Each row shows the app with its return address, the access (Read or Read and write), when it was connected, Last used and Stays connected until.
To change how long an app stays connected, pick a new period in its Stays connected until box. The new period counts from today.
To end a connection, click Disconnect on the row and confirm. The app loses access right away; to use it again, connect it again from the app.

If the list is empty you see No apps connected yet with the address to add to your assistant.

Result

The app works with your permissions. What you cannot see or do on screen it cannot see or do either (Security and permissions).
Without Allow changes the app can only read; tools that create or change records are refused.
When the period you chose ends, the app asks you to sign in again.
Personal access tokens keep working as before. Use a token when your client cannot sign in with a browser, for example Claude Desktop with the local package, Windsurf or mcp-remote (Creating an access token).

Common problems

Symptom: The page says This sign-in link is not valid, This sign-in link was already used or This sign-in link has expired.
Cause: The link was opened twice, opened too late, or copied incompletely.
Solution: Close the page and start the connection again from the app.

Symptom: Too many connections: "Too many connections in the last hour. Try again later."
Cause: Several connections were started from your account within an hour.
Solution: Wait a while and start again from the app.

Symptom: The app name or return address on the page is not the app you started from.
Cause: Someone else may have sent you the link.
Solution: Click Cancel. Only connect apps you trust: they act as you.

Symptom: The app connected but a write tool is refused.
Cause: Allow changes was off when you connected.
Solution: Disconnect the app under Connected apps and connect it again with Allow changes on.

For other errors: Troubleshooting.

Connecting ChatGPT, Claude, Cursor and VS Code to Teamso with a browser sign-in