Overview

Moloco Ads MCP is a Model Context Protocol (MCP) layer placed over the existing Moloco Ads APIs that lets advertisers interact with reporting, diagnostics, and campaign analysis workflows through conversational AI tools instead of manual dashboard and spreadsheet workflows.

These guidelines are intended for the initial alpha phase, which is scoped to read-only access for a small set of customers rather than a public launch.

What you can do in the alpha

In the read-only alpha, Moloco Ads MCP is intended primarily for:

• Performance reporting and campaign summaries
• Troubleshooting performance drops and delivery issues
• Monitoring multiple accounts and pacing risks
• Reviewing creative status and creative performance signals
• Automating recurring report generation and exports

What is not supported in the alpha

The alpha does not support MCP-originated write operations. High-stakes workflows remain out of scope for now, including ad account deletion or modification, SKAN configuration changes, destructive campaign deletion, and product-level configuration management.

Prerequisites

• A Moloco Ads account that has been approved for the alpha, with your Moloco credentials ready for the browser-based OAuth sign-in.
• Valid account access to the advertiser accounts you expect to query.
• A Claude plan or workspace that allows custom connectors. For Team or Enterprise workspaces, the admin owner may need to add the connector for the organization before individual users can connect.

The steps below use OAuth, which is our recommended way to connect for data security, as no key is stored in your device during sign in. If you'd rather connect using a Moloco Ads API key instead, see Connect with an API key instead.

Choose an MCP-compatible client.

• Claude Desktop — the desktop app; add a custom connector, no developer tools needed.
• Claude Code — the CLI, for engineers.

Initial setup

Claude Desktop

Claude Desktop connects to the remote server directly and completes OAuth in your browser — no extension or API key is needed.

1. Open Claude Desktop.
2. Go to Customize > Connectors.
3. Click +, then choose Add custom connector.
4. Enter Moloco Ads as the connector name and https://mcp.moloco.cloud/mcp as the remote MCP server URL.
5. Leave OAuth Client ID and OAuth Client Secret blank unless Moloco IT or the connector owner gives you specific values.
6. Click Add, then click Connect and complete the OAuth flow in your browser (see Complete OAuth and verify).

If custom connectors are blocked

Some organizations restrict custom connectors. If you cannot add or connect the Moloco Ads connector, send IT the details below.

If you can't use a custom connector at all, connect with the manual config fallback (API key) instead.

Claude Code

Claude Code supports remote HTTP MCP servers natively and handles OAuth for you — no API key or bearer header is needed.

1. Open a terminal.

2. Add the Moloco Ads remote MCP server using HTTP transport:

   Bash

   claude mcp add --transport http moloco-ads https://mcp.moloco.cloud/mcp

3. Start or return to an interactive Claude Code session.

4. Run /mcp and select the Moloco Ads server when prompted.

5. Choose the authentication option, then complete the browser OAuth flow (see Complete OAuth and verify).

Complete OAuth and verify

1. In the browser window, sign in with your Moloco account.
2. Approve the requested access if the details look correct.
3. Return to Claude Desktop or Claude Code.
4. Confirm the connector shows as connected. In Claude Code, the success message should say Authentication successful. Connected to moloco-ads.

Then open a new chat and ask: "Is the Moloco MCP connected?" or "What tools do you have in Moloco Ads MCP?" to confirm the tools are available.

Connect using an API key instead

OAuth is recommended, but you can still connect using a Moloco Ads API key.

You will need a Moloco Ads API key for your workplace. To learn how to get one, see the Cloud API authentication docs. Given that the MCP is read-only, we strongly recommend issuing a read-only key. The API key works the same way as a password; it grants read access to everything your workplace can see.

For Claude Code, register the server with your key as a bearer header:

claude mcp add --transport http moloco-ads https://mcp.moloco.cloud/mcp \
  --header "Authorization: Bearer <YOUR_CLOUD_API_KEY>"

Then restart Claude Code (the tool list is loaded at session start) and verify with claude mcp get moloco-ads (expect ✓ Connected).

Few things to note:

• The registration is scoped to the directory you ran the command in. Add --scope user to make it available everywhere.
• The header value lands in Claude Code's local config in plain text; to avoid this, prefer the env-var form: --header "Authorization: Bearer \${MOLOCO_API_KEY}" with the variable exported in your shell.
• To rotate your API key (or remove the server), use claude mcp remove moloco-ads, then claude mcp add … again with the new key. There is no claude mcp update.

For Claude Desktop, note that Claude Desktop can't attach an API key to a remote MCP server on its own, so use the manual config fallback in the troubleshooting guide.

Recommended first workflows

Daily performance review

Use Moloco Ads MCP for fast daily summaries when you want to understand yesterday’s spend, ROAS, and campaigns that need attention.

Suggested prompts:

• Summarize yesterday’s spend and ROAS by campaign.
• Which campaigns dropped below target CAC?
• Compare Moloco performance vs TikTok for Android installs.

Campaign troubleshooting

Use troubleshooting workflows when performance drops and you need to check creatives, tracking links, delivery anomalies, or recent changes.

Suggested prompts:

• Why did installs decline on Campaign A?
• Did any creatives fail review?
• Were tracking links broken?
• Show delivery anomalies from the last 7 days.

Multi-account monitoring

Agency and portfolio users can use MCP to identify which accounts need attention instead of checking accounts one by one.

Note: We currently don't support multi-workplace access. The MCP only works for the single workplace you authenticate to.

Suggested prompts:

• Show accounts with declining ROAS.
• Which advertisers overspent yesterday?
• Summarize pacing risks across all accounts.

Creative and review monitoring

Use MCP to spot rejected creatives, review bottlenecks, and creative groups that need operational attention.

Suggested prompts:

• Show rejected creatives.
• Which creative groups have the highest CTR?
• List creatives pending review for over 24 hours.

Reporting automation

Use conversational workflows when you want recurring summaries or exports without manually pulling reports from Moloco Ads Manager.

Suggested prompts:

• Generate a weekly executive summary.
• Export campaign performance grouped by geo.
• Create a report comparing spend efficiency week over week.

Best practices for alpha users

• Start with read-only analysis questions, since that is the intended first-phase usage model.
• Use specific campaign, timeframe, and KPI language in your prompts to reduce ambiguity and make diagnostics more actionable.
• Treat the output as decision-support, not autonomous decision-making.
• If an answer looks incomplete, follow up with narrower diagnostic prompts such as asking about creatives, tracking links, or change history separately.

Next steps

• Tools reference — the full catalog of read tools the server exposes, grouped by family.
• Troubleshooting — common errors (OAuth sign-in, connector approval, API keys, rate limits) with fixes.
• Manual config fallback — connect with an API key in a config file, e.g. if you can't use a custom connector.