How to Use the idloom MCP in CrewAI

Q: Can I limit which idloom tools my agents can access via MCP?

Yes, you can use the MCPServerHTTP class with a tool filter. This lets you restrict access, ensuring your crew can only call listemails and not modify sensitive transaction records.

Deploy a collaborative crew of AI agents to manage your idloom events, invoices, and attendees autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect idloom MCP to CrewAI

Create your Vinkius account to connect idloom to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup idloom with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative Event Management Teams

CrewAI allows you to run multiple specialized agents using an MCP Server to divide and conquer your event operations. One agent can monitor registration trends using `list_registration_forms` while another checks billing status via `list_invoices`. They share context naturally. When the billing agent finds an unpaid balance, it hands the attendee ID to the operations agent, which calls `get_attendee` to find their contact information and queue an email.

Autonomous Transaction Audits via CrewAI

Running manual financial checks is a waste of time. Your crew can run scheduled audits by pulling `list_transactions` and comparing them against the event categories in `list_categories`. First, the auditor agent compiles the transaction list. After that, the reporter agent uses `list_emails` to verify which confirmation messages went out to the attendees.

Multi-Agent Webhook and Event Monitoring

Keep your system running smoothly by assigning an agent to watch your integration health. By using this MCP Server, your crew can call `list_webhooks` to ensure your external connections are active. If a webhook fails, the monitoring agent calls `list_events` to locate the broken event pipe. It then hands the diagnostic data to a coordinator agent to alert your developers.

Setup guide

Set up idloom MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke idloom tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="idloom Analyst",
    goal="Access and analyze idloom data via MCP.",
    backstory="Expert analyst with direct idloom access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent idloom transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="idloom Analyst",
        goal="Access and analyze idloom data via MCP.",
        backstory="Expert analyst with direct idloom access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent idloom transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect idloom now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about idloom MCP in CrewAI

You pass the server URL in the agent configuration under the MCP Server configuration. This gives that specific agent access to tools like `list_events` and `get_event` while keeping other agents focused on different tasks.

Yes. You can set up a multi-agent crew where one agent uses `list_attendees` to manage participants, and another uses `list_invoices` to track payments, sharing memory to resolve discrepancies.

You can use stdio, SSE, or Streamable HTTP. The framework handles the connection details, letting your agents call `list_registration_forms` or `list_categories` without custom API wrappers.

Yes, you can use the `MCPServerHTTP` class with a tool filter. This lets you restrict access, ensuring your crew can only call `list_emails` and not modify sensitive transaction records.

All transactions, invoices, and attendee details are fetched over encrypted channels directly from the idloom API. The Vinkius runtime executes these queries inside short-lived, isolated environments that wipe all session tokens and data payloads the moment the crew finishes its task.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript