social-media-toolchain

Social Media MCP Toolchain

Overview

The user has self-hosted, private-API MCP servers for their own personal accounts. Each lives in ~/source/repos/ with its own SETUP.md. Status today: Instagram = live/registered, Facebook Messenger = built (groups/rooms/pages only), WhatsApp = built but proof-of-concept ONLY (do not register or use for routine tasks). TikTok = built: a read-only public scraper (trending works keyless, the other tools need an ms_token). All use private/unofficial APIs, so each carries Terms-of-Service and account-ban risk — keep usage human-paced (especially anything that writes/sends), and never commit credentials. Secrets (cookies, sessions, tokens, auth_info/, *.db, .env) are .gitignored in every repo.

Platform	Repo (~/source/repos/)	Runtime	Auth	Reads	Status / Hard limit
Instagram	insta-mcp	Node (JS)	session.json from a 2FA login (login.mjs); real password not stored	saved, posts, feed, search, DMs, liked, stories	LIVE / registered. Library spoofs a stale app version → IG unsupported_version checkpoint; fixed by impersonating the device's current IG app version (src/index.ts, env IG_APP_VERSION)
FB Messenger	fb-messenger-mcp	Python (venv)	facebook.com cookies (data/cookies.json, exported via the C3C extension)	group / room / page threads + message search	Built (groups/rooms/pages only). Personal 1:1 DMs are E2EE → unreadable by any unofficial API

Registering / loading

Egress: residential proxy + account state

Tool inventory (logical names)

Operating rules