Skip to main content
Help Center

Connect teamspace to Claude

Enter the MCP access as a connector in Claude and authorise it via OAuth – the process that looks the same at heart with every client.

Prerequisites

  • The address of an MCP access from your administrator (see Create an MCP configuration)
  • A teamspace account that is released for this access
  • A Claude account (desktop app or web)

You connect teamspace to Claude through a connector: enter the address, authorise via OAuth, done. Claude then works in teamspace with your permissions. The desktop app and the web behave identically, and the same procedure carries any other client – only the menus are named differently:

The principle is the same everywhere. Every client has a field where an MCP address belongs, and after that OAuth takes over. All that differs is the route to that field and what it is called – “Connectors”, “Konnektoren”, “MCP Server”. Once you have seen this flow, you’ll recognise it everywhere. Which clients are tested is listed in Supported clients.

Step 1: Open the connectors

Claude → Settings → Connectors

The overview shows popular connectors at the top and, below them, the ones already set up with their status.

Claude settings with the Connectors area: at the top the popular connectors Gmail, Google Drive and Slack, below a table with the already configured connector and the Add button at the top right
The connectors overview in the Claude settings

Step 2: Create the connector

  1. Click Add at the top right and choose Add custom connector.

  2. Enter a name by which you’ll recognise the access – e.g. projectfacts or teamspace.

  3. In the Remote MCP Server URL field, enter the address you received from your administrator:

    https://<your-tenant>/mcp/<identifier>

  4. Leave Advanced settings be. The OAuth Client ID and OAuth Client Secret fields stay empty – teamspace registers the client automatically.

  5. Click Add.

The Add custom connector dialog with the name projectfacts in the first field; the Remote MCP Server URL field is still empty, with the expanded advanced settings and the empty OAuth fields below
1 Name entered, address still empty
The same dialog with the MCP server address entered in the Remote MCP Server URL field; the OAuth Client ID and OAuth Client Secret fields stay empty, with the Add button at the bottom right
2 Address entered, OAuth fields stay empty

Step 3: Authorise the access

Claude now takes you to teamspace’s consent screen: Connect with Claude. This is the most important moment of the whole setup – here you decide what the assistant may do.

Consent screen Connect with Claude: yellow notice about the dynamically registered client, the application identity, the three permissions Read MCP server, Call tools and Write data, the redirect URI, the MCP configuration Employee and the Allow and Deny buttons
The OAuth consent screen with the three permissions, the redirect URI and the MCP configuration

Take a moment for it and check from top to bottom:

  1. Application identity – Claude appears as a dynamically registered client: it signed up automatically. That is why the yellow notice prompts you to check the permissions and the redirect.
  2. The three permissions – Read MCP server, Call tools and Write data. What each of them means is covered in Security and permissions with MCP.
  3. The redirect URI – the actual check. For Claude it must read https://claude.ai/api/mcp/auth_callback. If the domain doesn’t match the service you are about to connect, cancel.
  4. MCP configuration – the name of the access you are authorising, e.g. “Employee”. This shows you which set of tools you are releasing.
  5. Tick I know and trust this URL and click Allow.

After that you land back in Claude, the connector shows as connected – and you can get going.

Step 4: Try it out

Ask a question that can only be answered from teamspace. Good ones to start with:

  • “Who am I in teamspace?” – the quickest check of whether the connection really stands.
  • “What’s in my agenda today?”
  • “Show me all untouched bug tickets, grouped by status.”

If Claude answers with real data from your tenant, everything is set up correctly.

Common questions & needs

You want to …How to
Check that the connection standsAsk “Who am I in teamspace?”. If your name comes back, it’s working.
Use several accesses at onceSet up each as its own connector – one access per address.
Withdraw access againRemove the connector in Claude. In addition, your administrator can revoke the authorisation on the server side.
Use the same access on a second deviceRepeat the process there – the OAuth consent applies per client.
Know everything the assistant can doAvailable MCP tools – or just ask it yourself.
Use a different clientSupported clients – the process is the same, only the menus have different names.

When it doesn’t work

SymptomCause and remedy
The consent screen doesn’t appear at allCheck the address – usually a typo or a missing character in the identifier.
”Not authorised” after allowingYour account is not released for this access. The administrator enters you under “Authorised group or person”.
The connector connects but finds no toolsThe access has no active tools yet – or the Active flag is missing. The administrator sorts out both.
Claude can’t find data that should existVia MCP, your normal permissions apply. What you may not see in teamspace, you won’t see here either.
The redirect URI looks wrongDon’t confirm. Have the address and its origin checked by the administrator.