meta-mcp MCP Server
brijr/meta-mcp
[](https://agentrank-ai.com/tool/brijr--meta-mcp/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) Are you the maintainer of brijr/meta-mcp? Claim this listing →
MCP Server for connecting to the Meta Marketing API
Add AgentRank to Claude Code Discover and compare tools like brijr/meta-mcp — your AI finds the right one automatically
Get API Access → claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
brijr/meta-mcp is a TypeScript MCP server. MCP Server for connecting to the Meta Marketing API Topics: facebook-ads, mcp, mcp-server, meta, meta-ads, ads-mcp, facebook-mcp.
Ranked #5886 out of 24846 indexed tools.
Ecosystem
TypeScript No license
facebook-adsmcpmcp-servermetameta-adsads-mcpfacebook-mcp
Score Breakdown
Stars 15% 200
200 stars → growing community
Freshness 25% 5mo ago
Last commit 5mo ago → stale
Issue Health 25% 100%
7/7 issues closed → responsive maintainer
Contributors 10% 2
2 contributors → solo project
Dependents 25% 0
No dependents → no downstream usage
npm Downloads N/A
PyPI Downloads N/A
Forks 74
Description Good
License None
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
How to Improve
Description low impact
License low impact
Freshness high impact
Matched Queries
From the README
# Meta Ads MCP Server A Cloudflare Workers MCP server for Meta Ads account setup, campaign management, ad sets, creatives, audiences, reporting, and batch workflows. This repo is built on `xmcp` and exposes a Streamable HTTP MCP endpoint plus browser-facing Meta OAuth routes. ## Open Source / Self-Hosted This repository is intended to be deployed in your own Cloudflare account with your own Meta app credentials. It does not ship with: - a hosted control plane - a shared Meta app - a built-in end-user dashboard - a JWT issuer for your users and workspaces You bring: - your Cloudflare Worker deployment - your Meta developer app - your JWT issuer or auth provider - your own UI or backend that initiates the OAuth flow ## What It Does - Runs as a Cloudflare Worker - Uses direct Meta Graph API `fetch` calls instead of the Meta SDK - Stores Meta user connections per workspace in D1 - Stores short-lived OAuth state in KV - Encrypts stored Meta access tokens - Protects MCP requests wiRead full README on GitHub →
Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.