Back to Browse

Roasby MCP Server

by Roasby
Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Manage Google, Microsoft, ChatGPT and Meta Ads safely: previewed, logged, revertible changes.

About

Manage Google, Microsoft, ChatGPT and Meta Ads safely: previewed, logged, revertible changes.

Remote endpoints: streamable-http: https://roasby.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-roasby-roasby": {
      "url": "https://roasby.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Roasby

skills.sh

Roasby lets you manage Google Ads, Microsoft Ads, ChatGPT Ads and Meta Ads by talking to your AI assistant. Ask how your campaigns are doing, find searches that waste money, and make changes after a preview of exactly what will happen.

You need a Roasby account with at least one connected ad account. This repository is the Roasby plugin for Claude, Codex, ChatGPT and Cursor, and the skills for any assistant that reads Agent Skills.

Install

Claude Code

/plugin marketplace add Roasby/roasby
/plugin install roasby@roasby

Codex

codex plugin marketplace add Roasby/roasby
codex plugin add roasby@roasby

Cursor: add the Roasby MCP server, or install the plugin from the Cursor marketplace.

Skills only (any assistant that reads Agent Skills):

npx skills add Roasby/roasby

The skills need the Roasby connection to work, so add the MCP server too.

Claude.ai, Claude Desktop, ChatGPT and any other MCP client: add a custom connector with the URL https://roasby.com/mcp. You sign in to Roasby with OAuth when you first use it. The setup guide has the steps for each assistant.

What this plugin contains

  • A connection to the Roasby MCP server at https://roasby.com/mcp. You sign in with OAuth when you first use it.
  • Skills for your assistant:
    • working-with-roasby: how to use the Roasby tools safely (read freely, preview every change, wait for your yes), with detailed guides it reads when needed.
    • roasby-wasted-spend-audit: find spend without conversions and cut it with negative keywords and pauses.
    • roasby-weekly-review: a review of the week across platforms, with suggested next steps.
    • roasby-launch-search-campaign: plan and create a search campaign, created paused.
    • roasby-budget-and-bid-check: where more budget or higher bids would help, within your guardrails.

What it connects to and sends

The plugin connects only to https://roasby.com/mcp. It runs no local code, has no hooks and stores nothing on your computer. What you ask your assistant to do with your ads goes to Roasby, which reads from and writes to the ad accounts you connected. The privacy policy explains how Roasby handles that data.

How changes stay safe

  • Reading is free. Every change takes a preview first, then your confirmation.
  • Everything Roasby creates starts paused.
  • Nothing is ever deleted from your ad accounts.
  • Budget and bid changes stay within guardrails that only people can set.
  • Every change is logged, and most can be reverted.

Limitations

  • Roasby never deletes anything from your ad accounts: it pauses instead.
  • Guardrails, connecting ad platforms, billing and account settings are set by people in Roasby on the web. When only you can do something, your assistant tells you what to do and where.
  • A new search campaign is built whole from one blueprint (up to 1,000 ad groups with keywords, negative keywords and up to 3 ads each, and its own negative keywords, within 10,000 operations) and targets whole countries; a larger one is created in parts. Ad groups (with their keywords, negative keywords and up to 3 ads) can be added to an existing search campaign, and keywords and responsive search ads (with pinned headlines if you want) to an existing ad group (always paused), and a search campaign's settings (countries, search partners, tracking, ad schedule, device bid adjustments, ad rotation, Microsoft Ads languages) can be changed within the max bid change, the text of responsive search ads (headlines, descriptions, pins, display paths, final URL) can be edited in place, one ad at a time or by find and replace, and a keyword's text and match type can be changed (by a replace on Google Ads: the new keyword is added paused and the old one paused; a match type in place on Microsoft Ads), as can its own final URL, but Roasby can't yet edit other ad types or assets. Keyword research gives live estimates from Google Ads and Microsoft Ads.
  • A search campaign's conversion goals and its own bidding strategy and targets (manual CPC, maximize clicks, maximize conversions with a target CPA, maximize conversion value with a target ROAS, target impression share) can be changed, with targets within the guardrails you set and the max bid change; portfolio strategies and bidding Roasby could not put back are changed in the ad platform, and Roasby never creates custom conversion goals.
  • Some platforms can't do everything: for example, Microsoft Ads has no broad match negative keywords, and ChatGPT Ads and Meta Ads have no keywords.
  • Sitelinks, callouts, structured snippets and the other text assets can be added to an ad account, search campaign or ad group and paused or enabled: on Google Ads each is linked paused; Microsoft Ads has no paused links, so Roasby links new ones only to a paused campaign or ad group, and pausing one there takes the link away (the asset stays). Images, logos and business names are not added yet, and an asset's text is not edited.
  • Roasby answers from a synced copy of your data, refreshed on a schedule or when you ask. Keyword Quality Scores and bid estimates are missing when the platform has too little data or (estimates) under automated bidding; your assistant then says so instead of guessing.
  • One connection reaches every workspace you belong to. Your assistant works in your current workspace unless you name another, and can change ads only where your role allows it.

See every limitation by platform.

Example prompts

  • "How did my ads do in the last 7 days?"
  • "Find wasted spend and suggest negative keywords."
  • "Pause the Brand campaign."
  • "Add these 20 keywords as phrase match to the Running shoes ad group."
  • "Add trail, road and kids ad groups to the Running shoes campaign, each with its keywords and an ad."
  • "Add a second ad to the Trail ad group, with our brand name pinned as the first headline."
  • "Which workspaces can you see? Show me last week's spend in the Agency workspace."

Support

Read the docs or email support@roasby.com.

This repository is generated from Roasby's private source, so changes made here are overwritten.

Reviews

No reviews yet

Be the first to review this server!