Skip to main content
Glama
Sign In
facebook-mcp

facebook-mcp

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to facebook-mcp

No user-submitted related servers found.

    Related Servers

    • facebook-pages-mcp

      lanternrow
      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
      74 npm
      MIT

    • Facebook MCP Server

      tiroshanm
      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
      77
      -

    • mcp-facebook

      lmtNoLimit
      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
      11 npm
      MIT

    • meta-mcp-server

      N-Graves
      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
      8 npm
      MIT

    • io.github.anthonyjbolo/mcp-fb

      anthonyjbolo
      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
      14 PyPI
      MIT

    • meta-business-insights-mcp

      mediacraft-cc
      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
      -
    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.9/5.0

    Scored across 53 tools

    Disambiguation4/5

    Tools cover many distinct Facebook Page resources, and descriptions explicitly cross-reference alternatives such as post vs. reel vs. story and page vs. post vs. reel insights, so selection is usually clear. A few clusters—create_post/create_photo_post/create_video_post/create_reel and the several insights/report tools—require close reading but remain separable.

    Naming Consistency4/5

    All names use snake_case with a consistent facebook_ prefix and are mostly verb_noun (list_posts, create_comment, delete_label). Deviations like whoami, usage, page_insights, private_reply, and get_activity_since keep it from perfect consistency but remain readable.

    Tool Count2/5

    53 tools is far beyond the typical 3–15 range and is very heavy for any single server, even a broad Facebook Page management domain. Many tools map to real Graph endpoints, but the surface is large enough to impose high selection cost and would benefit from consolidation.

    Completeness3/5

    Core lifecycles for posts, comments, labels, saved replies, and messaging are well covered, with read/create/update/delete in several areas. However, media lifecycle is incomplete—no delete/update for photos, videos, albums, or stories, and no general video listing beyond Reels—so agents will hit dead ends for media management.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources