Integrating doo with 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, new events can be created or prepared using natural language – such as based on predefined event templates (for more information, see our help center article on event templates).
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 Bearer Token
To authenticate with the MCP Server, a Bearer Token is required. It is created from the following string:
client_id:client_secret
This string is Base64 encoded.
Example:
abc123:s3cret
→ YWJjMTIzOnMzY3JldA==
Simple ways to perform Base64 encoding
- Windows (recommended): Use tools such as certutil.
- Online Base64 encoders: Suitable for testing or temporary credentials. For production access, we recommend using a local solution.
3. Configure MCP Server
Configure your MCP client as described below:
MCP Server URL:
https://mcp-organizer.doo.net/mcp
Authorization Header:
Authorization: Bearer <IHR_BASE64_TOKEN>
4. Test connection
- Ensure that at least one event exists in doo.
- Run an initial query in your MCP client.
- If organization or event data is returned, the connection has been successfully established.
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”