Skip to main content
Glama
IvanBBaev

facebook-mcp

by IvanBBaev

Related Servers

Alternatives to facebook-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Facebook Pages organic analytics and management using Meta Graph API v25.0. Enables AI assistants to read page insights, posts, comments, and publish content via natural language.
      9
      51 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server implementation that provides Facebook Page interaction and management capabilities. This server enables automated posting, comment moderation, and content retrieval.
      7
      76
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Facebook Pages that allows creating, scheduling, and deleting posts, managing comments, and retrieving Page insights using the Facebook Graph API.
      8
      1 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP-based interaction with the Meta Graph API for Facebook Pages and linked Instagram Business accounts, including posting, commenting, and reading page details.
      6
      11 npm
      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
    • 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
      -

    TDQS

    A4.1/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, with clear separation between posts, reels, videos, insights, comments, and Messenger conversations. A few pairs could be confused—create_post vs create_photo_post, and create_video_post vs create_reel—but the descriptions draw explicit boundaries.

    Naming Consistency4/5

    The overwhelming pattern is facebook_<verb>_<noun> with snake_case throughout, and the insights tools follow a consistent object_insights shape. Minor deviations like facebook_whoami and facebook_usage are understandable utilities rather than naming chaos.

    Tool Count2/5

    At 30 tools, the server exceeds the comfortable 3-15 tool range and crosses the 'too many' threshold for a single MCP server. Each tool has a legitimate purpose and the surface is coherent, but the count is heavy enough that agents will need careful navigation.

    Completeness4/5

    The main Page workflows are well covered: posts have create/read/update/delete plus scheduling, comments have full moderation lifecycle, and messaging has list/read/send. Minor gaps remain—no video update/delete path, no conversation mark-as-seen, and no way to edit a comment—but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive