How to Use the Hologram.io MCP in CrewAI

Q: Is it possible to limit which Hologram.io tools a specific CrewAI agent can use?

Yes. When you instantiate the MCPServerHTTP tool in CrewAI, you can use the toolfilter argument. This lets you pass a specific list of tool names, ensuring an agent can only access the Hologram.io functions you've explicitly approved for its role.

Q: What's a good agent setup for managing Hologram.io costs with CrewAI?

A three-agent crew works well. Agent 1 ('Analyst') runs getdailyusagestats to find overages. Agent 2 ('Prioritizer') uses getdevicedetails to see if the device is critical. Agent 3 ('Controller') then calls pausesimdata only on non-critical, high-usage devices.

Deploy an autonomous IoT operations team for Hologram.io with CrewAI. Your agents are on the job 24/7.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Hologram.io MCP to CrewAI

Create your Vinkius account to connect Hologram.io 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 Hologram.io with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

The Autonomous Ops Crew

Assign roles to a crew of agents to manage your fleet. A 'Monitor' agent can use `get_daily_usage_stats` and `get_recent_data_sessions` to watch for weird activity. It passes findings to a 'Regulator' agent for analysis. If the Regulator decides action is needed, it tasks an 'Enforcer' agent, the only one with permission to execute `pause_sim_data` or `unpause_sim_data`. This division of labor makes your automation safer and easier to audit.

The Security Patrol

Your agents can act as a security team for your physical assets. A 'Scout' agent periodically runs `get_device_locations` to get a fix on every device. It compares these locations against a known safe area. If a device is out of bounds, the Scout alerts a 'Containment' agent. This agent can immediately `pause_sim_data` to prevent further use and log all relevant info from `get_device_details` for human review. This is how autonomous security works.

A Resource Management Crew

This MCP server gives your CrewAI agents the tools to manage costs. A 'Planner' agent analyzes the output of `list_sim_cards` and `list_available_data_plans` to identify inefficient plan assignments. It then creates a migration plan. The Planner passes the plan to an 'Executor' agent, which handles the actual re-provisioning. This creates a closed loop where your agents are constantly working to optimize your Hologram.io resources without any human input.

Setup guide

Set up Hologram.io 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 Hologram.io tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Hologram.io 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="Hologram.io Analyst",
        goal="Access and analyze Hologram.io data via MCP.",
        backstory="Expert analyst with direct Hologram.io access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Hologram.io 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 Hologram.io. 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 Hologram.io 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 Hologram.io MCP in CrewAI

Define two agents. The first, a 'Monitor' agent, gets tools like `get_daily_usage_stats`. The second, an 'Enforcer' agent, gets `pause_sim_data`. The Monitor's task is to find anomalies and pass the device ID to the Enforcer for action.

Yes, that's the core pattern for using CrewAI with this server. Create a 'Watcher' agent with read-only tools like `get_daily_usage_stats` and an 'Actor' agent with action tools like `pause_sim_data`. This separation of duties is a key safety feature.

Yes. When you instantiate the `MCPServerHTTP` tool in CrewAI, you can use the `tool_filter` argument. This lets you pass a specific list of tool names, ensuring an agent can only access the Hologram.io functions you've explicitly approved for its role.

A three-agent crew works well. Agent 1 ('Analyst') runs `get_daily_usage_stats` to find overages. Agent 2 ('Prioritizer') uses `get_device_details` to see if the device is critical. Agent 3 ('Controller') then calls `pause_sim_data` only on non-critical, high-usage devices.

Your agents only see the data returned by the tools they are permitted to use. For example, an agent with `get_device_locations` will see location data, while one without it won't. All traffic is routed through Vinkius's secure, single-tenant sandboxes, and your API key is never exposed to the agents themselves.

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