Markifact Meta Ads MCP MCP server

An MCP server provided by Markifact that connects AI agents like Claude and ChatGPT to Meta Ads. It enables users to analyze performance across ad accounts, track pixels and CAPI, create ads and creatives, manage campaigns and audiences, and optimize performance with approval-based actions for changes.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Markifact

MCP endpoint (Streamable HTTP)

https://api.markifact.com/mcp/meta-ads

Vendor documentation

What you can do with it

Analyze campaign and ad performance across multiple Meta ad accounts
Create image, video, and carousel ads with natural language prompts
Inspect Meta Pixel and Conversions API setup for attribution issues
Manage custom and lookalike audiences for campaign targeting

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http markifact-meta-ads-mcp https://api.markifact.com/mcp/meta-ads

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add markifact-meta-ads-mcp --url https://api.markifact.com/mcp/meta-ads

Cursor

Merge this server into .cursor/mcp.json in your project, then enable markifact-meta-ads-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "markifact-meta-ads-mcp": {
      "url": "https://api.markifact.com/mcp/meta-ads"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "markifact-meta-ads-mcp": {
      "type": "streamableHttp",
      "url": "https://api.markifact.com/mcp/meta-ads",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start markifact-meta-ads-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "markifact-meta-ads-mcp": {
      "type": "http",
      "url": "https://api.markifact.com/mcp/meta-ads"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http markifact-meta-ads-mcp https://api.markifact.com/mcp/meta-ads

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "markifact-meta-ads-mcp": {
      "url": "https://api.markifact.com/mcp/meta-ads"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "markifact-meta-ads-mcp": {
      "serverUrl": "https://api.markifact.com/mcp/meta-ads"
    }
  }
}

See all 347

Do you run Markifact Meta Ads MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing