Koskamo

OneUptime MCP

The OneUptime MCP server is a built-in component of every OneUptime instance that allows AI assistants to interact directly with the platform. It enables agents to manage monitors, handle incident response, acknowledge alerts, configure on-call policies, manage status pages, and query telemetry data such as logs and metrics using the Model Context Protocol.

Visit OneUptime

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

OneUptime MCP logo, by OneUptimeVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-10-26Operated by OneUptime
MCP endpoint (Streamable HTTP)
https://oneuptime.com/mcp
Vendor documentation

What you can do with it

  • Create and configure monitors to track service health
  • Acknowledge, resolve, and add notes to incidents
  • Query logs, metrics, and traces for debugging
  • Manage on-call schedules and alert policies

Source and maintenance

Vendor evidenceRegistry 14.0.98
mcp-registry: com.oneuptime/mcp@14.0.98Source repositoryProject website
Last repository push
Latest release
14.0.98
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · repository · passed · metadata changed · unchanged
  • · repository · passed · metadata changed · updated
  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http oneuptime-mcp https://oneuptime.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add oneuptime-mcp --url https://oneuptime.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable oneuptime-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "oneuptime-mcp": {
      "url": "https://oneuptime.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "oneuptime-mcp": {
      "type": "streamableHttp",
      "url": "https://oneuptime.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start oneuptime-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "oneuptime-mcp": {
      "type": "http",
      "url": "https://oneuptime.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http oneuptime-mcp https://oneuptime.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "oneuptime-mcp": {
      "url": "https://oneuptime.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "oneuptime-mcp": {
      "serverUrl": "https://oneuptime.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like OneUptime MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 298

Do you run OneUptime MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing