Connect
1
Add a custom connector in Claude
On an individual plan, open Customize → Connectors, click + Add and choose Add custom connector. Enter Shoppex as the name and
https://api.shoppex.io/mcp as the URL. Finish the setup, click Add, then Connect.On a Team or Enterprise plan, ask an Owner or Primary Owner to first add Shoppex in Organization settings → Connectors with https://api.shoppex.io/mcp as the URL. Once added, each member opens Customize → Connectors, finds Shoppex and clicks Connect, then approves access in the next step. See Claude’s custom connector instructions.2
Approve in Shoppex
Claude opens the Shoppex OAuth consent page. Sign in, pick the store and click Allow Access to approve the connection once. You need the permission to manage API keys.
3
Ask Claude
Back in Claude, ask about your store. Claude asks you before it runs a tool that changes data.
What Claude can do
Claude has no tool that issues refunds or pays money out. Do those in the dashboard. The connector also cannot credit customer wallets. A local MCP server can, when its API key has the
customers.write scope.
Access and safety
- The connection works for one store: the one you picked on the consent page. Connect again to add another store.
- Every change is live right away, like a change you make in the dashboard. Claude marks each tool as read-only or as a change, and asks before changes.
- Calls count against your Developer API rate limit and appear in the request log under Settings → Developer → Logs.
- Disconnect any time under Settings → Developer → API Keys → Connected Apps. Access ends immediately.
- If the person who connected Claude leaves your team, the connection stops working.
Local MCP servers
Prefer an API key and a local server? The@shoppexio/mcp-shoppex package runs the same tools over stdio for Claude Code, Cursor and other MCP clients. See Editing with AI.