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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago