Skip to main content
Glama
lanternrow

facebook-pages-mcp

by lanternrow

Related Servers

Alternatives to facebook-pages-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A TypeScript MCP server for the Meta Graph API focused on Facebook Pages, enabling publishing, reading, insights, and moderation tasks.
      30
      31 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing organic Facebook Page content: create and schedule posts, read posts and comments, view page insights, and delete posts.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for organic Instagram analytics via the Meta Graph API, providing read-only tools for profiles, media, insights, audience, and optional publishing.
      GPL 3.0
    • F
      license
      A
      quality
      B
      maintenance
      MCP server for reading Meta Business (Facebook Pages and Instagram) data via Graph API, with cross-account portfolio aggregation to answer questions about follower growth, page insights, and metrics. It runs as a stdio or HTTP server for Claude Desktop.
      9
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server to safely publish posts to multiple Facebook Pages via Meta Graph API, with built-in guardrails for brand voice, banned topics, image requirements, and anti-duplication.
      4
      MIT

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tool purposes are mostly distinct, but 'get_published_posts' and 'get_page_feed' both retrieve posts with the difference being inclusion of visitor posts. While descriptions clarify, they could cause confusion. Similarly, separate insight tools for page, post, and video are clear. Overall minor overlap.

    Naming Consistency3/5

    Most tools use 'get_' prefix, but 'create_post' and 'refresh_token_info' use different verbs. Among 'get_', suffixes vary between 'info', 'insights', 'posts', 'comments', 'feed', without a strict pattern. This mixed convention is noticeable but still understandable.

    Tool Count5/5

    9 tools is appropriate for a Facebook Pages API covering essential operations: page info, insights, post retrieval (two flavors), post interactions, video analytics, post creation, and token management. Neither too few nor too many.

    Completeness3/5

    The tool set covers reading page data, posts, comments, and insights, and creating posts. However, it lacks update and delete operations for posts, comment management beyond reading, and other page management features. These gaps are notable for a complete page management surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues