Meta Ads Insights Macp

Created By
ncklrs10 months ago
A Model Context Protocol (MCP) server for accessing Meta (Facebook) Ads insights data with built-in support for joining with HubSpot deal data. Features Fetch ad insights with flexible filtering and breakdowns Campaign and ad set management Mobile placement tracking for revenue attribution Prepare ads data for joining with HubSpot deals Configurable access tokens via MCP configuration
Overview

What is Meta Ads Insights MCP?

Meta Ads Insights MCP is a Model Context Protocol (MCP) server designed to access Meta (Facebook) Ads insights data, with the capability to join this data with HubSpot deal data for enhanced analytics.

How to use Meta Ads Insights MCP?

To use the server, install the necessary dependencies, build the server, and configure it within your Claude Desktop application. You will need to obtain a Meta Access Token and your Ad Account ID to set up the configuration properly.

Key features of Meta Ads Insights MCP?

  • Fetch ad insights with flexible filtering and breakdowns.
  • Manage campaigns and ad sets effectively.
  • Track mobile placements for accurate revenue attribution.
  • Prepare ads data for integration with HubSpot deals.
  • Configurable access tokens for secure data access.

Use cases of Meta Ads Insights MCP?

  1. Analyzing mobile ads revenue attribution by correlating ad performance with HubSpot deal data.
  2. Conducting campaign performance analysis to identify the most effective ad placements and strategies.
  3. Preparing ads data for detailed reporting and insights generation in conjunction with HubSpot.

FAQ from Meta Ads Insights MCP?

  • What permissions are needed for the Meta Access Token?

The token must have ads_read permission to access ad insights data.

  • How do I find my Ad Account ID?

The Ad Account ID can be found in the URL of the Meta Ads Manager, excluding the "act_" prefix.

  • What should I do if I encounter issues?

Ensure your access token is valid, the Ad Account ID is correct, and the server configuration path is accurate.

Server Config

{
  "mcpServers": {
    "meta-ads-insights": {
      "command": "node",
      "args": [
        "/absolute/path/to/your/project/dist/index.js"
      ],
      "env": {
        "META_ACCESS_TOKEN": "your_meta_access_token_here",
        "META_AD_ACCOUNT_ID": "your_ad_account_id_without_act_prefix",
        "META_API_VERSION": "v19.0"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
ncklrs
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago