Skip to content
Back to search

meta-ads

SkillWorks with Claude CodeGitHub

Meta Marketing API for Instagram and Facebook campaigns, with confirmation guards on every write.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kremnyi--meta-ads-mcp/badge.svg)](/listings/kremnyi--meta-ads-mcp)

HTML

<a href="/listings/kremnyi--meta-ads-mcp"><img src="/api/listings/kremnyi--meta-ads-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Claude Code.** Load the directory for one session:

claude --plugin-dir /path/to/meta-ads-mcp

For a permanent installation, add the directory to a plugin marketplace. The plugin includes the `meta-ads` skill, which has campaign recipes.

**Other MCP clients.** Start the server on stdio:

{
  "mcpServers": {
    "meta_ads": {
      "command": "node",
      "args": ["/absolute/path/to/meta-ads-mcp/scripts/server.mjs"]
    }
  }
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 9 lines
  1. {
  2. "name": "meta-ads",
  3. "displayName": "Meta Ads MCP",
  4. "version": "0.2.0",
  5. "description": "Meta Marketing API for Instagram and Facebook campaigns, with confirmation guards on every write.",
  6. "author": { "name": "Bohdan Kremnyi" },
  7. "license": "MIT",
  8. "keywords": ["meta", "instagram", "facebook", "ads", "marketing-api"]
  9. }
README.md · README · 99 lines
  1. # Meta Ads MCP
  2. One Node.js MCP server for the Meta Marketing API (Graph API). It has no npm dependencies.
  3. It manages Instagram and Facebook campaigns, ad sets, ads, and creatives for one ad account. It also reads insights and Instagram media.
  4. ## Tools
  5. | Tool | Access | Function |
  6. | --- | --- | --- |
  7. | `auth_status` | Read | Shows the token permissions, the token expiry, and the ad account |
  8. | `list` | Read | Lists campaigns, ad sets, ads, creatives, audiences, pixels, and media |
  9. | `get` | Read | Gets one object by ID |
  10. | `insights` | Read | Gets performance data for the account, a campaign, an ad set, or an ad |
  11. | `targeting_search` | Read | Finds interests, locations, locales, and categories |
  12. | `create` | Write | Makes a campaign, ad set, creative, or ad |
  13. | `update` | Write | Changes fields, for example budget, targeting, or name |
  14. | `set_status` | Write | Sets ACTIVE, PAUSED, or ARCHIVED |
  15. | `copy` | Write | Copies a campaign, ad set, or ad |
  16. | `delete` | Write | Deletes a campaign, ad set, ad, or creative |
  17. ## Safety
  18. A write can spend money. These rules apply to each write:
  19. - The call needs an exact change summary and `user_confirmed: true`.
  20. - `create` and `copy` always make PAUSED objects.
  21. - `update` refuses a status change. Activation is a separate `set_status` call.
  22. - `update`, `set_status`, `copy`, and `delete` first make sure that the object belongs to the configured ad account.
  23. ## Requirements
  24. - Node.js 24 or later.
  25. - The ID of a Meta ad account.
  26. - A Meta access token for that account. The read tools need `ads_read`. The write tools need `ads_management`. Instagram media and stories also need Instagram permissions.
  27. `auth_status` shows the granted permissions and the token expiry.
  28. ## Install
  29. **Claude Code.** Load the directory for one session:
  30. ```sh
  31. claude --plugin-dir /path/to/meta-ads-mcp
  32. ```
  33. For a permanent installation, add the directory to a plugin marketplace. The plugin includes the `meta-ads` skill, which has campaign recipes.
  34. **Other MCP clients.** Start the server on stdio:
  35. ```json
  36. {
  37. "mcpServers": {
  38. "meta_ads": {
  39. "command": "node",
  40. "args": ["/absolute/path/to/meta-ads-mcp/scripts/server.mjs"]
  41. }
  42. }
  43. }
  44. ```
  45. ## Configuration
  46. The source contains no account data. Put the settings in an env file with mode `600`. See `meta-ads.env.example`.
  47. The env file is the first of these that is set:
  48. 1. `META_ADS_ENV_FILE`
  49. 2. `$XDG_CONFIG_HOME/meta-ads/meta-ads.env`
  50. 3. `~/.config/meta-ads/meta-ads.env`
  51. | Variable | Content |
  52. | --- | --- |
  53. | `META_ADS_ACCOUNT_ID` | The ad account ID, with or without the `act_` prefix |
  54. | `META_ADS_ACCESS_TOKEN` | The access token |
  55. | `META_ADS_API_VERSION` | Optional. The Graph API version. The default is `v23.0`. |
  56. A variable in the environment of the server process overrides the value in the file.
  57. The server reads the file on each call, so a new token needs no restart. The server sends the token in the `Authorization` header.
  58. ## Backup
  59. ```sh
  60. node scripts/backup.mjs <output-directory>
  61. ```
  62. This command makes a read-only export of the ad account as JSON files: campaigns, ad sets, ads, creatives, audiences, pixels, and insights. The output contains your account data. Do not put it in a public repository.
  63. ## Tests
  64. ```sh
  65. npm test # protocol and write guards; no network, no credentials
  66. node scripts/test.mjs --live # read-only requests to Meta
  67. ```
  68. ## License
  69. MIT. See `LICENSE`.

Version history

  • v0.2.011/21/2026

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.