Competiprice
← Back to the blog

Connect Claude or Codex to Competiprice

Connect Claude, Codex or another MCP client to Competiprice. List your products, retrieve price history and set your first alert with the right permissions.

Method 4 min read

Have your Competiprice account ready. Pick a product you already monitor so you can check the first result. Copy the server URL below into your agent.

https://www.competiprice.com/mcp

Choose your client. Claude · Codex · Other MCP clients.

Claude on the web or in Claude Desktop

  1. Open Customize → Connectors in Claude and add a custom web connector. Name it Competiprice and paste the server URL. In a team workspace, someone with permission to manage connectors must first add it to the organization.
  2. Select OAuth. If Claude offers a choice of OAuth client identities, choose Register automatically. Save the connector and select Connect.
  3. Sign in to Competiprice. Select the permissions to list monitored products and compare offers, then confirm. In the Claude conversation, enable Competiprice in the connectors menu if needed.
Try in Claude
“Use Competiprice to list five products I monitor. Pick the first one with a competitor URL and compare its offers. Include the price, availability, link and observation time for each one.”

Using Claude Code in a terminal? Add the server with the command below. Then open /mcp inside Claude Code, select Competiprice and authenticate. Claude connector guide · Claude Code documentation.

claude mcp add --transport http competiprice https://www.competiprice.com/mcp

Codex

In your terminal, register the server once. The second command opens the OAuth flow for read and write access. If the server is already registered, go straight to the second command.

codex mcp add competiprice --url https://www.competiprice.com/mcp
codex mcp login competiprice --scopes monitoring:read,monitoring:manage

If you registered the server under a different name, find it with codex mcp list and use that name in place of competiprice. On the Competiprice consent screen, select the actions you need. For this example, enable the permissions to list monitored products and read historical observations. You can leave every write switch off. Codex MCP documentation.

Try in Codex
“List my monitored products and their IDs. For the first product with observations, show the prices recorded over the last seven days in chronological order. Include the observation date and URL.”

Other MCP clients

  1. Add a remote MCP server, choose Streamable HTTP as the transport and paste the Competiprice server URL shown above.
  2. Select OAuth with server discovery and dynamic client registration (DCR). Request monitoring:read to read data. Include monitoring:manage if you want to select write actions during consent.
  3. After authorization and MCP session initialization, call tools/list. If you enabled the permission to list products, the response includes list_products. A client that accepts JSON-RPC messages can now send this request.
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {"name": "list_products", "arguments": {"limit": 5}}
}

Find a product_id in items. To retrieve history, use that ID in the arguments to product_history. Replace the example IDs below with IDs from your own account. The agent needs permission to read historical observations.

SelectionArguments for product_history
One product{"product_ids": 42, "limit": 10}
Several products{"product_ids": [42, 57], "limit": 10}
The whole catalog{"product_ids": "*", "limit": 10}

Try an alert or an export

To create an alert, enable the permissions to compare offers, create alerts and list alert rules. Ask, “Compare the offers for [my reference]. Show the URLs and their IDs.” Pick one, then ask, “Create a 5% price drop alert for URL [chosen ID]. List the rules for this product so I can check the threshold.”

To export observations as CSV, enable the permissions to export monitoring data and read historical observations. Ask, “Export the last seven days of observations for my products as CSV.” A client can start with export_stats, section observations and format csv. For a full export of all authorized sections, start with {"format":"csv"} and follow next_arguments until it returns null.

If a tool is missing or a report has to wait

Open the agent in Settings → AI agents and check its switch for the action. Greyed-out write switches indicate a read-only connection. Reconnect the client with monitoring:manage, choose the actions you want and refresh the tool list. Manage my agents.

Between report pages, wait the number of seconds in next_report_after_seconds. If the server returns HTTP 429, wait for the Retry-After interval before retrying the same request. See limits by plan.