How apichai-17/meta-mcp works
Meta Ads MCP Server exposes Meta Marketing API operations to AI clients through MCP, with both local stdio and documented remote OAuth deployment modes. The main workflow is client request → MCP tool/resource handling → authenticated Meta API request → advertising data or action returned. Campaign/ad setup, audience targeting, creative work, and analytics remain distinct product stages. Source excerpts confirm the stdio entry point, resource registration, API-client request path, and authentication/storage behavior; some tool-to-client and remote-handler wiring is inferred only from the documented capabilities and tree.
Main entry points: meta-client.ts Marketing API client · index.ts Local MCP server · mcp.ts Remote MCP endpoint · user-auth.ts User sessions
Components 20
MCP interface
- Local MCP server
src/index.ts - Campaign resources
src/resources/campaigns.ts - Insights resources
src/resources/insights.ts - Audience resources
src/resources/audiences.ts
Advertising capabilities
- Campaign and ads
src/tools/campaigns.ts - Analytics tools
src/tools/analytics.ts - Audience tools
src/tools/audiences.ts - Creative tools
src/tools/creatives.ts - Marketing API client
src/meta-client.ts
Identity and resilience
- OAuth tools
src/tools/oauth.ts - Token management
src/utils/auth.ts - User sessions
src/utils/user-auth.ts - Session storage
src/utils/user-auth.ts - API error handling
src/utils/error-handler.ts - Rate limiting
src/utils/rate-limiter.ts - Pagination
src/utils/pagination.ts
Remote access
- Remote MCP endpoint
api/mcp.ts - OAuth routes
api/auth
Other components
- AI assistant
- Meta Marketing API
Connections 30
- AI assistant → Local MCP server: sends MCP requests
- AI assistant → Remote MCP endpoint: sends remote requests
- Local MCP server → Campaign and ads: registers tools
- Local MCP server → Analytics tools: registers tools
- Local MCP server → Audience tools: registers tools
- Local MCP server → Creative tools: registers tools
- Local MCP server → OAuth tools: registers tools
- Local MCP server → Campaign resources: registers resources
- Local MCP server → Insights resources: registers resources
- Local MCP server → Audience resources: registers resources
- Campaign resources → Marketing API client: fetches campaign data
- Audience resources → Marketing API client: fetches audience data
- Campaign and ads → Marketing API client: manages ads
- Analytics tools → Marketing API client: requests insights
- Audience tools → Marketing API client: manages audiences
- Creative tools → Marketing API client: manages creatives
- OAuth tools → Token management: manages tokens
- Marketing API client → Token management: uses credentials
- Marketing API client → Rate limiting: limits requests
- Marketing API client → API error handling: handles responses
- Marketing API client → Pagination: parses pages
- Marketing API client → Meta Marketing API: sends API requests
- Remote MCP endpoint → User sessions: authenticates users
- Remote MCP endpoint → Campaign and ads: dispatches MCP tools
- Remote MCP endpoint → Analytics tools: dispatches MCP tools
- Remote MCP endpoint → Audience tools: dispatches MCP tools
- Remote MCP endpoint → Creative tools: dispatches MCP tools
- OAuth routes → User sessions: manages sessions
- User sessions → Session storage: reads and writes
- User sessions → Token management: builds user credentials