Skip to main content
Glama
Facebook Marketplace MCP Server

Facebook Marketplace MCP Server

Facebook Marketplace MCP Server

An MCP server that provides access to Facebook Marketplace via direct GraphQL API calls. No browser automation at runtime — speaks Facebook's internal protocol directly.

How It Works

Facebook's web client makes all Marketplace requests as POST /api/graphql/ with a doc_id (query hash) and variables. This server replays those requests using your existing Facebook session cookies from Chrome.

Related MCP server: Facebook Marketplace MCP

Prerequisites

  • macOS (cookie extraction uses Keychain)

  • Google Chrome with an active Facebook login

  • Node.js 20+

Installation

git clone <this-repo>
cd facebook-marketplace-mcp
npm install
npm run build

Setup with Claude Code

claude mcp add facebook-marketplace -- node /path/to/facebook-marketplace-mcp/dist/index.js

Or add to your Claude Code config manually:

{
  "mcpServers": {
    "facebook-marketplace": {
      "command": "node",
      "args": ["/path/to/facebook-marketplace-mcp/dist/index.js"],
      "env": {
        "CHROME_PROFILE": "Default"
      }
    }
  }
}

Tools

search_listings

Search Marketplace by query, location, and filters.

Parameter

Type

Required

Description

query

string

yes

Search term

latitude

number

yes

Latitude of search center

longitude

number

yes

Longitude of search center

radius_km

number

no

Search radius (default: 50)

min_price

number

no

Min price in dollars

max_price

number

no

Max price in dollars

category

string

no

Category ID

limit

number

no

Max results (default: 20)

get_listing

Get full details for a specific listing.

Parameter

Type

Required

Description

listing_id

string

yes

Marketplace listing ID

Save a search as a monitor to track new listings over time.

Parameter

Type

Required

Description

name

string

yes

Monitor name

query

string

yes

Search term

latitude

number

yes

Search center lat

longitude

number

yes

Search center lng

radius_km

number

no

Radius (default: 50)

min_price

number

no

Min price

max_price

number

no

Max price

check_monitors

Check monitors for new listings since last check.

Parameter

Type

Required

Description

monitor_name

string

no

Check specific monitor, or omit for all

list_monitors

List all saved monitors.

delete_monitor

Delete a saved monitor.

Configuration

Env Variable

Default

Description

CHROME_PROFILE

Default

Chrome profile directory name

Updating GraphQL Queries

Facebook rotates their doc_id values on deploys. If searches stop working:

npm install -D playwright
npx playwright install chromium
npm run capture-queries

This opens a browser, navigates Marketplace, and captures current query IDs. Update src/facebook/queries.ts with the new values.

Rate Limiting

The server self-rate-limits to 3 requests/minute with random jitter to avoid detection. This means searches take a few seconds.

Limitations

  • macOS only for automatic cookie extraction

  • Requires Chrome with active Facebook session

  • Facebook ToS automating Facebook violates their Terms of Service

  • Fragile — doc_id values change on Facebook deploys

  • Rate limited aggressive use may trigger CAPTCHAs or account flags

  • No write operations — search/read only, no messaging or listing creation

Available Tools

7 tools
check_monitorsB

Check saved monitors for new listings since last check

Inputs: monitor_name.

delete_monitorB

Delete a saved search monitor

Inputs: name (required).

get_listingB

Get full details for a specific Facebook Marketplace listing

Inputs: listing_id (required).

list_monitorsB

List all saved search monitors

Inputs: no named parameters.

search_listingsC

Search Facebook Marketplace listings by query, location, and filters

Inputs: query (required), latitude (required), longitude (required), limit, +4 more.

search_locationA

Look up a city/town name to get coordinates for use with search_listings

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action: search_listings finds listings, get_listing fetches one, search_location resolves coordinates, and the monitor tools form a clean lifecycle. list_monitors vs check_monitors and monitor_search vs search_listings are clearly differentiated by their descriptions.

    Naming Consistency4/5

    Most names follow a clean verb_noun pattern (list_monitors, search_listings, get_listing, check_monitors, delete_monitor). The one deviation is monitor_search, which inverts the pattern (should be something like create_monitor), but the meaning is still readable.

    Tool Count5/5

    Seven tools is well-scoped for a Marketplace search-and-monitor server, with each tool earning its place across search, retrieval, location lookup, and monitor management.

    Completeness4/5

    The surface covers the full monitor lifecycle (create/list/check/delete) plus listing search and retrieval, which is comprehensive. The only minor gap is no way to update/edit an existing monitor's query or filters, requiring delete-and-recreate workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers