Tera Ads

co.teraadsPublished by teraads.coOfficial publisherv1.0.1Updated Nov 5, 2026

Meta Ads in your AI: approval before changes, undo for pauses and budgets, profit after returns.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that brings Meta Ads management into an AI assistant, with approval before changes, undo for pauses and budgets, and profit after returns.

What you can do
  • Manage Meta Ads campaigns from the assistant, including pausing and budget changes.
  • Require approval before changes are applied.
  • Undo pauses and budget adjustments.
  • Report profit after returns.
When to use it
Useful when you manage Meta advertising accounts and want an assistant to inspect and adjust campaigns while keeping a human approval step and a way to reverse changes.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; OAuth authentication is required. No environment variables or headers are declared.
Before you install
It can change live advertising campaigns, including pausing ads and adjusting budgets, which affects real ad spend. Changes are gated by an approval step and can be undone, but review each proposed change before approving. OAuth grants the server access to your Meta Ads account data.

Installation

In SourceWeft

  1. Open Tera 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/co.teraads%2Fconnect/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": {
    "tera-ads": {
      "type": "http",
      "url": "https://teraads.co/mcp"
    }
  }
}

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

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 16, 2026

Score

70% 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