---
title: "Connecting Claude and other AI assistants to Talkspirit"
description: "Connect Claude, ChatGPT, Gemini CLI or Microsoft Copilot Studio to your Talkspirit organisation. Enter the server address and the client ID mcp-claude-desktop, sign in with your Talkspirit account, and the assistant acts with your own permissions."
category: integrations
section: api-and-webhooks
type: Tutorial
lastUpdated: 2026-11-13
locale: en
canonical: https://support.talkspirit.com/en/integrations/connect-claude-and-other-ai-assistants
---

# Connecting Claude and other AI assistants to Talkspirit


Talkspirit runs a **Model Context Protocol (MCP) server**, so an AI assistant can read your organisation's data and act on it for you. You can connect Claude, Claude Code, ChatGPT, Gemini CLI and Microsoft Copilot Studio. Each one needs the same three values, and the assistant acts with your own permissions only.

## Values to enter in every tool

```
Server address:   https://mcp.talkspirit.com/mcp
OAuth client ID:  mcp-claude-desktop
Client secret:    leave empty
Sign-in:          your usual Talkspirit login, SSO included
```

Talkspirit's sign-in server does not let an AI tool register itself, so type the client ID by hand. `mcp-claude-desktop` is the client ID for every tool here, even though its name mentions Claude. Swiss customers: contact support for the server address of your region.

| AI tool | Who can connect | Method |
| --- | --- | --- |
| Claude (web, desktop, mobile) | Free (one connector), Pro, Max; Team and Enterprise via an owner | Sign in |
| Claude Code | Anyone | Sign in, or MCP key |
| ChatGPT (web) | Business, Enterprise, Edu; Pro for read-only | Sign in |
| Gemini CLI | Anyone | Sign in |
| Microsoft Copilot Studio | Agent makers | MCP key |
| Microsoft 365 Copilot, Gemini Enterprise | Not supported yet | None yet |

The Gemini app cannot connect: Google allows custom apps only on personal accounts in the US.

> **Note:** each vendor changes its screens independently of Talkspirit. Where a name has moved, look for the nearest equivalent.

### Working with several organisations

Requests run against your **active organisation**. If you belong to more than one, the assistant can list them and show which one is active before it changes anything. A client that sets request headers can address another organisation you belong to by sending its ID in an `X-Tenant-Id` header. An ID for an organisation you are not a member of is refused.

### Mentions in comments

An AI connected to Talkspirit can mention at most 5 people per comment and 20 people per hour. People who cannot see the item are not notified but still count. Past a limit, the comment is refused and the AI is told why; at the hourly limit, it is told to post without mentions. Mentions you write yourself in the app are not limited.

## Claude

### Claude on the web, desktop and mobile

1. Open **Customize → Connectors**. On Team and Enterprise plans, an owner of your Claude organisation opens **Organization settings → Connectors**, then selects **Add** and **Custom**.
2. Select **Add custom connector** (on Team and Enterprise plans, **Web** if Claude asks for the connector type), name it `Talkspirit` and enter the server address.
3. Set the OAuth client. In the two-step dialog, choose **Sign in now** or **Sign in when needed** under **Authentication**, then **Use your own OAuth client** under **OAuth client**. **No sign-in** hides the OAuth client setting. In the one-screen dialog, open **Advanced settings**. Enter `mcp-claude-desktop` as the client ID and leave the secret empty.
4. Select **Add**, then **Connect**, and sign in with your Talkspirit account.

On Team and Enterprise plans, each member then opens **Customize → Connectors**, finds the connector labelled **Custom** and selects **Connect**. A connector added on the web or desktop is also available on mobile.

