eonik-mcp
OfficialRelated Servers
Alternatives to eonik-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityFmaintenanceConnects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, analyze, and optimize ad campaigns across Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Amazon Ads, and ChatGPT Ads through natural language using 400+ tools.96MIT
- -licenseNot gradedqualityBmaintenanceConnects AI assistants to marketing mix models, enabling natural language data upload, performance modeling, budget optimization, and scenario testing.-

Presso MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceConnects e-commerce and marketing data sources like Shopify, GA4, Google Ads, and Meta Ads to AI assistants, enabling natural language queries about store performance, ad campaigns, and customer behavior.9 npm2MIT
PaidSync MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, manage, and optimize advertising campaigns across 14 ad and measurement platforms through a single MCP endpoint, with over 530 executable tools.3MIT- FlicenseNot gradedqualityBmaintenanceConnects AI assistants to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads so users can query live campaign performance, budgets and audiences in the account's own currency and prepare changes as proposals that only take effect after explicit approval. Reads run immediately, while every write is staged as an approvable proposal with before/after values, and newly created campaigns, ad sets and ads start paused.1-
TDQS
Scored across 32 tools
Several tools cluster around overlapping concepts: brand/marketer memory (get_brand_context, get_context_ledger, get_brand_briefing, get_account_memory, remember, recall) and competitor/ad reads (get_watch_activity, get_my_competitor_ads, get_competitor_assets, get_competitor_timeline). The descriptions include explicit routing hints and many tools are genuinely distinct, but an agent could easily select the wrong one in these clusters.
The set is dominated by a get_* + resource pattern, with consistent save_* groups and the list_my_ads/sync_my_ads pair. Deviations like remember, recall, lookup_ad_performance, probe_asset_duration, and deconstruct_ad break the pattern, but the naming remains readable and mostly predictable.
With 32 tools, the surface exceeds the 25+ too-many threshold, and the count feels inflated by a deprecated duplicate (generate_creative_brief) and several overlapping memory/context tools. The server's scope is broad, but the tool set is heavier than its core workflows require.
Core read, search, sync, save, and deconstruction workflows are well covered. However, the write-side lifecycle is thin: there is no tool to update or delete saved context/plans/truths, no competitor-watch management, and the deprecated brief-generation flow leaves no way to persist an authored brief, creating notable dead ends.