Log inSubmit server

AdAdvisor MCP Server vs Monitor

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

A
AdAdvisor MCP ServerMonitoringQuery Meta Ads performance data — accounts, campaigns, ad sets, ads, metrics & settings.37FairAuth: not declaredMonitor 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 required

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

Which MCP server should you choose?

A
Choose AdAdvisor MCP Server when

  • You need dedicated capabilities in the Monitoring domain.
Explore AdAdvisor MCP Server

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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
AdAdvisor MCP Server		Monitor logoMonitor
CategoryMonitoringMonitoring
Quality signal37/100 · Fair64/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—1,309
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView AdAdvisor MCP Server View Monitor

Tools & capabilities

AdAdvisor MCP Server tools

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

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.

AdAdvisor MCP Server

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

Monitor

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

Frequently asked questions

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

AdAdvisor MCP Server has no declared pricing — check the project's own site. Monitor is listed as freemium — a free tier with paid plans. Auth: api key required. 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 adadvisor-mcp-server and betterdb-inc-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AdAdvisor MCP Server has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Monitor has 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars.

Popular comparisons with AdAdvisor MCP Server

Popular comparisons with Monitor