Skip to main content
Ausdrucken

Connect doo to AI agents (MCP server)

More and more companies want to not only manage event and attendee data in doo, but also reuse it in their own systems, automations, or AI‑driven workflows.

With the doo MCP Server (Model Context Protocol), we provide a standardized interface that allows MCP‑enabled clients to access doo data in a structured way.

This also gives occasional users an easy entry point to doo’s powerful event automation platform. For example, you can use natural language to create new events from a predefined event template or as a copy of an existing event (for more information, see our help center article on event templates). For an overview of everything agents can and cannot do in doo, see the article doo MCP Server for Event Organizers: Overview of All Tools.

To use the doo MCP Server, the following steps are required. Please note that access is limited to a single doo organization.

1. Create Client Credentials in doo

To access the MCP Server, you need client credentials. These act as a username and password for technical applications and are assigned to a specific doo organization.

  • Log in to your doo organization.

  • Go to the organization settings via the gear icon in the header (administrator rights required).

  • Select the “Users” tab and navigate to the “Client Credentials” section.

  • Click “New Client Credentials”, assign an internal name, and click “Create”.

doo will then generate a Client ID and a Client Secret.

Important: The Client Secret cannot be displayed again after closing the pop-up! Make sure to save it immediately (e.g. in a password manager) and treat this information with the same level of confidentiality as your doo login credentials.

2. Generate Your Access Token

Your MCP client signs in to doo with an access token, called a Bearer token. You create it once from the Client ID and Client Secret you got in step 1.

2.1. How the token is built

The token is your Client ID and Client Secret joined by a colon, then converted into Base64 format:

client_id:client_secret

Example with made-up values:

 

 

Value

Client ID

abc123

Client Secret

s3cret

Joined

abc123:s3cret

Token (Base64)

YWJjMTIzOnMzY3JldA==

You don’t have to do this by hand. The commands below do it on your own computer and show the finished token.

⚠️ Important: Your token works like a password for your doo organization. Create it only on your own computer, and never paste your Client ID, Client Secret, or token into websites, online converters, emails, or chats! We recommend to store it in a password manager.

2.1.1. Create the Token on Windows

  1. Open the Start menu, type PowerShell, and open Windows PowerShell.

  2. Copy the line below. Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with your own values, keeping the colon between them and the quotes around them.

  3. Paste the line into PowerShell and press Enter. Your token is shown on the next line.

If PowerShell is blocked on your work computer, ask your IT team for help.

[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("YOUR_CLIENT_ID:YOUR_CLIENT_SECRET"))
 

2.1.2. Create the Token on MacOS

  1. Open Terminal: press Cmd + Space, type Terminal, and press Enter.

  2. Copy the line below. Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with your own values, keeping the colon between them and the quotes around them.

  3. Paste the line into Terminal and press Enter. Your token is shown on the next line.

 

printf '%s' 'YOUR_CLIENT_ID:YOUR_CLIENT_SECRET' | base64

Tip: Edit the line in a text editor first, then paste the finished line. Close the window when you’re done.

2.2. Check your result

  • If you test with the example values abc123 and s3cret, you should get YWJjMTIzOnMzY3JldA==.

  • A real token is one long line of letters, numbers, and possibly +, /, or = at the end, with no spaces.

  • In step 3 you’ll use it like this. Note the word Bearer and the space after it:

Authorization: Bearer YWJjMTIzOnMzY3JldA==
 

If something goes wrong: If the connection fails later, make sure there are no extra spaces in your Client ID or Secret and that you copied the whole Client Secret. If you lost the Client Secret, create new client credentials in doo (step 1) and run the script again.

3. Configure MCP Server

Configure your MCP client as described below:

MCP Server URL:

https://mcp-organizer.doo.net/mcp
 

Authorization Header:

Authorization: Bearer <YOUR_BASE64_TOKEN>
 

Example with the made-up token from step 2:

Authorization: Bearer YWJjMTIzOnMzY3JldA==
 

⚠️ Important: There must be exactly one space between “Bearer” and your token. If your AI tool asks only for a header value, enter Bearer followed by your token, for example Bearer YWJjMTIzOnMzY3JldA==.

Setup guides for popular agents

The exact steps differ for each AI tool. Platform-specific steps and limits are described in our step-by-step guides:

4. Test connection

  1. Ensure that at least one event exists in doo.

  2. In your AI tool, start a new chat and make sure the doo connection is switched on.

  3. Enter a first request, for example: “Show me my upcoming events in doo.” or “Which doo organization am I connected to?”

  4. If the agent shows your organization name or a list of your events, the connection has been successfully established.

Your AI tool may ask you to confirm before it uses a doo tool. For this first test, the agent only reads data and does not change anything in doo.

5. Processing Personal Data via Agents

If you process personal data from doo via an agent, you must ensure that GDPR requirements (e.g. logging, access control, and traceability) are fulfilled.

You have two options:

a) Implementation in your agent platform
You ensure that GDPR‑relevant features are implemented within your agent environment, such as:

  • Logging / audit trails

  • Traceability of actions

  • Per‑user access control

  • Separation of user contexts

b) Implementation in the doo platform
Alternatively, you can use the corresponding features provided by doo.

Important: In this case, each end user must have their own client credentials.

  • Separate credentials must be created in doo per user

  • Each user connects once using their own credentials

  • All actions are executed in the context of that user

The exact setup currently depends on the agent platform used.

Example (Microsoft Copilot):
Setting “Authentication type” → “End user credentials”

6. Lost or Leaked Client Secret?

If you lost the Client Secret, or if the Client Secret or token may have been seen by someone else (for example sent by email or pasted into a website):

  1. Log in to doo and go to the organization settings via the gear icon in the header.

  2. Select the “Users” tab and go to the “Client Credentials” section.

  3. Find the old client credentials in the list and click the trash icon on the right to delete them.

  4. Create new client credentials as described in step 1.

  5. Create a new token as described in step 2.

  6. Update the token in your AI tool. Depending on the tool, you may have to remove the doo connection and add it again.

As soon as the old credentials are deleted, the old token stops working.

Table of Contents

Didn’t find the answer to your question?

Our Support Team is happy to help

Scroll to Top