Supervised Meta Ads Operating System for Claude Code. You can find the premium version here
Konquest Meta Ads MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Supervised Meta Ads Operating System for Claude Code. You can find the premium version here: https://farasokster.gumroad.com/l/konquest-meta-ads-mcp-premium ## Open-Core Model.
Once Konquest Meta Ads MCP is connected, these are the calls the assistant has available:
Multi — asset ad creation (video + static image, multi-dimension)Production — tested** across 37+ client campaigns with real budgets and real edge casesVault-integrated — reads client intelligence (ICPs, brand voice, angles) to generate better adsRollback — undo recent changes with execution journalTier — based access** - safety tiers per account (sandbox, standard, production)META_ACCESS_TOKEN — Meta Marketing API access token (system user token recommended)META_APP_SECRET — for appsecret_proof (recommended for production)META_APP_ID — Meta app IDVAULT_PATH — path to your marketing vault directory (defaults to ~/marketing-vault)Classification — Countproduction-safe — 38supervised-only — 29Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
You will need 4 environment variables: META_ACCESS_TOKEN, VAULT_PATH, META_APP_SECRET, META_APP_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Konquest Meta Ads MCP's toolset — Multi, Production, Vault-integrated and 11 more — is a fair guide to whether it matches your workflow. It is maintained by brandu-mos; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Multi | asset ad creation (video + static image, multi-dimension) |
| Production | tested** across 37+ client campaigns with real budgets and real edge cases |
| Vault-integrated | reads client intelligence (ICPs, brand voice, angles) to generate better ads |
| Rollback | undo recent changes with execution journal |
| Tier | based access** - safety tiers per account (sandbox, standard, production) |
| META_ACCESS_TOKEN | Meta Marketing API access token (system user token recommended) |
| META_APP_SECRET | for appsecret_proof (recommended for production) |
| META_APP_ID | Meta app ID |
| VAULT_PATH | path to your marketing vault directory (defaults to ~/marketing-vault) |
| Classification | Count |
| production-safe | 38 |
| supervised-only | 29 |
| advisory-only | 31 |
| Category | Tools |
| Variable | Description | Required |
|---|---|---|
| META_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| VAULT_PATH | Filesystem location the server is allowed to use. | Optional |
| META_APP_SECRET | Credential the server authenticates with. | Yes |
| META_APP_ID | Configuration value read at startup. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.