Skip to main content
Glama
EfrainTorres

ArmaVita Meta Ads MCP

by EfrainTorres

Related Servers

Alternatives to ArmaVita Meta Ads MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Python MCP server that exposes Meta Marketing API data, providing tools to manage ad accounts, campaigns, and analytics through natural language interfaces.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server to manage Meta Ads (Facebook/Instagram) campaigns, ad sets, insights, and audiences from Claude Code using natural language.
      9
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Meta Ads providing 30 tools for account discovery, campaign management, targeting research, and insights. Designed with LLM-friendly outputs and productivity features like cloning and bulk operations.
      1
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Local MCP server for operating Instagram, Meta Ads, and Facebook Page from Claude Code via Meta's Graph API. Provides 20 tools for publishing, campaign management, and insights.
      20
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted Model Context Protocol (MCP) server that gives AI agents secure, multi-tenant access to the Meta Marketing API for Facebook Ads and Instagram Ads. It enables campaign management, audience targeting, insights, lead management, and more across multiple ad accounts.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that allows AI models to access, analyze, and manage Meta advertising campaigns, enabling LLMs to retrieve performance data, visualize ad creatives, and provide strategic insights for Facebook and Instagram platforms.
      37
      1,266
      Business Source 1.1

    TDQS

    C2.4/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools are clearly distinct, targeting specific resources like ads, creatives, ad sets, campaigns, and targeting categories. However, some tools like 'search_web_content' and 'read_web_content' have ambiguous boundaries with other search/read tools, and 'create_report' overlaps in purpose with 'list_insights' for performance data, which could cause mild confusion.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_ad', 'list_campaigns', 'read_ad_account', 'update_ad_set', 'search_interests', and 'clone_ad_creative'. There are no deviations in naming conventions, making the set predictable and easy to parse.

    Tool Count2/5

    With 40 tools, the count is excessive for the apparent scope of Meta Ads management. This many tools can overwhelm agents and increase complexity, as typical well-scoped servers have 3-15 tools. It suggests over-fragmentation of operations that could be consolidated.

    Completeness5/5

    The tool surface provides comprehensive coverage for the Meta Ads domain, including full CRUD operations for ads, creatives, ad sets, and campaigns, along with reporting, audience estimation, targeting searches, and asset management. There are no obvious gaps, enabling agents to handle complete workflows without dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues