Supercharge your AI with idloom. Manage Event Logistics and Finances from your Agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
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.
What your AI can do
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.
Get detailed records about specific events or list all current attendees across multiple events.
Check the status of invoices, view transaction logs, and see which registration forms were used for billing.
Ask an AI about this
Compatible AI Apps
OAuth 2.0 Compatible Gemini Waiting for input…
idloom: 10 Event Management Tools
These tools let you manage everything related to an event, from listing general events to getting specific attendee details or checking financial records.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using idloom on VinkiusGet 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.
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token from
cloud.vinkius.com. For OAuth-protected servers, expand Advanced
settings to add credentials.
Start a conversation
Open a new chat. The idloom integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with idloom, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by idloom. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking Event Data Used to Be A Three-System Nightmare
Today, if you want to know who attended an event and whether they paid, you open three tabs. First, you check the registration platform for the attendee list. Second, you jump into your accounting software to pull invoices based on names or dates. Third, you have to cross-reference transaction logs in a separate system just to see if payment cleared. It's constant clicking and copy-pasting.
With this MCP, your agent handles it all. You tell your client: 'What are the financials for the Annual Summit?' The agent runs list_events first, then pulls the necessary attendees using list_attendees, and finally reviews every outstanding invoice via list_invoices. What you get is one complete answer.
The idloom MCP Delivers a Single Source of Truth
You instantly eliminate the need to manually reconcile attendee lists with financial records, or to check if an invoice was created before the payment cleared. The agent handles that data linking for you.
Now, your AI client doesn't just retrieve data; it connects the dots between who signed up and what money moved. That’s a massive difference.
What your AI can actually do with this
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.
019d75b7-d7e1-7249-bcf2-3732bfffadae 
Here's how it actually works
The bottom line is you don't have to jump between your registration dashboard, your accounting software, and your event calendar anymore.
Tell your AI client to find an event by ID or list all events. This gives you the central data point.
Next, ask your agent to pull attendee details related to that event, then check for any associated invoices and transactions.
Your agent combines this information into a single report, showing who attended, what they paid, and when.
Who is this actually for?
Event managers who hate the manual effort of reconciling sign-ups with revenue. Operations staff dealing with complex event logistics or finance teams needing a clear view of payment status.
Uses this to list events and get attendee details, verifying that the right people are marked present for upcoming functions.
Runs reports using this MCP to pull all invoices and transactions, making sure every event has its revenue tracked correctly.
Combines list_emails and list_categories to audit registration forms and ensure data integrity across the entire user base.
What Changes When You Connect
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.
See it in action
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.
The honest tradeoffs
Mixing Up Data Sources
Trying to manually combine the attendee count from a spreadsheet with the payment data in a separate accounting portal.
Don't copy-paste. Use this MCP: Your agent calls list_attendees for the roster, then calls list_invoices and list_transactions to get the financials. It does both steps automatically.
Missing Event Context
Pulling a generic list of transactions without knowing which event they relate to, leading to mixed-up numbers.
Always start by calling get_event or list_events first. This gives the agent the necessary context ID so that all subsequent calls (like list_transactions) are scoped correctly.
When It Fits, When It Doesn't
Use this MCP if your core problem involves reconciling three things: who was there, and how much money they generated. You need to connect event logistics with financial records. For example, 'Show me all attendees from the Spring Gala (list_events) whose invoices are still pending payment (list_invoices).' Don't use this if you just need a simple contact list; for that, using only list_emails is enough. If your primary goal is managing internal systems or user roles, look at specialized identity management tools instead.
Questions you might have
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.
We've already built the connector for idloom. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.