Meta Ads MCP server with 47 tools for campaigns, creatives, audiences, and insights.
The publisher's own URL. Not a PlugMCP endpoint.
https://mcp.adweave.ai/meta-ads-mcp
Claude opens with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.adweave-meta-ads-mcp https://mcp.adweave.ai/meta-ads-mcp
Run in a terminal.
{
"mcpServers": {
"ai.adweave-meta-ads-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.adweave.ai/meta-ads-mcp"
]
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
This server asks you to sign in when you connect. Your agent handles that.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchMeta Ads MCP server with 47 tools for campaigns, creatives, audiences, and insights.
README is not crawled yet. No repository on file.
No tool list yet. Remote servers get one after the first health check.