eonik-mcp
OfficialRelated Servers
Alternatives to eonik-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query advertising spend, ROAS, campaigns, pacing and anomalies across many ad, analytics and commerce platforms, and to make approval-first changes such as pausing campaigns or adjusting budgets after a preview.1Apache 2.0- AlicenseAqualityBmaintenanceEnables AI apps such as Claude, ChatGPT, Cursor and Codex to create and edit campaigns, ad groups and ads, look up targeting values, upload images and videos, and read spend, lead and engagement reports from a connected ad account. Every change is saved as a draft that only goes live once the user approves it.5MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to a hosted motion-design studio that turns a product URL or brief into editable storyboard-based video ads, with quotes for paid steps approved before credits are spent.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants and agents to read analytics and manage advertising across Google Ads, Google Analytics 4, and Meta Ads through natural language, with preview-confirm guardrails and configurable account and budget limits.21MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to 27 marketing and analytics platforms, enabling read-only access to data, built-in tracking audits, and KPI context for informed answers.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceConnects the AI assistant a business already uses to its Google Ads, social accounts, Shopify store, inventory and a phone line, so it can create campaigns, publish and schedule posts, manage products and orders, and place or answer calls. Ad spend and other writes are held behind an owner approval gate, and each connection is limited to the workspaces and permissions the user grants.MIT
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.