An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Hyperdx Open Source Observability to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Debug infrastructure and manage alerts without leaving your IDE.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 7 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 7 available through HyperDX.

  1. 01

    Get dashboard

    This capability pulls the specific details and configuration for a single dashboard.

  2. 02

    List events

    Use this to pull structured logs or spans from HyperDX using query filters.

  3. 03

    List logs

    This capability retrieves a list of logs based on your specific search criteria like service name or error level.

  4. 04

    Create alert

    Use this to set up a new alert rule within your HyperDX instance.

Capability set02 / 02

05-07

3 capabilities in this set.

Part of 7 available through HyperDX.

  1. 05

    Delete alert

    This capability removes an existing alert rule using its unique ID.

  2. 06

    List alerts

    This capability returns a full list of all alert rules currently configured in your organization.

  3. 07

    List dashboards

    Use this to see all the dashboards available in your HyperDX organization.

Real work

What teams actually run

01

Rapid Debugging

Ask your agent to find all error logs for a specific service immediately after a deployment.

02

Incident Investigation

Use the agent to correlate recent error spikes with specific dashboard trends.

03

Alert Configuration

Tell your agent to set up a new monitoring rule when you notice a new pattern of failures.

04

System Health Checks

Quickly pull a list of all active alerts to see if any thresholds were recently breached.

Automate a task

Put HyperDX to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

HyperDX works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put HyperDX to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

938ms average. Fast in production.

HyperDX is checked daily against the live service.

Daily averagePeak 1549ms
Oct 3Today
Fastest day
728ms
Slowest day
1549ms
14-day trend
Stable+3%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 7 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of HyperDX, so you can see the experience inside your AI.

It does not authenticate your account with HyperDX. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

HyperDX Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_lc01BEQeS86qzu5Tsala3mRU7FKVPIY7tYMD90oU/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — HyperDX capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "hyperdx-open-source-observability-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_lc01BEQeS86qzu5Tsala3mRU7FKVPIY7tYMD90oU/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up HyperDX in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work HyperDX owners hand off.

This MCP is built for technical teams who need to bridge the gap between their code and their telemetry data.

  • 01

    DevOps Engineers

    They use the agent to check error rates and system logs without opening a browser.

  • 02

    SREs

    They manage alert thresholds and investigate incidents through a chat interface.

  • 03

    Developers

    They fetch specific logs or trace IDs while staying focused on writing code.

FAQ

Questions HyperDX owners ask.

  • 01

    How do I connect HyperDX to my AI client?

    You subscribe to the MCP on Vinkius and enter your HyperDX API Key. Once connected, you can use it immediately in any compatible client like Cursor or Claude.

  • 02

    Which AI clients can use this MCP?

    This MCP works with any client that supports the Model Context Protocol, including Claude, Cursor, and Windsurf.

  • 03

    Can I create alerts using my AI agent?

    Yes, you can use the create_alert capability to set up new alert rules through your agent.

  • 04

    Do I need to host the MCP myself?

    No, Vinkius hosts and manages the MCP for you, so it is ready to use as soon as you connect.

  • 05

    Can I filter logs by specific services?

    Yes, you can use query parameters like 'service:auth' or 'level:error' to filter logs via your agent.

  • 06

    Can I search for specific errors in my logs using this server?

    Yes! Use the list_logs capability with a query like level:error. You can also specify a time range using the from parameter (e.g., '1h' or '24h') to narrow down the results.

  • 07

    How do I set up a new alert for a specific service?

    You can use the create_alert capability. You'll need to provide a name, the search query (e.g., service:auth level:error), a threshold value, the type of alert (like 'count'), and the evaluation interval (e.g., '5m').

  • 08

    Is it possible to delete an alert rule if it's no longer needed?

    Yes, simply use the delete_alert capability and provide the unique ID of the alert rule you wish to remove.

Explore

More in Devops Cicd

Suggestions

Connect HyperDX to Claude, Cursor, ChatGPT & more