Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FB_PROXYNoProxy URL used to reach Facebook. If not set, the transport falls back to the HTTPS_PROXY environment variable or the macOS system proxy.
FB_COOKIENoCookie string for authenticated operations (e.g., search_people, search_pages, send_message). Alternatively, use FB_COOKIE_FILE or place a cookies.txt in ~/.facebook-mcp/accounts/<account>/.
FB_ACCOUNTNoAccount name selecting the directory under ~/.facebook-mcp/accounts/ (e.g., 'default', 'work').default
HTTPS_PROXYNoStandard proxy environment variable used as a fallback when FB_PROXY is not set.
FB_COOKIE_FILENoPath to a Netscape-format cookies.txt file used for authenticated operations. Alternative to FB_COOKIE.
FB_TRANSPORT_MODENoTransport mode: 'http' to use stored cookies without a browser, or 'auto' to borrow a live Chrome session (cookies bootstrapped lazily).

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_user_latest_post_timeA

Get the publish time (UTC) of a user's latest post by username. Example username: 'exampleuser' (no URL, no leading '@'). Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

get_user_recent_postsB

List a user's recent posts (newest first), including text, UTC publish time and permalink. Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

search_peopleA

Search Facebook people by keyword, e.g. 'pest control'. Requires a logged-in session. Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

search_pagesB

Search Facebook pages by keyword, e.g. 'pest control'. Requires a logged-in session. Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

send_messageA

Send a Messenger message to a user or page. 'recipient' accepts a numeric uid, a username/vanity, or a profile URL. Requires a logged-in browser (FB_TRANSPORT_MODE=auto or cdp). Optional account name selecting the credential set under ~/.facebook-mcp/accounts//. Defaults to the configured account.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation4/5

search_people, search_pages, and send_message are clearly distinct, and the two retrieval tools target different scopes. However, get_user_latest_post_time is essentially a subset of get_user_recent_posts (which returns newest-first posts with publish times), so an agent may struggle to justify choosing one over the other.

Naming Consistency5/5

All five tools follow a consistent snake_case verb_noun pattern (get_user_*, search_*, send_message). No mixed conventions or vague verbs; the naming is predictable and self-explanatory.

Tool Count4/5

Five tools is a reasonable, well-scoped surface for a Facebook read/search/messaging server. It is on the lean side but each tool earns its place, with no filler.

Completeness3/5

The surface covers reading posts, searching people/pages, and sending messages, but lacks any content-creation (posting, commenting, liking) or message/conversation retrieval, leaving notable gaps for a Facebook interaction server.

Maintenance

ActivityMaintained
ResponsivenessNo issues