Google Ads vs MCP Uptime Kuma

A side-by-side look at the Google Ads and MCP Uptime Kuma MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

G
Google AdsMonitoring
Google Ads MCP server — manage campaigns, keywords, and metrics.36FairAuth: not declared
MCP Uptime Kuma logoMCP Uptime KumaMonitoring · Local subprocess (stdio)A Model Context Protocol (MCP) server for Uptime Kuma version 2.63GoodAuth: other

Verdict: choose Google Ads for monitoring work; choose MCP Uptime Kuma for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

G
Choose Google Ads when

  • You need dedicated capabilities in the Monitoring domain.
Explore Google Ads

MCP Uptime Kuma logoChoose MCP Uptime Kuma when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
  • You want tools like getMonitorSummary, listMonitors, listMonitorTypes.
Explore MCP Uptime Kuma

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
G
Google Ads
MCP Uptime Kuma logoMCP Uptime Kuma
CategoryMonitoringMonitoring
Quality signal36/100 · Fair63/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedUPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS
Verified ownerCommunity listingCommunity listing
GitHub stars—60
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed26

Tools & capabilities

Google Ads tools

No tool names declared yet. Check the project README from the listing page.

MCP Uptime Kuma tools 26

  • getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.
  • listMonitorsGet the full list of all monitors with configurations. Supports filtering.
  • listMonitorTypesGet all available monitor types supported by Uptime Kuma.
  • getMonitorGet detailed configuration for a specific monitor by ID.
  • createMonitorCreate a new monitor (requires name and type at minimum).
  • updateMonitorUpdate an existing monitor's configuration.
  • deleteMonitorPermanently delete a monitor and all its heartbeat history.
  • pauseMonitorPause a monitor to stop performing checks.
  • resumeMonitorResume a paused monitor to restart checks.
  • listHeartbeatsGet status check history for all monitors.
  • getHeartbeatsGet status check history for a specific monitor.
  • listNotificationsList all configured notification channels (Slack, Discord, email, webhooks, etc.).
  • +14 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Google Ads

No confirmed install command for Google Ads yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Uptime Kuma

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "@davidfuchs/mcp-uptime-kuma@latest"
      ],
      "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"
      }
    }
  }
}

Frequently asked questions

Google Ads is categorized under Monitoring and uses an install path we have not confirmed yet. MCP Uptime Kuma belongs to Monitoring and uses a local stdio subprocess. Pick Google Ads for monitoring work and MCP Uptime Kuma for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Google Ads has no confirmed install command yet — follow its own setup instructions.

Google Ads has no declared pricing — check the project's own site. MCP Uptime Kuma is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add google-ads-3 and mcp-uptime-kuma as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Ads has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Uptime Kuma has 63/100 (Good) with 5 views, 0 installs and 60 GitHub stars.