MCP (Model Context Protocol) Beta

Commerce MCP connects your affiliate data, campaigns, and products directly to your AI tools.

Create content, analyze performance, or optimize monetization — all through natural language. Whether you’re a developer or creator, Commerce MCP turns complex affiliate data into conversation-ready insights.

Quickstart

Add the Commerce MCP Server to your AI client once — and your assistant instantly gains tools for affiliate search, reporting, and link generation.

Step 1: Configure your client

Use this configuration in your MCP setup file:

{
  "mcpServers": {
    "Commerce MCP Server": {
      "url": "https://mcp.sovrn.com/commerce",
      "headers": {
        "Authorization": "secret {SECRET_KEY}"
      }
    }
  }
}
❗️

Authorization

To use the Commerce MCP, include a Secret Key in the Authorization header of your request. The header must be formatted as:

"Authorization": "secret {SECRET_KEY}"

Ensure that the word secret is followed by a space before the key itself.

For details on generating a Secret Key for your site, visit our Authorization guide.

Step 2: Restart your client

Once saved, restart Cursor, Claude Desktop, or your chosen client. The client will automatically detect and register the Commerce MCP tools.

Step 3: Try a simple request

Example request:

Use one of my campaigns to create a quick price comparison guide for the iPhone 15.

Rate Limiting

Rate limits are enforced by the underlying Sovrn Commerce APIs, not by the MCP server itself, and may differ between tools depending on data type and endpoint capacity.

General guidance

  • Reporting and transaction tools (for example, trx_Transactions, trx_Merchants, trx_Links) are typically limited to 1 request per 60 seconds.
  • Search and recommendation tools (for example, comp_search_prices, rec_recommend_products) allow higher throughput, often supporting multiple requests per second depending on the endpoint.
  • Limits are per tool, not global across the Commerce MCP service.

Recommendations

  • Handle too many request responses by retrying after a short delay or using exponential backoff.
  • Space repeated calls to the same tool to prevent throttling.
  • When batching data retrieval across several tools, apply rate-limiting logic individually per tool.

If you require precise rate limits for a particular API, refer to that API’s documentation or the Sovrn Developer Center for the corresponding service.


Resources, Tools and Prompts

Each MCP tool represents a callable endpoint that can be executed by your AI client through natural language or structured JSON requests.

Tool NameDescriptionCategory
comp_search_pricesSearch affiliated product pricesTool
link_check_linkValidate or convert merchant URLs into affiliate linksTool
rec_recommend_productsReturn related or recommended productsTool
trx_TransactionsRetrieve detailed transaction-level dataTool
trx_MerchantsAggregate reporting by merchantTool
trx_Merchants_By_DateMerchant-level performance grouped by dateTool
trx_LinksTransaction data grouped by linkTool
trx_PagesTransaction data grouped by pageTool
trx_MerchandiseProduct-level transaction and revenue dataTool
trx_SourcesTransactions grouped by traffic sourceTool
trx_NetworksTransactions grouped by networkTool
trx_CUIDsClick or user-level analytics and attributionTool
setup_commerce_workflowInitialize the Commerce MCP workflow environmentPrompt
get_campaignsRetrieve active campaigns and metadataResource

Demo Prompts

For full examples of how to use the Commerce MCP tools together, see our Demo Prompts.

Demo workflows include:

  • Affiliate Link Tools
  • Price Comparison Guides
  • Seasonal Shopping Guides
  • Product Roundups
  • Deal Alerts
  • Transaction Reporting
  • Conversion Optimization

Each demo illustrates the sequence of tool calls, example prompts, and expected output structures.


Troubleshooting

IssueLikely CauseResolution
UnauthorizedInvalid or missing API keyVerify authorization header format
No tools visibleMCP configuration syntax errorCheck JSON formatting and restart client
Empty responseMissing required date or filter parameterInclude at least one valid date field
Rate limit triggeredMore than one call per 60 secondsApply delay between transaction calls


What’s Next