-
General information
-
Account Settings
- Creating & managing your personal doo account
- Organization settings: Managing your account settings
- User Management: How to Work as a Team
- Payment Process: How to manage payment options
- How to reset your password
- Changing the email address of your doo account
- The doo account packages
- What can I do if a doo site does not load
- Adjusting standard labels and texts of the doo booking process
- Password Security using doo: What options are available?
- How do I delete my account
-
Events
-
- Edit email contents
- Using placeholders in booking email templates
- How to adjust invoice contents
- Attendee tickets and QR code scanning
- How do doo tickets look like?
- E-mail attachments for bookers and attendee
- Certificates & Co: Create custom documents
- Define your own booking conditions
- Revenue Disbursement: Entering and editing invoice address & bank account information
- Create bilingual (multilingual) events
- Bookings with manual approval
- Create a waiting list
- Access codes and promotion codes: Discounted tickets for your participants
- General Event Documents: Share Presentations and Materials with Attendees
- Event Staff: Restricted user access for specific events
- doo Widgets: Integration into your own website
- doo Default Event Website and Custom Event Website
- How to create a booking process in english
- Overview: Providing event documents such as flyers, presentations or certificates
- How does the booking process work for my attendees?
- How do I make test bookings?
- Creating exclusive registration access for selected contacts
- Delete ticket categories & change prices and sales periods after go-live
- Cancellation of events
- What are event fields and how do I use them best ?
- Shorten the booking process and prefill data: How to make the booking process as convenient as possible for bookers
- Tips for virtual events with doo
- Integration into your own Facebook page
- Event Templates: Creating templates for your events
-
Manage Bookings
- Manage bookings and attendees
- Monitoring incoming bookings
- The attendee overview
- Download booking overview and attendee list
- Invitation list: Track the registration status of specific contacts
- Manual registration
- Resend automatically generated emails
- Rebooking: How to change existing bookings
- Cancellation & Refund Handling
- Booking self-service: Allow bookers to subsequently access and edit their bookings
- Change of attendee data and invoice address
- Bank transfer: How to deal with pending transactions
- What to do, if someone has not received their confirmation e-mail or ticket
-
Contact Management
- Contacts: Introduction and Topic Overview
- Contact details: Collect cross-event contact information
- Overview contact data fields
- Managing contact data fields
- Creating contacts - How do contacts get into the doo contact center?
- Contact import - Bulk creation and editing of contacts
- Managing existing contacts
- Creating and managing contact groups
- Datamatching & Synchronization of booking data and doo contact
- Email subscriptions: Double opt-in & opt-out options at doo
- Deleting contacts
-
Emails
-
Websites
- The doo website editor: create an individual event page
- Mobile optimization: Customize your site for all your devices
- Installing different tracking tools on the website
- Creating a SSL certificat (HTTPS) to ensure data security
- Website Tracking: How to integrate doo into your Google Analytics
- E-Commerce dataLayer-Events in our Widgets
-
On-Site and Attendance
-
Additional Functions
- Optional Service: Refund handling via doo
- Ticket design: How to get your ticket in the desired design
- Forms - Set up surveys and feedback requests for your attendees
- Embedded Reports
- Customer specific sender emails
- Add calendar entries to your event communication
- Filtering widgets: Adding filter options and (pre)filtering events
- Widgets and Accessibility
-
Automations
-
Integrations
-
Booker & Attendee FAQ
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_secretExample with made-up values:
| Value |
|---|---|
Client ID |
|
Client Secret |
|
Joined |
|
Token (Base64) |
|
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
Open the Start menu, type PowerShell, and open Windows PowerShell.
Copy the line below. Replace
YOUR_CLIENT_IDandYOUR_CLIENT_SECRETwith your own values, keeping the colon between them and the quotes around them.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
Open Terminal: press Cmd + Space, type Terminal, and press Enter.
Copy the line below. Replace
YOUR_CLIENT_IDandYOUR_CLIENT_SECRETwith your own values, keeping the colon between them and the quotes around them.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
abc123ands3cret, you should getYWJjMTIzOnMzY3JldA==.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/mcpAuthorization 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
Bearerfollowed by your token, for exampleBearer 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
Ensure that at least one event exists in doo.
In your AI tool, start a new chat and make sure the doo connection is switched on.
Enter a first request, for example: “Show me my upcoming events in doo.” or “Which doo organization am I connected to?”
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):
Log in to doo and go to the organization settings via the gear icon in the header.
Select the “Users” tab and go to the “Client Credentials” section.
Find the old client credentials in the list and click the trash icon on the right to delete them.
Create new client credentials as described in step 1.
Create a new token as described in step 2.
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.