Autoady

io.autoady.wwwPublished by www.autoady.ioOfficial publisherv2.0.0Updated Oct 24, 2026

Run Meta ads from your AI assistant: briefings, drop diagnosis, winners, budgets, receipts.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an AI assistant run Meta ads: briefings, drop diagnosis, winners, budgets and receipts.

What you can do
Autoady connects an AI assistant to Meta advertising workflows. According to the registry description, it covers briefings, diagnosis of performance drops, identification of winning ads, budget handling and receipts. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Relevant for teams that manage Meta ad campaigns and want to brief, diagnose underperformance, review winners, adjust budgets or check receipts from within an AI assistant rather than the ads interface.
Requirements
A remote MCP endpoint at the provider's site over streamable HTTP. Authentication is OAuth and required, so a provider account and an OAuth sign-in are needed. No environment variables or headers are declared.
Before you install
The server is described as running Meta ad campaigns, including budgets, so actions may change live campaigns and spend money. OAuth grants it access to the connected advertising account. Review what it can change before connecting, and confirm budget or campaign changes before they are applied.

Installation

In SourceWeft

  1. Open Autoady 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/io.autoady.www%2Fmcp/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": {
    "autoady": {
      "type": "http",
      "url": "https://www.autoady.io/api/mcp"
    }
  }
}

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. v2.0.0LatestSep 16, 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.