How to Use the Dotcom-Monitor MCP in Google ADK

Q: How do I register the Dotcom-Monitor MCP Server with my Google ADK agent?

Install the SDK with pip install google-adk and create an McpToolset pointing to your HTTP endpoint. Pass this toolset directly into the tools parameter when initializing your LlmAgent.

Q: Can I restrict which Dotcom-Monitor tools my Google ADK agent can access?

Yes, you can pass a list of specific tool names to your McpToolset configuration. This lets you restrict your Gemini agent to only run listmonitoringdevices while blocking access to history tools.

Q: How does Google ADK handle large payloads from Dotcom-Monitor history tools?

Gemini models handle massive context windows easily. When getdevicemonitoringhistory returns large datasets, the ADK feeds the entire raw payload directly into the model without truncation.

Connect Dotcom-Monitor to your Google ADK pipelines to feed real-time uptime telemetry into enterprise Gemini models.

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 Google ADK

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Analyze Global Outages with Gemini and Google ADK

Feed raw geographic data from `list_monitoring_locations` directly into your Gemini long-context window. Your Google ADK agent processes thousands of regional latency metrics simultaneously to find patterns that standard dashboards miss. By combining this MCP Server with BigQuery datasets, your agent correlates live network performance against historical infrastructure logs. The agent runs `get_device_monitoring_history` to pull raw statistics and write them to your cloud warehouse.

Dynamic Device Auditing via Google ADK

Your enterprise agent uses `list_monitoring_devices` to audit your active monitoring footprint across all cloud zones. It automatically maps your Google Cloud virtual machines against active monitoring targets to find unmonitored endpoints. The agent calls `get_device_details` to verify that your critical services have active checks configured. If a gap is found, the agent flags the missing coverage directly inside your Vertex AI monitoring console.

Map Monitoring Platforms to Enterprise Infrastructure

Use `list_available_platforms` to let your agent discover which monitoring types are active on your account. Your Google ADK agent reads this data via the MCP Server to verify that your API checks align with your Google Cloud DNS configurations. The agent checks `list_alert_groups` to map active alert pathways directly to your internal site reliability engineering teams. This ensures your automated diagnostic pipelines always route high-priority alerts to the correct personnel.

Setup guide

Set up Dotcom-Monitor MCP in Google ADK

Prerequisites

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

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Dotcom-Monitor tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Dotcom-Monitor_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Dotcom-Monitor tools via MCP.",
    tools=mcp_tools,
)

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 Google ADK

Install the SDK with `pip install google-adk` and create an `McpToolset` pointing to your HTTP endpoint. Pass this toolset directly into the `tools` parameter when initializing your `LlmAgent`.

Yes, you can pass a list of specific tool names to your `McpToolset` configuration. This lets you restrict your Gemini agent to only run `list_monitoring_devices` while blocking access to history tools.

Gemini models handle massive context windows easily. When `get_device_monitoring_history` returns large datasets, the ADK feeds the entire raw payload directly into the model without truncation.

The server runs securely on Vinkius, but your Google ADK agent can connect to it from any environment, whether it is running on Cloud Run or your local workstation.

This server only handles your performance metrics and alert group configurations. The server handles your credentials inside an ephemeral V8 sandbox, meaning your raw API tokens are never sent to the model or saved in Google Cloud logs.

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