About Meta Ads Insights Macp
Meta Ads Insights Macp is an MCP server for retrieving Meta ad performance and campaign data. It also prepares ad records to join with HubSpot deals for revenue attribution.
Key features
- 01Ad insights with filters and breakdowns
- 02Campaign and ad set listing
- 03Mobile placement tracking
- 04HubSpot join preparation by date, UTM, or click ID
- 05Configurable access tokens
Use cases
- 01Analyze campaign performance by placement and device
- 02Relate mobile ad spend to HubSpot deal revenue
MCP support
Exposes tools to retrieve Meta ad insights, list campaigns and ad sets, and prepare data for joining with HubSpot deals.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMeta Ads Insights MCP Server
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
Setup
- Install dependencies:
npm install
- Build the server:
npm run build
- Configure Claude Desktop: Add the server configuration to your Claude Desktop config file:
Location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Configuration:
{
"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"
}
}
}
}
-
Get your Meta Access Token:
- Go to Meta for Developers
- Create an app or use existing app
- Generate a User Access Token with
ads_readpermission - For production, use a System User Access Token
-
Find your Ad Account ID:
- Go to Meta Ads Manager
- The account ID is in the URL:
act_1234567890(use just1234567890)
Available Tools
get_ad_insights
Fetch ad performance data with breakdowns and filtering.
Example usage:
Get mobile ad performance for the last 30 days with placement breakdown
get_campaigns
List campaigns with filtering options.
get_adsets
List ad sets, optionally filtered by campaign.
prepare_hubspot_join
Prepare ads data for joining with HubSpot deals data using various strategies:
- date_range: Match deals created within attribution window
- utm_params: Match deals with UTM parameters
- conversion_tracking: Match deals with Facebook click IDs
Example workflow:
- Get mobile placement ads data
- Prepare for HubSpot join with date range strategy
- Use the prepared data to query HubSpot for deals created within the attribution window
- Analyze mobile ads → revenue correlation
Example Use Cases
Mobile Ads Revenue Attribution
1. Get ads insights with device_platform and placement breakdowns
2. Filter for mobile placements
3. Prepare data for HubSpot join with 7-day attribution window
4. Query HubSpot deals created in that timeframe
5. Calculate ROI from mobile ad spend to deal revenue
Campaign Performance Analysis
1. Get campaign insights for last 30 days
2. Break down by placement and device
3. Join with HubSpot deal data
4. Identify highest-converting campaign + placement combinations
Data Joining Strategy
The server provides a prepare_hubspot_join tool that:
- Adds join keys based on strategy (UTM params, date ranges, click IDs)
- Calculates attribution windows
- Flags mobile placements for filtering
- Provides HubSpot query suggestions
This allows you to connect ad performance data with actual revenue outcomes tracked in HubSpot.
Development
# Development mode with auto-rebuild
npm run dev
# Build only
npm run build
# Run built server
npm start
Troubleshooting
- Ensure your Meta access token has
ads_readpermission - Verify the ad account ID is correct (without "act_" prefix)
- Check that the absolute path in claude_desktop_config.json is correct
- Restart Claude Desktop after configuration changes# meta-insights-mcp
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.