Skip to main content
The MerchantOps MCP server is a remote, read-only Model Context Protocol server. Connect it to an MCP client (Claude Desktop or Claude Code) and ask questions about your catalog in natural language — products, variants, pricing, and publish status. All access is scoped to your organization via OAuth; the server performs no writes.
Server URL: https://mcp.merchantops.ai/mcp  ·  Transport: Streamable HTTP  ·  Auth: OAuth 2.1 (sign in with your MerchantOps account)

​
Connect

1

Open connector settings

Settings → Connectors → Add custom connector.
2

Add the server

Name it MerchantOps and enter the URL:
3

Authenticate

Click Connect. A browser window opens to sign in with your MerchantOps account and authorize access. After consent you’re returned to Claude and the MerchantOps tools appear.

​
Authentication & access

The server authenticates you with OAuth using your MerchantOps account — you don’t create or paste an API key to connect it. Access is scoped to your organization automatically, and the server is read-only, so connecting it changes nothing: it can answer catalog questions but cannot alter data. Read-only is a guarantee about writes, not about interpretation. Some tools return raw records that need reading carefully — see the caveat on get_product_pricing below — so treat an agent’s answer as a starting point to confirm in the dashboard, not as a final one.
The Settings → API Keys page in your dashboard manages a separate kind of credential — server API keys for direct API access or customer-run workers — and is unrelated to connecting this OAuth-based MCP server. You never paste an API key into an MCP client.
After connecting, ask Claude to run whoami to confirm which account and organization it’s operating as.

​
Available tools

All tools are read-only and scoped to the authenticated member’s organization.
get_product_pricing returns raw price-record history, not “the current price.” It returns the product’s price records in every status — draft, active, expired, and superseded — and of every price type (MAP, MAP stepdown, sale, and so on), mixed together and ordered newest- created first, which is not the same as newest-effective. There is no date filter, and the result is capped at the 100 most recently created records, so a product with a long pricing history may not show its oldest records at all.To identify the price that is actually live, you (or the agent) must read each record’s status, price_type, and effective_from yourself. Treat the answer as a working list to verify in Price records, not as an authoritative current price.

​
Example prompts

​
Troubleshooting

Make sure pop-ups/redirects aren’t blocked, then retry the connection. In Claude Code, re-run /mcp and re-authenticate. MCP clients cache the tool list — fully reconnect the connector to pick up changes.
Results are scoped to your organization. Run whoami to verify you’re signed in as the expected member and org. If the org is wrong, sign out of the connector and reconnect with the right account.
Confirm the URL is exactly https://mcp.merchantops.ai/mcp (with the /mcp path). This is the only address the server advertises as its protected OAuth resource, so a connector still pointing at an older hostname can fail authorization even though that hostname answers. Remove the old connector and re-add it with the URL above. If problems persist, contact your MerchantOps admin.