ASA Condor

com.asacondorPublished by asacondor.comOfficial publisherv1.0.0Updated Oct 24, 2026

Run Apple Search Ads from Claude: performance, recommendations, keywords, budgets, launches.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant run Apple Search Ads campaigns — performance, recommendations, keywords, budgets and launches — from Claude.

What you can do
Review Apple Search Ads performance data and account metrics through the assistant. Get campaign recommendations and act on them. Manage keywords and adjust budgets. Launch and run Apple Search Ads campaigns without leaving the conversation.
When to use it
Useful when you manage Apple Search Ads and want to check performance, apply recommendations, tune keywords and budgets, or launch campaigns conversationally instead of through the ads console.
Requirements
A remote endpoint at app.asacondor.com reached over streamable HTTP; OAuth authentication is required, so an ASA Condor account and an Apple Search Ads account connection are implied. No environment variables or headers are declared.
Before you install
The server can change live advertising: budgets, keywords and campaign launches may spend real money. It requires OAuth sign-in and connects to your Apple Search Ads account, so review any action before it is applied and confirm what data is shared with the provider.

Installation

In SourceWeft

  1. Open ASA Condor 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.asacondor%2Fasa-condor/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": {
    "asa-condor": {
      "type": "http",
      "url": "https://app.asacondor.com/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. v1.0.0LatestOct 9, 2026

Score

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

    Publish an icon in the registry entry.

  • 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.