Run My Ads

com.runmyadsPublished by runmyads.comOfficial publisherv1.0.0Updated Oct 31, 2026

Read your Meta ads from your own AI; find why cost per booked appointment moved. From $49/30 days.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI assistant read your Meta ads data and investigate why cost per booked appointment changed.

What you can do
  • Read Meta ads performance data from your own ad account through the assistant.
  • Investigate shifts in cost per booked appointment and look into what drove them.
  • No tool list is published, so the exact set of actions is not documented; the description centers on reading ad results and diagnosing cost changes.
When to use it
Useful when you run Meta ad campaigns and want to ask an assistant why appointment-booking costs moved, without switching between ad dashboards and chat.
Requirements
A remote endpoint at app.runmyads.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. A paid subscription is mentioned, starting at $49 per 30 days.
Before you install
OAuth grants the server access to your Meta ads data, so review the scopes requested during sign-in. The service is paid, starting at $49 per 30 days, so check billing before connecting. Your ad account data is shared with a third-party service.

Installation

In SourceWeft

  1. Open Run My Ads 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/com.runmyads%2Frun-my-ads/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": {
    "run-my-ads": {
      "type": "http",
      "url": "https://app.runmyads.com/mcp/rma"
    }
  }
}

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.0LatestOct 31, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.