How to Use the Dotcom-Monitor MCP in CrewAI

Q: How do I pass the Dotcom-Monitor tools to my CrewAI agents?

You can pass the Vinkius URL directly in the mcps parameter of your CrewAI agent definition. This automatically registers the monitoring tools for that specific agent.

Q: Can I limit which Dotcom-Monitor tools a CrewAI agent can access?

Yes, you can use the MCPServerHTTP class from the CrewAI MCP package and apply a toolfilter. This restricts sensitive tools like alert configurations to your supervisor agents.

Q: How do CrewAI agents handle historical Dotcom-Monitor data?

Agents use getdevicemonitoringhistory to retrieve performance trends over time. This allows your research agent to analyze patterns and write post-mortem reports.

Deploy specialized CrewAI agent teams to monitor, diagnose, and resolve uptime alerts autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dotcom-Monitor MCP to CrewAI

Create your Vinkius account to connect Dotcom-Monitor 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 Dotcom-Monitor with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate Multi-Agent Incident Audits

`get_device_details` provides granular configuration parameters for any monitored target. Your diagnostic agent queries this tool to understand the baseline settings of a failing service. While one CrewAI agent inspects the device setup, a secondary analyst agent can cross-reference the logs. This collaborative approach isolates environmental issues without human intervention.

Map Regional Outages Collaboratively

`list_monitoring_locations` returns the complete set of global monitoring nodes. A specialized network agent uses this data to map out exactly which regions are experiencing packet loss. By sharing this state in CrewAI's memory, your agents quickly determine if an outage is localized. The crew then coordinates to alert regional on-call engineers.

Connect CrewAI Teams to an MCP Server

`list_alert_groups` pulls the active notification channels configured in your account. Your manager agent reads this list to determine the correct escalation path during an outage. Exposing this MCP Server to your crew requires only passing the Vinkius URL in your agent definition. Your autonomous team can immediately query live monitoring data to make informed escalation decisions.

Setup guide

Set up Dotcom-Monitor 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 Dotcom-Monitor tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

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

You can pass the Vinkius URL directly in the `mcps` parameter of your CrewAI agent definition. This automatically registers the monitoring tools for that specific agent.

Yes, you can use the `MCPServerHTTP` class from the CrewAI MCP package and apply a `tool_filter`. This restricts sensitive tools like alert configurations to your supervisor agents.

Agents use `get_device_monitoring_history` to retrieve performance trends over time. This allows your research agent to analyze patterns and write post-mortem reports.

The integration supports stdio, SSE, and Streamable HTTP transports. This gives you the flexibility to run your crew locally or deploy it as a hosted service.

This integration processes your device IDs, alert configurations, and historical telemetry data. Vinkius runs the server in an isolated V8 sandbox, ensuring your private monitoring infrastructure metrics are never exposed.

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