How to Use the Dotcom-Monitor MCP in Claude

Q: How do I connect Dotcom-Monitor to Claude Desktop?

Open your claudedesktopconfig.json file and add the server configuration under the mcpServers block. Provide your API credentials as environment variables, restart the app, and you will see the tools ready in your chat window.

Q: Can I filter monitoring devices by geographic location?

Yes, you can ask the agent to filter the output of listmonitoringdevices by cross-referencing it with the location IDs returned from listmonitoringlocations.

Pull real-time global website uptime and alert history from Dotcom-Monitor directly into your Claude Desktop chat to diagnose outages instantly.

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 Claude Desktop

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Track global Dotcom-Monitor uptime directly from Claude Desktop

The Dotcom-Monitor MCP Server lets your local Claude Desktop client query website uptime directly from your chat window. You can list your monitoring infrastructure inside Claude Desktop instantly without jumping between browser tabs. This server pulls live Dotcom-Monitor data directly to your local chat to keep your focus intact. By invoking `list_monitoring_devices` and `list_monitoring_locations` in Claude Desktop, your agent maps out where your tests run and which servers are reporting errors. You get immediate eyes on global latency issues inside the Claude Desktop interface right when they happen.

Diagnose Dotcom-Monitor performance dips inside Claude Desktop

This Dotcom-Monitor tracking tool provides Claude Desktop with direct access to historical performance metrics during active debugging sessions. When a Dotcom-Monitor outage alert hits, you can ask Claude Desktop to check if it is a transient blip or a systemic failure. You get raw telemetry summarized directly in the Claude Desktop chat window. Your Claude Desktop agent calls `get_device_monitoring_history` to pull recent Dotcom-Monitor uptime trends and cross-references it with hardware profiles using `get_device_details`. You don't have to write custom scripts to parse Dotcom-Monitor XML payloads when Claude Desktop can analyze them instantly.

Audit Dotcom-Monitor notification routing in Claude Desktop

This alert management MCP Server exposes active Dotcom-Monitor notification groups directly inside your Claude Desktop workspace. Outages get worse when the right people do not get the Dotcom-Monitor page, so you can verify who is on the hook for a failing endpoint in seconds inside Claude Desktop. You can check your current escalation paths directly in the Claude Desktop sidebar. The tool `list_alert_groups` pulls your active Dotcom-Monitor communication channels directly into Claude Desktop. If you need to verify which platform is failing, `list_available_platforms` shows Claude Desktop exactly where the monitoring agent is deployed.

Setup guide

Set up Dotcom-Monitor MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

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.
3

Start a conversation

Open a new chat. The Dotcom-Monitor MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Dotcom-Monitor MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under dotcom-monitor-mcp.

json

{
  "mcpServers": {
    "dotcom-monitor-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Claude Desktop

Open your `claude_desktop_config.json` file and add the server configuration under the `mcpServers` block. Provide your API credentials as environment variables, restart the app, and you will see the tools ready in your chat window.

Yes, you can use the Claude web interface to connect to a hosted version of this MCP Server. Paste your secure endpoint URL into the Integrations settings page to grant your web-based agent access.

You can ask the agent to run a quick check on your systems. It will call the tools to fetch the latest status updates, saving you from logging into the web portal.

Yes, you can ask the agent to filter the output of `list_monitoring_devices` by cross-referencing it with the location IDs returned from `list_monitoring_locations`.

Your API keys and device IDs are never stored on external servers or exposed to third parties. The server runs inside an ephemeral, zero-trust sandbox, meaning your credentials only pass through secure, encrypted memory during active tool execution.

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