Armavita Meta Ads Mcp

What is Armavita Meta Ads Mcp?

Armavita Meta Ads Mcp is a local Model Context Protocol server for Meta Ads built for local MCP clients such as Claude Code, Cursor, and Codex. It provides a set of tools to manage Meta ad accounts, campaigns, ads, targeting, and insights via the Meta Marketing API.

How to use Armavita Meta Ads Mcp?

Install the package via pip (pip install armavita-meta-ads-mcp) or from source (uv sync). Configure authentication by setting either a META_ACCESS_TOKEN environment variable (access token mode) or both META_APP_ID and META_APP_SECRET (OAuth mode). Run the server with armavita-meta-ads-mcp and optionally --login for OAuth flow. Register the server in your MCP client using the provided JSON configuration.

Key features of Armavita Meta Ads Mcp

• Supports both Meta access token and local OAuth authentication.
• Provides tools for accounts, campaigns, ad sets, ads, and creatives.
• Includes insights and reporting with date range or presets.
• Offers targeting tools: interest/behavior/demographic search and audience estimation.
• Supports duplication of campaigns, ad sets, and ads.
• Uses cursor-based pagination on list endpoints.
• Redacts access tokens from returned URL fields for security.
• Only supports stdio MCP transport (no HTTP).

Use cases of Armavita Meta Ads Mcp

• Automate creation and management of Meta ad campaigns from a local environment.
• Retrieve and analyze ad performance insights with flexible date ranges.
• Search for interests and audience estimates to inform targeting.
• Clone existing campaigns, ad sets, or ads for rapid testing.
• Access the Meta Ads Archive for competitive research.

FAQ from Armavita Meta Ads Mcp

What authentication methods does Armavita Meta Ads Mcp support?

Armavita Meta Ads Mcp supports two authentication methods: a direct Meta access token (META_ACCESS_TOKEN) or a local OAuth flow using META_APP_ID and META_APP_SECRET.

What transport does the server use?

The server uses only local stdio MCP transport. Remote or HTTP transports are not supported.

What version of the Meta Marketing API is used?

By default, Armavita Meta Ads Mcp uses Meta Marketing API version v25.0. This can be overridden by setting the META_GRAPH_API_VERSION environment variable.

How does pagination work?

Cursor-based pagination is supported on core list endpoints. Use the page_cursor parameter with the paging.cursors.after value from the previous response. Responses preserve Meta's native paging object.

What are the runtime requirements?

Armavita Meta Ads Mcp requires Python 3.11+ and the mcp[cli] package version 1.26.0.