![Claude's one-screen "Add custom connector" dialog with the Talkspirit server address, the client ID mcp-claude-desktop under Advanced settings and an empty secret](/images/integrations/connect-claude-and-other-ai-assistants/01-claude-add-custom-connector.png)

**Use Claude's published identity** and **Register automatically** end on a Talkspirit sign-in error. Claude cannot edit these settings afterwards: remove the connector and add it again.

### Claude Code

Pick any free port for `--callback-port`:

```bash
claude mcp add --transport http --client-id mcp-claude-desktop --callback-port 33418 \
  talkspirit https://mcp.talkspirit.com/mcp
claude mcp login talkspirit
```

`claude mcp login` opens your browser. Without `--client-id`, Claude Code stops with "Dynamic Client Registration rejected". For scripts and machines without a browser, use an MCP key (see **Any other MCP client**).

## ChatGPT

ChatGPT connects on the web only, and developer mode must be on for whoever creates the app. OpenAI offers custom MCP apps in beta; these steps follow its help pages. When a setup fails, check these three points first:

- **Plan:** custom MCP apps need ChatGPT Business, Enterprise or Edu. Pro connects read-only. OpenAI does not list Free and Plus.
- **Developer mode:** the path depends on the plan.
  - Business: only administrators and owners can use it, each for themselves, under **Settings → Apps → Advanced settings → Developer mode**.
  - Enterprise and Edu: an administrator grants it under **Permissions & Roles → Connected Data**, then each member switches it on under **Settings → Apps → Advanced Settings**.
  - Pro: you switch it on yourself.
- **Client ID field:** enter the client ID under **Advanced OAuth settings**. Talkspirit's sign-in server refuses automatic registration.

Then create the app:

1. Open **Settings → Apps** and select **Create**. Administrators use **Workspace settings → Apps → Create**. OpenAI is renaming Apps to **Plugins**.
2. Enter the name `Talkspirit` and the server address.
3. Choose OAuth as the authentication mechanism, open **Advanced OAuth settings** and select **User-Defined OAuth Client**.
4. Enter `mcp-claude-desktop` as **OAuth client ID**, leave **OAuth client secret** empty and set **Token endpoint auth method** to `none`.
5. Select **Scan Tools**, sign in with your Talkspirit account when asked, then select **Create**.
6. Administrators publish the draft under **Workspace settings → Apps → Drafts → Publish** so colleagues can use it.

ChatGPT keeps a copy of the tool list from when the app was approved. After Talkspirit adds tools, an administrator selects **Refresh** in the app's settings.

## Gemini, Copilot and other tools

### Gemini CLI

Add Talkspirit to `mcpServers` in your Gemini CLI `settings.json` (by default `~/.gemini/settings.json`):

```json
{
  "mcpServers": {
    "talkspirit": {
      "httpUrl": "https://mcp.talkspirit.com/mcp",
      "oauth": {
        "enabled": true,
        "clientId": "mcp-claude-desktop",
        "scopes": ["openid", "assistant:read", "assistant:write"]
      }
    }
  }
}
```

Then run `/mcp auth talkspirit` in Gemini CLI and sign in. The sign-in needs a browser on the same machine.

### Microsoft Copilot Studio

Copilot Studio connects with an MCP key. [Create the key](/en/integrations/create-and-manage-mcp-keys) first:

1. In your agent, open **Tools**, select **Add a tool**, **New tool**, then **Model Context Protocol**.
2. Enter a **Server name**, a **Server description** and the server address as **Server URL**.
3. Choose **API key** as the authentication type, set **Type** to **Header** and enter `X-API-Key` as the header name. Select **Create**.
4. On **Add tool**, select **Create a new connection**, paste an MCP key, then select **Add to agent**. Microsoft says the user of the agent provides the API key.

A Copilot Studio trial can build and test an agent but cannot publish it. Your organisation's Power Platform data policies can also block MCP servers.

> **Warning:** a connection acts as the owner of the key pasted into it, so everyone who shares that connection shares that owner's permissions. Use a key created for this purpose, and **Read only** when the agent does not need to write.

### Any other MCP client

Create an MCP key under **Account → MCP keys**, point the client at the server address and send the key in an `X-API-Key` header on every request. In Claude Code:

```bash
claude mcp add --transport http talkspirit https://mcp.talkspirit.com/mcp \
  --header "X-API-Key: tsk_<your_api_key>"
```

Treat an MCP key like a password: keep it in a secrets manager, never in version control, and use one key per tool so you can revoke them independently.

## Troubleshooting

Check that it worked by asking *"Using Talkspirit, who am I?"*. The assistant replies with your name and organisation.

| What you see | What it means | What to do |
| --- | --- | --- |
| The sign-in loops or is rejected, or you see "Dynamic Client Registration rejected", "Trusted Hosts" or "registration not allowed" | The client ID is missing, or the tool tried to register itself, which Talkspirit does not allow | Enter the client ID `mcp-claude-desktop` and leave the secret empty |
| "Invalid parameter: redirect_uri" on the Talkspirit sign-in page | This tool's return address is not authorised on Talkspirit's side | Contact support: the tool is not supported yet |
| ChatGPT does not show a new tool | ChatGPT keeps a frozen tool list | An administrator selects **Refresh** on the app |
| `401 Unauthorized` | The sign-in expired, or the key is mistyped, expired or deleted | Sign in again, or check the key is **Active** at **Account → MCP keys** |
| `403 Forbidden` | Your account is not allowed to do that, for example a guest account | The assistant only has your permissions. Check what your account can do in Talkspirit |
| It cannot reach the server, or times out | Network or firewall | Check that `mcp.talkspirit.com` is reachable |

## Next steps

- [What the Talkspirit MCP server can do](/en/integrations/what-the-mcp-server-can-do)
- [Create and manage MCP keys](/en/integrations/create-and-manage-mcp-keys)
- [The Talkspirit Partner API](/en/integrations/partner-api)
- [How Spark processes your organisation's data](/en/administration-security/how-ai-processes-your-data)
- [MCP connector privacy policy](/en/integrations/mcp-connector-privacy-policy)
