AdsAgent — Meta Ads MCP

md.adsagentPublished by adsagent.mdOfficial publisherv1.0.0Updated Oct 24, 2026

Hosted Meta ads MCP with OAuth, bounded reads, and prepare/confirm writes.

The publisher's own server: AdsAgent — Google Ads MCP

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A hosted Meta ads MCP server that lets an assistant read ad data and prepare and confirm ad changes under OAuth.

What you can do
It connects an assistant to Meta advertising through a hosted remote endpoint. The description lists OAuth authentication, bounded reads, and a prepare/confirm pattern for writes. No individual tools are listed in the manifest, so the exact read and write operations are not documented here.
When to use it
Consider it when an assistant needs to work with Meta ads data or make controlled changes to ad campaigns, and when a hosted OAuth-based connection is preferred over running a local server. It is not aimed at non-Meta advertising platforms.
Requirements
A remote streamable HTTP endpoint at the provider's host, reached over the network, with OAuth authentication required. No packages, environment variables, or headers are declared.
Before you install
Writes are described as prepare/confirm, so an assistant may stage changes to live ad campaigns; review each confirmation before approving. Access is granted through OAuth, so the connected account's advertising permissions and any spending authority should be considered before authorizing.

Installation

In SourceWeft

  1. Open AdsAgent — Meta Ads MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/md.adsagent%2Fmeta-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "adsagent-meta-ads": {
      "type": "http",
      "url": "https://adsagent.md/mcp/v2"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Adsagent integrations