MCP Server Setup Guide

Follow this guide to connect AdsMAA's MCP server to your preferred AI tool.

Prerequisites

Before starting, make sure you have:

• An AdsMAA account with at least one connected Meta ad account
• Node.js 18+ installed on your machine
• Access to the AdsMAA MCP remote URL:
  output

  https://mcp.adsmaa.com/mcp

Step 1: Generate API Key

1. Log into AdsMAA and navigate to MCP Server (in sidebar under AI Tools) or Settings > Developer
2. Click Generate to create a new API key
3. Name it "MCP Server" and ensure
   output

   campaigns

   +
   output

   analytics

   permissions are enabled
4. Copy the key immediately — it will not be shown again

Step 2a: Claude Desktop Setup

Add the following to your Claude Desktop config file:

Use this configuration for all clients (Claude.ai, Claude Desktop, Claude Code, Cursor):

json
{
  "mcpServers": {
    "adsmaa": {
      "url": "https://mcp.adsmaa.com/mcp",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    }
  }
}

Replace

your_api_key_here

Where to add the config:

• Claude.ai: Settings > MCP Servers > Add server > paste URL and API key
• Claude Desktop:
  output

  ~/Library/Application Support/Claude/claude_desktop_config.json

  (macOS) or
  output

  %APPDATA%\Claude\claude_desktop_config.json

  (Windows)
• Claude Code:
  output

  ~/.claude/settings.json

• Cursor: Settings > MCP Servers > Add new server

Step 3: Verify Connection

After restarting your AI client:

1. You should see adsmaa listed in the MCP tools
2. Try these test prompts:
   • "List my Meta integrations"
   • "Show campaign statistics for the last 30 days"
   • "Run an audit on my ad account"
   • "What campaigns need attention?"

Environment Variables

ADSMAA_API_KEY

ADSMAA_AUTH_TOKEN

ADSMAA_BASE_URL

http://localhost:3000

ADSMAA_RATE_LIMIT

60

ADSMAA_RATE_WINDOW_MS

60000

*One of

ADSMAA_API_KEY

ADSMAA_AUTH_TOKEN

Troubleshooting

"Authentication failed" error

• Verify your API key is correct and not expired
• Check that the key has
  output

  campaigns

  and
  output

  analytics

  permissions
• Ensure
  output

  ADSMAA_BASE_URL

  points to the correct backend

"Backend request timed out"

• Verify the AdsMAA backend is running at the specified URL
• Check network connectivity between your machine and the backend
• For local development, ensure
  output

  ADSMAA_BASE_URL=http://localhost:3000

No tools showing up

• Restart your AI client after adding the config
• Check that the MCP server was built:
  output

  cd meta-ads-mcp-server && npm run build

• Verify Node.js 18+ is installed:
  output

  node --version

"Integration not found" on live tools

• Run
  output

  meta_list_integrations

  first to get valid integration IDs
• Ensure the integration status is "connected"
• If disconnected, reconnect via the AdsMAA Integrations page