DocumentationMCP Access

MCP Access

Revenuealot MCP lets approved AI clients query your Revenuealot tools through a remote MCP server. The current MVP focuses on managed Bearer keys, read-only marketplace data access, and plan-aware permissions.

MCP access is available on Starter and above. Each MCP client can only use tools allowed by your current plan and organization permissions.

What MCP Can Do

The MCP server exposes read-only tools for common operating questions:

  • Store discovery across connected platforms
  • Takealot keyword research, keyword reverse lookup, product research, store analytics, and returns risk
  • Amazon store metrics, product analytics, products, orders, keyword reverse, and ads performance
  • Makro store metrics and product analytics
  • Shopify product data
  • Supplier product data

Create an MCP Key

Open MCP Keys

Go to Dashboard → Settings → MCP Keys.

Create a Key

Click Create key, enter a clear name such as Claude Desktop or Operations Agent, and optionally choose an expiry date.

Copy the Key Once

After creation, Revenuealot shows the full key one time. Copy it immediately and store it in the environment variable used by your MCP client.

Manage Active Keys

You can edit the name or expiry, disable a key temporarily, or delete it permanently from the same page.

Connect an MCP Client

Use a client that supports remote MCP over Streamable HTTP and manual Bearer tokens.

<MCP_KEY> means the Revenuealot MCP key you created and copied in the previous section. When configuring a client, replace <MCP_KEY> with the full key value and do not keep the angle brackets.

Open the Codex app, then go to Settings → MCP Servers → Add Server and add Revenuealot MCP. Choose Streamable HTTP as the type, set the URL to https://api.revenuealot.com/mcp, then add Authorization in Headers with the value Bearer <MCP_KEY>.

Codex MCP server setup

⚠️

Do not paste an MCP key into shared prompts, documents, code repositories, or screenshots. Treat it like an API secret.

Security Notes

  • Create separate keys for separate clients or team workflows.
  • Use expiry dates for temporary assistants or trials.
  • Disable a key first if you want to pause access without losing the record.
  • Delete a key if it may have been exposed. Deleted keys cannot be recovered.
  • Organization admins can review organization-level keys when permitted.

Troubleshooting

The client cannot connect
Confirm that the URL is https://api.revenuealot.com/mcp, the transport is Streamable HTTP, and the request includes Authorization: Bearer <MCP_KEY>.

The tool list is empty or incomplete
Check your current plan and team tool permissions. MCP tool availability follows the same access rules as Revenuealot.

A key stopped working
Check whether the key is disabled, deleted, expired, or no longer covered by your current plan.

Next Steps