claude-meta-mcp: My Open-Source Connector for Claude

If you wanted to control Meta ad data or posts via AI, you had two options: a SaaS connector like windsor.ai or Pipeboard (your data flows through their servers) or manually exported spreadsheets and manual posting. For agencies under NDAs or companies with GDPR obligations, both are awful.

That's why I built claude-meta-mcp — a self-hosted Meta connector for Claude and other MCP clients (including ChatGPT with MCP support). MIT-licensed, no SaaS middleman.

What it is

A Streamable-HTTP server following the Model Context Protocol standard. It connects AI clients directly to the Meta Graph API v22. You install it on your own server, drop in a System User token, and access your Meta Ads, Facebook Pages, Instagram accounts and Product Catalogs from Claude or ChatGPT.

What's inside

Currently 47 tools (v0.4), split into four areas:

• Meta Ads (CRUD): create, read, update and pause campaigns, ad sets, ads and creatives — including asset upload and ad preview
• Facebook Pages (read + write): create posts, fetch insights, engagement
• Instagram Business publishing: publish images, videos, reels, stories and carousels, plus comment moderation and reach analytics
• Product Catalogs (read): businesses, catalogs, feeds, products and diagnostics — for Dynamic Product Ads and shop catalog health checks

All through the official Graph API. No scrapers, no workarounds.

Safe defaults

Every creation tool sets campaigns, ad sets and ads to PAUSED by default. Activation requires an explicit second action. That way the AI can't accidentally burn budget.

How it works technically

• TypeScript, Node 20, Express 5
• MCP SDK + OAuth 2.1 with Dynamic Client Registration
• nginx reverse proxy, pm2 cluster mode
• TLS via Let's Encrypt

The OAuth shim lets Claude.ai add the connector through its normal "Add connector" UI — no tunnels, no hacks.

What you need

• A Meta Developer App in Business mode with the relevant use cases
• System User token with ads_read, ads_management, business_management and the Pages/Instagram scopes
• A Linux VPS with Node 20
• nginx + TLS certificate

The README walks through the Meta App setup and token creation step by step — usually the most painful part.

Why open source

The code shouldn't sit in my drawer. Anyone who wants to build a connector for other platforms (Google Ads, LinkedIn, TikTok) can reuse the OAuth layer and MCP structure as a starting point. License: MIT — fork it, change it, use it commercially.

If you'd like to contribute or open issues, the repo is on GitHub.

---

More on the idea and the full tool list on the repo page.