meta-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| META_PAGE_ID | No | The ID of the Facebook Page. Optional; defaults the arguments. | |
| MCP_READ_ONLY | No | Set to 1 to refuse anything that changes state. | |
| META_IG_USER_ID | No | The ID of the linked Instagram Business account. Optional; defaults the arguments. | |
| MCP_NO_DESTRUCTIVE | No | Set to 1 to allow posting, refuse the generic caller. | |
| META_IG_ACCESS_TOKEN | No | Instagram access token. Optional; defaults to the Page token, which is correct when the Instagram account is linked to that Page. | |
| META_PAGE_ACCESS_TOKEN | Yes | Your Facebook Page access token. Used to authenticate requests to the Meta Graph API. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meta_get_pageC | A Facebook Page's own details. |
| meta_create_page_postA | Post to a Facebook Page. Immediately public — there is no draft state here, and the only undo is deleting it. |
| meta_create_post_commentA | Comment on a Page post — how you put an outbound link in the first comment rather than the post body. ⚠️ A successful call here is your ONLY confirmation. Reading comments back is not possible with a standard app (see the README), so if this succeeds, believe it; there is nothing to verify against. |
| meta_get_instagram_accountD | The linked Instagram Business account. |
| meta_create_instagram_postA | Publish to Instagram. Immediately public, no draft state. Instagram's Content Publishing API does not accept a direct file upload: the media must be at a publicly reachable http(s) URL that Meta fetches server-side. A local path can never work. |
| meta_callA | Call any Graph API endpoint directly, with the Page token by default. Meta publishes no machine-readable spec for the Graph API, so this server does not claim a complete catalogue — this is how you reach the rest of it. Paths are relative to the Graph host and version. |
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 6 tools
Each tool has a distinct purpose: page retrieval, post creation, comment creation, Instagram account retrieval, Instagram post creation, and a generic API caller. No overlaps or ambiguous boundaries.
All tools follow a consistent 'meta_verb_noun' pattern (e.g., meta_get_page, meta_create_page_post, meta_create_post_comment). Even the catch-all meta_call fits the naming convention.
Six tools is within the typical well-scoped range (3-15). It covers the core interactions without being overwhelming or excessively sparse.
The surface covers page and Instagram posting, plus a generic API caller that can fill gaps. However, it lacks dedicated operations like reading page posts or managing comments, which would be expected in full CRUD coverage. The catch-all mitigates this but doesn't fully replace dedicated tools.