If you already use Claude Desktop, you can skip the dashboard entirely for routine monitoring tasks. Connect it once, and you can create monitors, check status, and read incident history just by asking.

This walkthrough takes about two minutes and needs a free Baromio account, no credit card required.

What you'll need

• A Baromio account (the Free plan works fine for this)
• Claude Desktop, updated to a version with connector support

Step 1: Connect Claude Desktop to Baromio

1. Open Claude Desktop and go to Settings → Integrations.
2. Click Add Integration and paste in the Baromio MCP server URL:

https://baromio.io/mcp

3. Claude opens a browser window. Log in to Baromio and click Authorize.
4. Back in Claude Desktop, ask: List my Baromio monitors. If you're on a fresh account, Claude will tell you the list is empty, that's expected, and confirms the connection works.

No API key, no config file editing. Claude Desktop handles the OAuth flow for you.

Step 2: Create a monitor by describing it

This is where it gets interesting. With a Free or paid plan, ask Claude something like:

You: Monitor https://example.com and check it every 5 minutes. Alert me if it's down for more than a minute.

Claude: I'll set that up now.

[Claude calls the create-monitor tool]

Claude: Done, I've created an HTTP monitor for https://example.com, checking every 5 minutes with a 1-check alert threshold. You'll get an email if it goes down.

That's the entire setup. No form, no dashboard click-through, Claude read your intent, filled in the monitor type, interval, and alert threshold, and created it via the same API the dashboard uses.

Step 3: Ask about status in plain language

Once you have monitors running, you can query them conversationally instead of opening the dashboard:

You: What's my uptime been like this week?

Claude: [calls get-uptime-stats] Your monitors are averaging 99.97% uptime over the past 7 days. example.com had one incident on Tuesday, 4 minutes of downtime, since resolved.

You: Why did that incident happen?

Claude: [calls get-monitor-incidents, reads the AI-generated diagnosis] The incident on example.com was a connection timeout, most likely caused by a deploy that briefly took the server down. It self-resolved after 4 minutes with no further occurrences.

What write access unlocks

Everything above works on the Free plan with read-only access. Upgrade to Pro or Business and Claude can also pause monitors, update check intervals, or delete monitors you no longer need, useful when you're doing maintenance and want to say "pause the staging monitor for an hour" instead of finding it in a list.

Full reference

This walkthrough covers the common path. For the complete tool list, token types, and troubleshooting, see the AI Agents & MCP documentation.

Note: the conversation snippets above show real tool calls and real response shapes, condensed for readability, not a verbatim transcript of a single session.