What is the key difference between MCP Uptime Kuma and Tá Rodando?

MCP Uptime Kuma belongs to the Monitoring category with local stdio execution, while Tá Rodando belongs to the Monitoring category with cloud HTTP/SSE execution.

How do I install MCP Uptime Kuma or Tá Rodando in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Uptime Kuma and Tá Rodando free or paid?

MCP Uptime Kuma operates under a Free / Open Source model (No auth required). Tá Rodando operates under a Freemium model (OAuth 2.0).

Which MCP server has more tools and community activity?

MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars. Tá Rodando lists 0 tools with 0 views and 0 GitHub stars.

Can I use both MCP Uptime Kuma and Tá Rodando together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Uptime Kuma vs Tá Rodando

In-depth architectural comparison of the MCP Uptime Kuma and Tá Rodando MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Uptime Kuma

Monitoring · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Tá Rodando

Monitoring · Remote HTTP/SSE

Quality: 51/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose MCP Uptime Kuma if you need specialized Monitoring tools running via a local process. Choose Tá Rodando if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Uptime Kuma when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
Primary tools included: getMonitorSummary, listMonitors, listMonitorTypes.

Explore MCP Uptime Kuma Details

Choose Tá Rodando when:

You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).

Explore Tá Rodando Details

Feature & Specification Comparison

Specification	MCP Uptime Kuma Monitoring	T Tá Rodando Monitoring
Summary	A Model Context Protocol (MCP) server for Uptime Kuma version 2.	Remote MCP server for Tá Rodando, uptime monitoring and public status page from Brazil. Create HTTP monitors, check what is down, wire alert channels (Telegram, Slack, Discord, Google Chat, email) and manage the status page and incidents from chat. Streamable HTTP with OAuth (dynamic client registration) or API key. Free plan: 3 monitors every 5 min.
Category & Scope	Monitoring

Tools & Capabilities Breakdown

MCP Uptime Kuma Tools (22)

getMonitorSummary

Get a quick overview of all monitors with their current status. Supports filtering.

listMonitors

Get the full list of all monitors with configurations. Supports filtering.

listMonitorTypes

Get all available monitor types supported by Uptime Kuma.

getMonitor

Get detailed configuration for a specific monitor by ID.

createMonitor

Create a new monitor (requires name and type at minimum).

updateMonitor

Update an existing monitor's configuration.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Uptime Kuma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@davidfuchs/mcp-uptime-kuma",
        "mcp-uptime-kuma-get-jwt"
      ],
      "env": {
        "UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
        "UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
        "UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
        "UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
        "UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
        "UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
      }
    }
  }
}

Tá Rodando Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "t-rodando": {
      "command": "npx",
      "args": [
        "-y",
        "t-rodando"
      ]
    }
  }
}

Frequently Asked Questions

MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. In contrast, Tá Rodando belongs to Monitoring using remote streaming HTTP/SSE transport. Select MCP Uptime Kuma when you need capabilities focused on monitoring and Tá Rodando when you require tools for monitoring.