In-depth architectural comparison of the Lucidity Mcp and ZuckerBot — Meta Ads MCP Server 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
Lucidity Mcp
Monitoring · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
ZuckerBot — Meta Ads MCP Server
Monitoring · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lucidity Mcp if you need specialized Monitoring tools running via a hosted cloud SSE transport. Choose ZuckerBot — Meta Ads MCP Server if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lucidity Mcp when:
You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
The root directory of the workspace/git repository
path
Optional specific file path to analyze
ZuckerBot — Meta Ads MCP Server Tools (47)
audit_account
Full read-only account audit: wasted spend, creative fatigue, opportunity score (0-100), projected CPL improvement, prioritised action items. Available on every tier — the recommended first call
redeem_license
Redeem a lifetime licence code (Dealify/AppSumo) and upgrade all API keys on the account
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).
Lucidity Mcp is categorized under Monitoring and uses a remote streaming HTTP/SSE transport. In contrast, ZuckerBot — Meta Ads MCP Server belongs to Monitoring using local stdio subprocess. Select Lucidity Mcp when you need capabilities focused on monitoring and ZuckerBot — Meta Ads MCP Server when you require tools for monitoring.