Skip to main content
Glama
eonik-ai

eonik-mcp

Official
by eonik-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to eonik-mcp

No user-submitted related servers found.

    Related Servers

    • PaidSync MCP Server by PaidSync

      PaidSync MCP Serverofficial

      PaidSync
      A
      license
      Not graded
      quality
      F
      maintenance
      Connects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.
      MIT
    • Spytrend MCP Server by Spytrend

      Spytrend MCP Serverofficial

      Spytrend
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search and retrieve Meta and TikTok advertising intelligence — ads, creatives, advertisers, the accounts behind them, destinations and rankings — through a hosted, browser-authenticated endpoint with no installation or API key. Supports full record lookups, similarity and trend queries, favorite folders, plus ready-made skills and recipes for competitive ad research.
      21
      MIT

    • Ads MCP

      amekala
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      103
      MIT

    • simba-mcp

      fritsferdiansyah38-EOS
      -
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to marketing mix models, enabling natural language data upload, performance modeling, budget optimization, and scenario testing.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 32 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources