meta-social-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FB_PAGE_ID | Yes | Facebook Page ID associated with the Instagram Business/Creator account. | |
| MCP_BEARER_TOKEN | No | Bearer token for authenticating remote HTTP MCP connector access (required when deploying as a web service). | |
| GRAPH_API_VERSION | No | Meta Graph API version to use. Update if requests start failing due to version deprecation. | |
| FB_PAGE_ACCESS_TOKEN | Yes | Facebook Page Access Token obtained via Graph API Explorer. Provides full access to the page and linked Instagram account. | |
| IG_BUSINESS_ACCOUNT_ID | Yes | Instagram Business Account ID linked to the Facebook page. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fb_create_text_postA | Publish a text post (optionally with a link) to the connected Facebook Page's feed. |
| fb_schedule_postA | Schedule a text post to publish on the Facebook Page at a future time (10 minutes to 6 months out). |
| fb_create_photo_postA | Publish a photo post to the Facebook Page from an image URL. |
| fb_create_video_postB | Upload and publish a video to the Facebook Page from a video URL. |
| fb_list_postsB | List recent posts from the Facebook Page. |
| fb_get_postB | Get details of a single Facebook post by ID. |
| fb_delete_postA | Permanently delete a post from the Facebook Page. This cannot be undone. |
| fb_get_commentsA | List comments on a Facebook post. |
| fb_reply_to_commentC | Reply to a comment on a Facebook post. |
| fb_get_page_insightsB | Get Facebook Page insight metrics (e.g. page_impressions, page_engaged_users, page_fans). |
| ig_publish_photoB | Publish a single photo to the connected Instagram Business account. |
| ig_publish_videoB | Publish a video to the connected Instagram account as a Reel, feed video, or Story. |
| ig_publish_carouselB | Publish a multi-image carousel post (2-10 images) to Instagram. |
| ig_get_account_infoB | Get profile info for the connected Instagram account. |
| ig_list_mediaB | List recent media posts from the connected Instagram account. |
| ig_get_media_insightsA | Get insight metrics for a specific Instagram media item (e.g. reach, likes, comments, saved). |
| ig_get_commentsC | List comments on an Instagram media item. |
| ig_reply_to_commentC | Reply to a comment on an Instagram media item. |
| ig_get_account_insightsB | Get account-level Instagram insight metrics (e.g. reach, impressions, profile_views). |
| graph_api_requestA | Advanced/escape hatch: make a raw call to any Meta Graph API endpoint with the configured access token. Use this for anything the other tools don't cover yet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Every tool is clearly scoped to a specific platform and action, with fb_ and ig_ prefixes separating Facebook from Instagram. Within each platform, actions like create, schedule, list, get, delete, and reply are distinct and unlikely to be confused.
All tools use snake_case with platform prefixes, but there is a minor inconsistency: Facebook uses 'create' for publishing posts while Instagram uses 'publish'. This is a small deviation from a fully consistent verb_noun pattern.
20 tools is on the higher side but appropriate for a server covering two distinct social platforms with posts, comments, and insights. Each tool earns its place, and the dual-platform scope justifies the count.
Core workflows are well-covered: create/schedule/list/get/delete posts, comments, and insights for Facebook; publish media and retrieve insights for Instagram. Missing update operations and Instagram deletion are minor gaps, and the graph_api_request escape hatch covers edge cases.