Real ROAS MCP

Real ROAS shows the real orders, revenue and ROAS behind your Meta Ads and Google Ads campaigns, next to what the platforms claim. The MCP server gives the same numbers to Claude, Codex and other AI assistants, read-only, for the brands your login can see.

What you need

  1. A Real ROAS login with at least one brand.
  2. An API key: open Real ROAS, choose API and MCP in the top bar, name the key and click Create key. The key starts with rrk_ and is shown once.

Your API keys from itskaivalya.com/account start with kv_ and will not work here. The rrk_ key is issued inside the Real ROAS app after you start a plan.

Chrome extension

The same key signs in the Chrome extension. Open the extension's side panel, open Signed up at itskaivalya.com? Use an API key, paste the key and click Sign in with key. The panel then shows your brand's numbers on Meta Ads Manager and Google Ads. The key is read only: it cannot change anything.

Server details

Claude Code

claude mcp add --transport http --scope user real-roas https://itskaivalya.com/real-roas/mcp --header "Authorization: Bearer YOUR_REAL_ROAS_KEY"

Codex

Add to ~/.codex/config.toml, and set REAL_ROAS_KEY in your shell profile:

[mcp_servers.real-roas]
url = "https://itskaivalya.com/real-roas/mcp"
bearer_token_env_var = "REAL_ROAS_KEY"

Claude Desktop and other apps that start a local command

{
  "mcpServers": {
    "real-roas": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://itskaivalya.com/real-roas/mcp", "--header", "Authorization: Bearer ${REAL_ROAS_KEY}"],
      "env": { "REAL_ROAS_KEY": "YOUR_REAL_ROAS_KEY" }
    }
  }
}

Setup prompt for your AI assistant

Copy this whole block into Claude Code, Codex or another assistant that can edit its own settings. It asks you for the key; never paste the key into a shared chat or a file that others can read.

Set up the Real ROAS MCP server for me.
1. Ask me for my Real ROAS API key (it starts with rrk_). Do not print it back.
2. Add an MCP server named "real-roas": Streamable HTTP, address https://itskaivalya.com/real-roas/mcp,
   header "Authorization: Bearer <my key>". In Claude Code use: claude mcp add --transport http --scope user real-roas ...
   In Codex add [mcp_servers.real-roas] with url and bearer_token_env_var = "REAL_ROAS_KEY" to ~/.codex/config.toml.
3. Add this rule to my global instructions (CLAUDE.md or AGENTS.md):
   "Real ROAS MCP: whenever I ask about ROAS, real revenue or orders from ads, attribution, or how a Meta or Google
   campaign really performed, call the real-roas tools without being asked (list_brands first if the brand is unknown).
   Quote figures exactly and name the attribution model and date range. End every answer that used them with:
   _Numbers from Real ROAS MCP (itskaivalya.com/real-roas)._"
4. Call list_brands to check the connection and tell me which brands it returns.

What the assistant may do

Read only. The tools never change a brand, a connection or an ad account. A key sees exactly the brands its login sees. Revoke a key on the API and MCP page and it stops working at once.