Oh Dear MCP server

What the model can do

Oh Dear website monitoring: monitors and which checks are failing, uptime percentages, downtime periods, check run history, certificate health, broken links, maintenance windows, and status pages with their updates; when you ask, can post, edit or delete a status page update, start, stop, schedule or delete maintenance, run a check now, snooze, unsnooze, enable or disable a check, and add or delete a monitor.

Reads

• ohdear_list_monitorsOh Dear monitors: label, URL, type, group, tags, overall result (succeeded, warning, failed…) and which checks are not passing with their summary…
• ohdear_get_monitorOne Oh Dear monitor in full: every check with its id (the actions need it), result, summary, average response time and any snooze…
• ohdear_uptimeUptime percentages of an Oh Dear monitor per hour, day or month over a period, with the average.
• ohdear_downtimeDowntime periods of an Oh Dear monitor: when each started and ended, how many minutes, and any notes, with the total.
• ohdear_check_runsRecent runs of one kind of check on an Oh Dear monitor (kept about ten days): result, start and end, and a link to the report.
• ohdear_certificate_healthCertificate health of an Oh Dear monitor from its latest run (or a given run): issuer, valid from and until, days left…
• ohdear_broken_linksBroken links Oh Dear found on a monitored site in its latest crawl (or a given run): the broken URL, its status code or error…
• ohdear_status_pagesOh Dear status pages (title, public URL, overall status, which monitors they show), or with status_page_id the updates posted on one: title…

Acts, when you ask

These change something in Oh Dear. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• ohdear_post_status_updatePosts an update on an Oh Dear status page, visible to the public at once (whether its subscribers are emailed is not documented).
• ohdear_edit_status_updateChanges a public Oh Dear status page update: its title and severity (both required by Oh Dear, so pass the current ones to keep them), text…
• ohdear_delete_status_updatePermanently deletes an update from a public Oh Dear status page.
• ohdear_start_maintenancePuts an Oh Dear monitor into maintenance now, silencing its alerts for the given minutes (default 60).
• ohdear_stop_maintenanceEnds any maintenance running on an Oh Dear monitor now, so its alerts resume.
• ohdear_schedule_maintenanceSchedules a maintenance window on an Oh Dear monitor, during which its alerts are silenced.
• ohdear_delete_maintenanceDeletes a scheduled Oh Dear maintenance window, so alerts are not silenced then.
• ohdear_run_checkAsks Oh Dear to run one check now rather than at its next scheduled time; if it fails, the team's alerts go out as usual.
• ohdear_snooze_checkSnoozes an Oh Dear check's notifications for the given minutes; problems are still recorded but nobody is alerted.
• ohdear_unsnooze_checkRemoves a snooze from an Oh Dear check, so its notifications go out again.
• ohdear_set_check_enabledEnables or disables one Oh Dear check on a monitor.
• ohdear_add_monitorAdds a monitor to an Oh Dear team, counting against the plan's monitor allowance (which may cost money).
• ohdear_delete_monitorPermanently deletes an Oh Dear monitor with all its checks and history; the site is no longer watched.

Connect it

First connect Oh Dear on Dashboard → Connections, then add Memtro to your client once. The Oh Dear tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Oh Dear connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which monitors have failing checks right now?
• › What was the shop's uptime last month?
• › Which certificates expire in the next 30 days?
• › What broken links did the last crawl find on our docs site?
• › Put the main website into maintenance for 30 minutes.

Questions

Is this an official Oh Dear MCP server?

No. It is Memtro's MCP server with Memtro's Oh Dear connector behind it: the connector reads Oh Dear through its API with the credentials you connect on Dashboard → Connections, and Oh Dear publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Oh Dear?

Only when you ask, and only what it has been granted: post an update on a public status page; edit a status page update; delete a status page update; start maintenance on a monitor now; stop maintenance on a monitor; schedule a maintenance window; delete a scheduled maintenance window; run a check now; snooze a check's notifications; unsnooze a check; enable or disable a check; add a monitor; delete a monitor. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server