How to Use the Dotcom-Monitor MCP in VS Code Copilot

Q: How do we share the Dotcom-Monitor setup with the whole team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and commit it. Any team member with the Copilot extension installed will automatically gain access to the configured tools.

Q: How do I check if a monitoring platform is supported?

Ask Copilot to run listavailableplatforms to get a list of supported environments, letting you verify compatibility before setting up a new device.

Keep your engineering team aligned inside VS Code Copilot with shared Dotcom-Monitor uptime data and live alert tracking.

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 VS Code Copilot

Create your Vinkius account to connect Dotcom-Monitor to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share Dotcom-Monitor status across VS Code Copilot teams

The Dotcom-Monitor MCP Server integrates real-time uptime telemetry directly into your team's VS Code Copilot workflow. Outages require immediate, coordinated team action inside VS Code Copilot. By committing the server configuration to your shared repository, every developer gets instant access to live Dotcom-Monitor performance metrics. When a service fails, any engineer can ask VS Code Copilot to run `list_monitoring_devices` to see which Dotcom-Monitor endpoints are down. This keeps your entire engineering organization aligned on the same live operational data inside VS Code Copilot.

Trace regional Dotcom-Monitor performance inside VS Code

This global telemetry MCP Server allows VS Code Copilot to query Dotcom-Monitor performance metrics from multiple geographic locations. Latency issues are often regional, making them incredibly difficult to debug from a local VS Code session. You can pinpoint exactly where the Dotcom-Monitor bottleneck is occurring directly from the VS Code Copilot chat interface. By calling `list_monitoring_locations` alongside `get_device_monitoring_history`, the VS Code Copilot agent correlates regional latency spikes with specific code paths. You can quickly determine in VS Code Copilot if a database query is slow globally or just lagging in Europe according to Dotcom-Monitor.

Verify Dotcom-Monitor thresholds inside VS Code Copilot

This diagnostic server lets you inspect active Dotcom-Monitor alert thresholds inside VS Code Copilot before committing your code. Changing endpoint behavior can easily trigger false alarms if your Dotcom-Monitor configurations are out of sync with your VS Code workspace. You can inspect active alarm thresholds inside VS Code Copilot before you merge a pull request to keep your SRE configurations aligned with your actual code. The VS Code Copilot agent calls `get_device_details` to verify current Dotcom-Monitor timeout settings and queries `list_alert_groups` to see who gets paged. You can commit your changes in VS Code Copilot knowing you will not wake up the on-call engineer by accident.

Setup guide

Set up Dotcom-Monitor MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Dotcom-Monitor MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Dotcom-Monitor tools listed. Try asking: "List my recent Dotcom-Monitor transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and commit it. Any team member with the Copilot extension installed will automatically gain access to the configured tools.

No, it runs under the standard developer permission model. The extension uses your local configuration file to execute queries securely without elevated system privileges.

Yes, you can use the Copilot chat panel or inline agent to query active notifications and device details while you are working in your workspace.

Ask Copilot to run `list_available_platforms` to get a list of supported environments, letting you verify compatibility before setting up a new device.

All communication runs through a local subprocess utilizing standard I/O channels. Your alert configurations and performance metrics are never sent to external AI training sets, keeping your operational data completely private.

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