Marketplace Finder MCP Server
Search Facebook Marketplace for listings with filters (query, city, price, radius, days listed, sort, max results) and retrieve full listing details and descriptions.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Marketplace Finder — an MCP server that searches marketplaces in your own browser
One job: let a remote agent (e.g. claude.ai) search online marketplaces for an item — anything for sale, not just housing — through your logged-in browser, running on your machine.
How it fits together
claude.ai ──HTTPS──▶ tunnel (cloudflared/ngrok) ──▶ this server (your Mac)
│
▼
your logged-in Chromium (Playwright)
│
▼
Facebook Marketplaceclaude.ai can only reach an MCP server over HTTP, but Facebook Marketplace only shows real results to a real, logged-in browser. So this server runs locally (Streamable-HTTP transport), drives your persistent logged-in Chromium, and you expose it to claude.ai through a tunnel.
The agent gathers missing details from you in chat (budget, city, condition…) before it calls a tool — the tools just declare parameters.
Related MCP server: marketplace-lister-mcp
Tools the agent gets
search_facebook_marketplace—query,city,min_price,max_price,radius_km,days_listed,sort(best/newest/price_low/price_high/distance),max_results. Returns structured listings (title, price, location, url, photo, raw text) pulled straight off the results page.get_listing_details— full description / condition for one listing URL.
Setup — one command
Want the step-by-step + troubleshooting? See DEPLOY.md.
brew install cloudflared # if you don't have it yet
./finder install./finder install does everything, idempotently:
creates the virtualenv, installs deps, downloads Chromium,
opens a browser for your one-time Facebook login,
sets up a permanent Cloudflare tunnel to
https://mcp.<your-domain>/mcp(a named tunnel routed to a domain you manage in Cloudflare — the URL never changes), andinstalls launchd services so the server + tunnel auto-start at login and restart themselves if they crash. No terminals to babysit.
When it finishes it prints your permanent connector URL. Paste it once into claude.ai → Settings → Connectors → Add custom connector:
https://mcp.<your-domain>/mcpNow ask claude.ai things like "find me a used Herman Miller Aeron under $400 in Seattle, listed this week." It will ask for anything it's missing, then call the search tool, which runs in your browser.
Managing it
./finder status # health of server + tunnel, and your connector URL
./finder logs # tail the live logs
./finder restart # bounce both services
./finder login # re-log into Facebook when the session expires
./finder stop # /start, /uninstall also availableBecause the tunnel host is now stable, the server pins it via
MCP_ALLOWED_HOSTS — DNS-rebinding protection is back on (the old rotating
quick-tunnel URL couldn't do this).
Config (environment variables, all optional)
Var | Default | Meaning |
|
| bind address |
|
| port |
| (unset) | set it to lock the server with Google sign-in (the recommended gate that works with claude.ai). |
| (unset) | the matching Google OAuth client secret |
| (unset) | comma-separated allowlist of Google emails permitted to connect |
| (auto) | public base URL for OAuth metadata + the Google redirect; derived from your tunnel host when unset |
| (unset) | static |
| (unset) | comma-separated Host allow-list. Unset = DNS-rebinding protection off (needed so a rotating tunnel host isn't rejected with HTTP 421). Set it to pin specific hosts. |
|
| set |
|
| FB city slug used when a search omits one |
Locking it down (recommended)
Without a gate, anyone who learns your URL can drive your logged-in Facebook
session. ./finder install offers to lock the server to your Google
account. One-time setup in
Google Cloud — full
step-by-step (incl. the consent screen) is in DEPLOY.md:
OAuth consent screen → User type External, then Publish to Production (our scopes are non-sensitive, so no Google review). External + Production is what lets friends with any Gmail sign in.
Credentials → OAuth client ID, type Web application, with the Authorized redirect URI exactly
https://<your-host>/oauth/google/callback.Run
./finder install; paste the Client ID + secret and list the allowed email(s).
claude.ai then shows a Google sign-in when you add the connector; only the allowlisted account(s) get in. (Cloudflare Access does not work here — it breaks claude.ai web; see CLAUDE.md → "Auth".)
Sharing with friends: add their Gmail to MCP_ALLOWED_EMAILS in .finder.env
and ./finder restart, then send them the URL — they add it in their own
claude.ai and sign in. Remove the email + restart to revoke. (Their searches run
through your Facebook session on your Mac.) Details in docs/DEPLOY.md →
"Adding & removing friends".
First connect shows "Server not found"? It's a transient while the OAuth handshake finishes — just refresh. See docs/DEPLOY.md → Troubleshooting.
Notes & next steps
Facebook city slugs are short names like
vancouver,seattle,nyc,la,chicago. The agent passes one ascity.Session expiry: if Facebook starts showing a login wall, the tool says so — run
./finder login(re-auths FB, then restarts the service).Adding marketplaces (Craigslist, eBay, Kijiji…): add a new
@mcp.tool()insrc/server.pythat builds that site's search URL and reuses the same card-extraction pattern. Craigslist needs no login; it's scraped through the same real browser because it blocks datacenter IPs.Clarifying questions are handled by the agent today. If you later want the server to drive structured prompts, that's MCP "elicitation" — a tool can request input mid-call via
ctx.elicit(...); client support is still uneven.
This folder is self-contained and ready to move into its own repo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
LinkedIn MCP server for ChatGPT, Claude and any AI agent: create post, comment on post, send message, send connection invitation, search people, search companies, list connections and read conversations in your own LinkedIn account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to LinkedIn yourself; Cotlet does not store your password and you need no LinkedIn API key. About the official LinkedIn API: LinkedIn has an official API, but most of it needs an approved application (checked 6 Nov 2026). The open Share on LinkedIn permission lets an app post, comment and like on behalf of a member. Setup and FAQ: https://cotlet.dev/integrations/linkedin-api-mcp-server
Mashvisor MCP server for ChatGPT, Claude and any AI agent: run saved search, get property analysis and export properties in your own Mashvisor account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Mashvisor yourself; Cotlet does not store your password and you need no Mashvisor API key. About the official Mashvisor API: Mashvisor has a REST Data API, sold as a separate product with an API key: a free tier of 30 one-time sample requests, then plans from $129 a month for 500 calls (checked 11 Oct 2026). It returns market and property data. Setup and FAQ: https://cotlet.dev/integrations/mashvisor-api-mcp-server
Hemnet MCP server for ChatGPT, Claude and any AI agent: search listings, get sold prices, list saved homes, save search and follow home value in your own Hemnet account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Hemnet yourself; Cotlet does not store your password and you need no Hemnet API key. About the official Hemnet API: Hemnet has no public or developer API for buyers or owners (checked 11 Oct 2026). Its own AI access is the Hemnet app inside ChatGPT, which runs only in ChatGPT and gives your agent or scripts no way to read your saved homes or saved searches. Setup and FAQ: https://cotlet.dev/integrations/hemnet-api-mcp-server
Bullhorn MCP server for ChatGPT, Claude and any AI agent: search candidates, find matching candidates for a job, add candidate note, submit candidates to a job, update submission status and list job submissions in your own Bullhorn account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Bullhorn yourself; Cotlet does not store your password and you need no Bullhorn API key. About the official Bullhorn API: Bullhorn has a REST API, but it is sold as a paid partner contract to technology vendors, not as a key for a recruiter or an agency (checked 23 Oct 2026). Bullhorn does not allow middleware or connector companies to build on it and has no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/bullhorn-api-mcp-server
Related MCP Servers
- FlicenseAqualityCmaintenanceEnables searching Facebook Marketplace listings from Claude using your existing Facebook session without a browser.72-
- AlicenseAqualityDmaintenanceEnables posting second-hand items to Facebook Marketplace from local photo folders via Claude, featuring login, listing creation, pricing reference, and publishing tools.76MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and compare Facebook Marketplace listings, collect listing details and photos, organize research workspaces, evaluate promising items with reusable product guides, and refresh or revisit results while preserving evidence.1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to read public marketplace listings—searching sources and fetching individual listings as structured JSON—through a self-hosted bridge that runs on a residential connection and fetches pages with a real Chromium browser, avoiding datacenter IP blocks. It is strictly read-only, reporting blocks, login walls and unavailable sources as explicit statuses instead of performing any account actions.-