# Connect Claude, ChatGPT and other AI assistants via MCP

> Connect AI assistants to qutee via MCP so they can read calls, transcripts, agents, campaigns and settings. With sign-in or an API key.

Source: https://docs.qutee.ai/en/integrationen/api-und-mcp/

With MCP (Model Context Protocol) you connect AI assistants such as Claude, ChatGPT or Claude Code to qutee. The assistant can then read and search your company's calls, summaries, transcripts, agents, campaigns and settings, and look things up in this help center. If you allow it, it can also edit calls, campaigns and agents.

## Before you start

- You are signed in as a **Company Admin**. Only admins can connect AI apps and create API keys.
- A connection acts with your permissions and only for your own company.
- Call data the assistant reads is processed by its AI provider. Only connect providers your company has approved.

## What a connected assistant may do

You choose the permissions when you connect. Reading is preselected, editing you have to allow explicitly.

| Permission | What the assistant can do with it |
| --- | --- |
| **Read calls** | Read and search calls and summaries. |
| **Read transcripts** | Read full call transcripts. |
| **Read agents** | Read phone agent configuration. |
| **Read campaigns** | Read outbound campaigns. |
| **Read settings** | Read customer settings and your plan's features, such as data retention, limits, notifications and 2FA rules. |
| **Edit calls** | Change tags and status (open/done), add comments, and assign or unassign calls. |
| **Edit campaigns** | Create and edit drafts, add and remove recipients, pause, resume and cancel. |
| **Edit agents** | Change the configuration and actions of phone agents, always previewed first, and restore an earlier state from the history. |

You always do the legal confirmation and the first start of a campaign in the app, not through the assistant.

The assistant shows you changes to an agent as a preview first. Only when you agree does it apply them, and they take effect from the next call. Every change is listed in the [agent history](https://docs.qutee.ai/en/agenten/verlauf-und-wiederherstellen/) as **Edit through AI app** with the badge **Connected app** and can be undone there. Switching an agent on or off is only possible in the app.

The assistant can only read settings, not change them. It can suggest changes and tell you where to make them in the app, using this help center. The help center is public and needs no permission of its own.

> **Caution:** Write access lets a connected AI change data in qutee. Only grant it to assistants you control.

## Connect Claude, ChatGPT or Claude Code with sign-in

You don't need an API key for these assistants. You sign in to qutee while connecting and approve the access.

1. Click your name to open the account menu and choose **Integrations**.
2. Open the **API & MCP** tab.
3. Under **Connect an MCP client**, copy the **MCP URL** with **Copy URL**.
4. Paste the URL into your assistant. The app shows the exact steps for your assistant:
   - **Claude** (web, desktop and mobile): Customize > Connectors > Add custom connector.
   - **ChatGPT**: In ChatGPT settings, enable developer mode for apps and connectors and add a custom MCP server. Whether this is possible depends on your ChatGPT plan.
   - **Claude Code**: Run the command from the app. Claude Code opens the sign-in itself.
5. Sign in to qutee when your assistant asks you to. If two-factor authentication is on, you also enter your code.
6. On the "Connect … to qutee" page, choose the permissions. Write permissions are under **Allow changes (optional)** and are not preselected.
7. Click **Allow**. You are taken back to your assistant.

The connection then appears in qutee under **API & MCP** > **Connected apps**.

> **Tip:** Only allow access if you just started the connection yourself. If the page says that the app registered itself, its name has not been verified.

## Connect other MCP clients with an API key

For clients in which you can set an Authorization header, for example Cursor or VS Code, you create an API key.

1. Open **Integrations** > **API & MCP**.
2. Click **Create key**.
3. Enter a **Name** that helps you recognize the key later, for example "Cursor laptop Jane".
4. Choose the **Permissions**. The read permissions are preselected, editing is optional. At least one permission is required.
5. Under **Expires**, choose a validity period: 30, 90, 180 or 365 days, or **Never**. 90 days is preselected.
6. Click **Create key**.
7. Copy the key with **Copy key**. It is shown only once and can't be retrieved later.
8. Use **Copy configuration** to copy the matching example for **Claude Code** or **Other MCP clients (JSON)** and add it to your client.
9. Click **Done**.

Keep the key safe, for example in a password manager. If it gets lost, revoke it and create a new one.

The list shows **Prefix**, **Permissions**, **Created**, **Expires**, **Last used** and **Status** for each key.

## End access

**Revoke an API key:**

1. Under **API keys**, click **Revoke** on the key.
2. Confirm with **Revoke**. Connected clients can no longer use the key afterwards.

You can see expired and revoked keys with **Show inactive keys**.

**Remove a connected app:**

1. Under **Connected apps**, click **Revoke** on the app.
2. Confirm. The app loses access immediately.

A key or connection also stops working if the person who created it is deleted or is no longer a **Company Admin**.

## Check that it works

1. Ask your assistant, for example: "Which calls did qutee have today?"
2. The answer should match the calls under **Calls**.
3. Under **API & MCP**, **Last used** shows a recent date for the key or the connected app.

## Common problems

**"Only administrators can connect AI apps for their own company."**: Sign in with an account that has the **Company Admin** role.

**"This connection request has expired or was already answered."**: Start the connection again in your assistant.

**The assistant can't change anything**: The key or the approval has no edit permission. Create a new key, or reconnect the app and allow the changes.

**The assistant reports that the agent has changed in the meantime**: Since the assistant read the agent, someone changed the same places. The assistant then applies nothing. Let it read the agent again and propose the change once more.

**The assistant can't read the settings**: Keys and connections created before the **Read settings** permission existed don't have it. Create a new key or reconnect the app.

## Next steps

- [Which systems qutee works with](https://docs.qutee.ai/en/integrationen/integrationen-ueberblick/)
- [Set up two-factor authentication](https://docs.qutee.ai/en/einstellungen/zwei-faktor-authentifizierung/)
