How to Use the Dotcom-Monitor MCP in Vercel AI SDK

Q: How do I register Dotcom-Monitor tools within my Vercel AI SDK project?

Install the @ai-sdk/mcp package and initialize the client using the HTTP transport. Pass the output of mcpClient.tools() directly into your generateText or streamText calls to expose the monitoring tools to your agent.

Q: What is the best way to handle streaming errors when querying Dotcom-Monitor with Vercel AI SDK?

You should wrap your streamText call in standard try-catch blocks and ensure you call mcpClient.close() in a finally block. This prevents connection leaks and ensures your UI handles API timeouts gracefully.

Q: How does the agent know which monitoring platforms are available?

Your agent queries listavailableplatforms to check which monitoring environments exist in your account. This prevents the LLM from attempting to query metrics for unsupported device types.

Feed real-time global uptime data directly into your Vercel AI SDK interface without blocking the main UI thread.

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 Vercel AI SDK

Create your Vinkius account to connect Dotcom-Monitor to Vercel AI SDK 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 Vercel AI SDK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Map Global Latency Instantly

`list_monitoring_locations` lets your application map out active monitoring nodes across the globe. Your AI client reads this geographic registry to pinpoint exactly where user traffic faces the highest latency. Instead of waiting for a slow backend fetch, the Vercel AI SDK streams these location arrays directly into your frontend components. Users see live geographic performance metrics populate their dashboards block by block as the data arrives.

Stream Live Device History to Next.js

`get_device_monitoring_history` extracts raw historical performance logs for any target device. Your agent inspects these timestamps to diagnose intermittent connection drops or regional outages. Integrating this with your edge runtime means the AI streams status logs directly to your user interface. You don't have to build custom API polling logic because the Vercel AI SDK handles the data stream natively.

Inspect Server Health via MCP Server Tools

`get_device_details` pulls configuration details and current status metrics for any monitored endpoint. Your code exposes this tool to the agent, allowing it to inspect specific target configurations on demand. This MCP Server setup handles the authentication handshake behind the scenes so your client can query device lists instantly. Developers get a direct path from LLM reasoning to raw infrastructure health data without writing custom API wrappers.

Setup guide

Set up Dotcom-Monitor MCP in Vercel AI SDK

Prerequisites

Node.js 18+ and a TypeScript project
ai + @modelcontextprotocol/sdk packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies

Run npm install ai @modelcontextprotocol/sdk plus your preferred model provider (e.g. @ai-sdk/openai).
2

Create the Streamable HTTP transport

Use StreamableHTTPClientTransport with your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Discover and use tools

Call mcpClient.tools() to auto-discover all Dotcom-Monitor tools. Pass them directly to generateText() or streamText() — no manual schema definitions needed.
4

Works with any model provider

Swap openai("gpt-4o") for any AI SDK provider — Anthropic, Google, Mistral. The MCP tools work identically across all supported models.

index.ts

import { experimental_createMCPClient as createMCPClient } from "ai";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

const transport = new StreamableHTTPClientTransport(
  new URL("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
);

const mcpClient = await createMCPClient({ transport });
const tools = await mcpClient.tools();

const { text } = await generateText({
  model: openai("gpt-4o"),
  tools,
  prompt: "List recent Dotcom-Monitor transactions",
});

console.log(text);
await mcpClient.close();

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 Vercel AI SDK

Install the `@ai-sdk/mcp` package and initialize the client using the HTTP transport. Pass the output of `mcpClient.tools()` directly into your `generateText` or `streamText` calls to expose the monitoring tools to your agent.

Yes, this Dotcom-Monitor MCP integration runs perfectly inside Edge Functions because it relies on standard HTTP transport protocols. This ensures your AI agent can query device statuses with minimal cold-start times.

You should wrap your `streamText` call in standard try-catch blocks and ensure you call `mcpClient.close()` in a finally block. This prevents connection leaks and ensures your UI handles API timeouts gracefully.

Your agent queries `list_available_platforms` to check which monitoring environments exist in your account. This prevents the LLM from attempting to query metrics for unsupported device types.

This tool handles your Dotcom-Monitor API tokens, device lists, and historical uptime logs. All transactions run inside an ephemeral V8 sandbox, meaning your configuration keys never persist on Vinkius servers or leak to unauthorized clients.

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