Skip to main content
Glama
oliverames

Meta MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Meta MCP Server

No user-submitted related servers found.

    Related Servers

    • Open MCP Servers

      open-work-org
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to self-host MCP connectors for managing Meta platforms such as Facebook Pages, Instagram, Threads, Ads Manager, and Commerce, with tools for publishing, engagement, analytics, ad campaigns, and competitor research.
      200
      166 npm
      MIT

    • Meta Marketing API MCP Server

      Pythonando
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Facebook and Instagram advertising data through the Meta Marketing API. It supports full campaign lifecycle management, performance analytics, audience targeting, and creative optimization.
      1,242 npm
      MIT

    • meta-mcp

      exileum
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage Instagram and Threads accounts — publish content, handle comments, view insights, search hashtags, and manage DMs through the Meta Graph API.
      59
      13 npm
      12
      MIT

    • Meta Marketing API MCP Server

      brijr
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Facebook and Instagram advertising via the Meta Marketing API. It provides comprehensive tools for campaign lifecycle management, performance analytics, audience targeting, and creative optimization.
      18 npm
      200
      MIT

    • ,

      Lightning-Products
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage Facebook and Instagram advertising campaigns through the Meta Marketing API. Supports full campaign lifecycle management, performance analytics, audience targeting, and creative optimization.
      -
    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

    B3.1/5.0

    Scored across 200 tools

    Disambiguation4/5

    Most tools target a distinct resource-and-action combination, and descriptions clearly separate lookalikes such as page feed posts vs. published posts vs. visitor posts, or page insights vs. post insights vs. campaign insights. A few boundaries are fuzzy — particularly create/publish and get/list variants — but an agent can usually disambiguate with the provided descriptions.

    Naming Consistency3/5

    The dominant meta_verb_noun pattern is readable, but conventions are mixed: collection retrieval uses both get and list (meta_get_posts vs. meta_list_campaigns), content publishing uses both create and publish (meta_create_post vs. meta_publish_instagram_photo), and Threads tools use a separate threads_ prefix. These deviations are widespread enough to make naming somewhat inconsistent.

    Tool Count1/5

    200 tools is an extreme mismatch for an MCP server. Even though the server spans Pages, Instagram, Ads, Threads, product catalogs, pixels, audiences, and more, this surfaces far too much surface area for an agent to navigate effectively.

    Completeness4/5

    The tool surface is impressively comprehensive, covering CRUD-like workflows for posts, ads, audiences, pixels, products, Instagram media, Threads posts, and more. Minor gaps remain — such as no event update/delete, no ad creative update/delete, and no catalog create/delete — but agents can usually accomplish their goals without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources