# idloom MCP MCP

> Manage events and associated finances with idloom. This MCP lets your agent retrieve event details, track all attendees, pull transaction logs, and review invoices from a single API connection. It's designed for automating entire event logistics workflows, making sure registration data always matches the financial records.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** event-registration, attendee-management, invoicing, logistics-automation, event-planning

## Description

You can use this MCP to handle the full lifecycle of an event, from initial planning to post-event billing. Need to know who showed up and how much money was made? Your agent pulls all that together. You start by pulling general information about specific events or listing everything happening in your account. Next, you pull attendee lists to get details on every person registered. If you need to check the cash flow, you can list invoices and view detailed transactions. This keeps event logistics moving without manual data checks. With Vinkius, connecting this MCP means your agent sees all those pieces—the people, the events, the money—and works with them automatically. It's basically giving your workflow a central source of truth for every single thing that happens at an event.

## Tools

### get_attendee
Pulls specific details for one attendee based on their ID.

### get_event
Retrieves all data points for a single event.

### list_attendees
Gathers and lists details for every attendee registered.

### list_categories
Shows the different categories used across all event registrations.

### list_emails
Provides a list of all email addresses recorded in your system.

### list_events
Lists every event managed within idloom.

### list_invoices
Retrieves a comprehensive list of all invoices created for events and attendees.

### list_registration_forms
Lists every registration form available, helping you audit data sources.

### list_transactions
Pulls a history of all financial transactions associated with the events.

### list_webhooks
Displays all active webhooks configured for real-time data updates.

## Prompt Examples

**Prompt:** 
```
List all active events in my idloom account.
```

**Response:** 
```
I'll fetch the list of events for you.
```

**Prompt:** 
```
Show me the attendee list for event ID '123'.
```

**Response:** 
```
I'll retrieve the attendee list for that specific event.
```

**Prompt:** 
```
Check for any unpaid invoices.
```

**Response:** 
```
I'll look up your invoices and highlight any that are pending payment.
```

## Capabilities

### Pull Event and Attendee Records
Get detailed records about specific events or list all current attendees across multiple events.

### Review Financial History
Check the status of invoices, view transaction logs, and see which registration forms were used for billing.

## Use Cases

### Post-Event Billing Audit
The event finished and the finance team needs a full revenue report. The agent is asked to check for unpaid invoices by pulling list_invoices, then cross-references those IDs against list_transactions to highlight exactly which payments are missing.

### Attendee Roster Verification
An event coordinator needs a final count of all people who signed up. They use list_attendees first, and if they need specific details for just one person, the agent calls get_attendee to pull the complete profile.

### Data Cleanup Project
The ops analyst needs to know which people signed up through an old form. They run list_registration_forms and then filter by category using list_categories to find all affected attendees.

## Benefits

- Automate attendance tracking: Use list_attendees to pull full rosters instantly, eliminating the need to manually export names and check them against a separate spreadsheet.
- Financial reconciliation in minutes: Run queries using list_invoices and list_transactions. You can verify revenue totals by matching invoice data to actual payment logs.
- Deep event understanding: By calling get_event or list_events, your agent gathers all the necessary context—from capacity limits to specific dates—so you don't forget critical details.
- Streamline communications: Use list_emails and list_categories together. Your agent can check who belongs to a certain group and pull their contact information for targeted follow-up.
- Audit data sources: With list_registration_forms, you always know which specific form was used to collect an attendee's details, improving your compliance records.

## How It Works

The bottom line is you don't have to jump between your registration dashboard, your accounting software, and your event calendar anymore.

1. Tell your AI client to find an event by ID or list all events. This gives you the central data point.
2. Next, ask your agent to pull attendee details related to that event, then check for any associated invoices and transactions.
3. Your agent combines this information into a single report, showing who attended, what they paid, and when.

## Frequently Asked Questions

**How do I get idloom API credentials?**
Log in to your idloom.events backend, navigate to Integrations, create a Custom Integration, and enable API access to generate your unique Bearer Token.

**Which version of the API is used?**
This MCP uses idloom API v4, the latest stable version for event and attendee management.

**Can I see attendee check-ins?**
Yes, the list_attendees tool provides access to attendee details including their registration and status information.

**When I use the `list_events` tool, how does the MCP handle paginated results if my organization has many events?**
The system handles pagination automatically. When the initial list is retrieved, you'll receive a cursor or a next page token. You pass that token back to the MCP on subsequent calls until all available records are gathered.

**Can I use `get_attendee` details to cross-reference and find their associated payment history using the invoice data?**
Yes, you must link them manually. You'll need to pass both the attendee ID from `get_attendee` and the relevant event ID when calling the transaction or invoice tools for correlation.

**If I use the `list_webhooks` tool, how do I verify which webhooks are currently active and what endpoints they point to?**
The output of `list_webhooks` shows the status (active/inactive) and the target URL for every webhook. This lets you confirm exactly where data is being sent out from your idloom account.

**I want to filter attendees by specific groups; how do I combine `list_categories` with the `list_attendees` tool?**
You must use the category ID retrieved from `list_categories`. This ID acts as a required parameter when calling `list_attendees`, allowing you to narrow down the user list effectively.

**What information do I get if I run `list_transactions` and find an entry with a 'failed' status?**
The MCP provides specific failure codes, along with a detailed message explaining why the transaction failed. You need to pass the unique transaction ID to see the full error context.