Monitor vs World Monitor

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

Monitor logoMonitorMonitoring · Local subprocess (stdio)Valkey-first observability with Redis compatibility. Query real-time metrics, analyze slow commands, detect hot keys, and investigate performance issues directly from AI coding assistants.64GoodAuth: api key requiredWorld Monitor logoWorld MonitorMonitoringLive global intelligence: real-time markets, conflicts, country risk, chokepoints, energy. 39 tools.45FairAuth: other

Verdict: choose Monitor for monitoring work as a local process; choose World Monitor for monitoring. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Monitor logoChoose Monitor when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Monitor

World Monitor logoChoose World Monitor when

  • You need dedicated capabilities in the Monitoring domain.
  • Its auth model fits you: other.
Explore World Monitor

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMonitor logoMonitorWorld Monitor logoWorld Monitor
CategoryMonitoringMonitoring
Quality signal64/100 · Good45/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredother
PricingFreemiumFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,30989,218
Directory activity 5 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Monitor tools

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

World Monitor tools

No tool names declared yet. Check the project README from 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.

Monitor

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "betterdb-inc-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@betterdb/monitor"
      ]
    }
  }
}

World Monitor

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

Frequently asked questions

Monitor is categorized under Monitoring and uses a local stdio subprocess. World Monitor belongs to Monitoring and uses an install path we have not confirmed yet. Pick Monitor for monitoring work and World Monitor 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. World Monitor has no confirmed install command yet — follow its own setup instructions.

Monitor is listed as freemium — a free tier with paid plans. Auth: api key required. World Monitor 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 betterdb-inc-monitor and world-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Monitor has a quality signal of 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars. World Monitor has 45/100 (Fair) with 5 views, 0 installs and 89,218 GitHub stars.