> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zuddl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to the Zuddl MCP server

> Connect AI assistants to Zuddl and see every tool they can use

The Zuddl MCP server lets AI assistants such as Claude and ChatGPT work with your Zuddl organization through the [Model Context Protocol](https://modelcontextprotocol.io) (MCP). Your assistant can list and create events, manage sessions, speakers, sponsors and locations, look up and register attendees, and answer analytics questions.

This reference lists every tool the server offers. It is generated from the live server on every release, so it always matches what your assistant sees.

# Server URL

```text theme={null}
https://setup.zuddl.com/api/mcp
```

> [!NOTE]
>
> If your Zuddl account is hosted in another region (see [EU region](https://docs.zuddl.com/getting-started/eu-region.md)), use the domain you sign in to the Zuddl dashboard with, followed by `/api/mcp`.

# Connecting your assistant

1. In your assistant, add a remote (custom) MCP server and enter the server URL. See the examples below.
2. Your assistant opens a Zuddl sign-in page. Sign in and approve access.
3. The assistant can now call the tools in this reference on your behalf.

**Claude**

In Claude on the web or the Claude desktop app:

1. Go to **Settings** > **Connectors** and click **Add custom connector**.
2. Enter `Zuddl` as the name and `https://setup.zuddl.com/api/mcp` as the URL, then click **Add**.
3. Click **Connect** and sign in to Zuddl.

On Team and Enterprise plans, an owner adds the connector in **Organization settings** > **Connectors** first. Members then connect to it from their own settings.

**ChatGPT**

In ChatGPT on the web:

1. Open **Plugins**, click **+** and choose **Add custom MCP server**.
2. Enter `Zuddl` as the name and `https://setup.zuddl.com/api/mcp` as the server URL, and choose **OAuth** for authentication.
3. Accept the warning, then sign in to Zuddl.

Custom MCP servers are available on ChatGPT Business, Enterprise and Edu plans. If you don't see **Add custom MCP server**, ask your workspace admin to allow custom MCP servers.

The assistant acts with your Zuddl permissions. It can only see and change what you can see and change in the dashboard.

> [!NOTE]
>
> AI features must be enabled for your organization. If your assistant can't connect, contact your Customer Success Manager or write to [support@zuddl.com](mailto:support@zuddl.com).

Sign-in uses OAuth 2.1 with dynamic client registration and PKCE, so there is no API key to copy. Your assistant handles the sign-in flow.

# How tools are called

Assistants call a tool with a JSON-RPC `tools/call` request. The request's `name` is the tool name and its `arguments` match the request body documented on the tool's page.

The `/tools/<name>` paths in this reference identify each tool. They are not HTTP endpoints you can call directly.

# Behaviour labels

Every tool page shows a behaviour label, taken from the tool's MCP annotations.

| Label | Meaning |
| - | - |
| 🔒 Read-only | Reads data and changes nothing. |
| ✏️ Write | Creates or updates data, but does not delete it. |
| ⚠️ Destructive | Deletes or removes data. Most assistants ask you to approve these calls before running them. |
| 🔁 Idempotent | Calling it again with the same arguments has no further effect. |

# Tools and the Public API

Many tools perform the same operation as a [Zuddl Public API](https://docs.zuddl.com/api-reference/introduction.md) endpoint. Their pages say **Same as Public API** and link to that endpoint's page, where you can see the full response format.

Tools marked **MCP-only** have no Public API equivalent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.