Connecting from Claude on the Web

No terminal needed — add StoreOps as a connector right on claude.ai (or in Claude Desktop). Once added, the same connector works in the mobile app on the same account.

Before you start

• A StoreOps connection token (see AI Assistant Connection).
• A paid Claude plan: custom connectors require Pro/Max (personal) or Team/Enterprise (organization).

Adding the connector (Pro / Max personal plans)

1. Open claude.ai and go to Settings → (Customize) Connectors, or visit claude.ai/directory and click Add custom in the top-right corner.
2. Click Add custom connector.
3. Name: StoreOps. Remote MCP server URL: https://your-storeops-url/api/mcp.
4. Authentication: choose None — StoreOps authenticates with the token, not OAuth.
5. Open Request headers:
   • pick authorization as the header name
   • enter Bearer sop_your-token as the value — the Bearer prefix and its space are required; Claude sends the value exactly as typed, and the server rejects it without the prefix.
6. Save, then enable StoreOps under the + menu → Connectors in the chat input, and start asking about your numbers.

Don't see a Request headers section?

Request headers are in beta and rolling out gradually. If the dialog has no such section, your account can't enter the token on the web yet — use the one-line Claude Code command instead; the result is identical.

Team / Enterprise plans

1. An Owner goes to Organization settings → Connectors, clicks Add → Custom (choose Web if asked for a type).
2. Same fields as above; the admin enters the token once and the whole organization shares it.
3. Members then go to Customize → Connectors, find StoreOps labeled "Custom", and click Connect.

Suggestion

For a shared org token, give it a clear label in StoreOps (e.g. "Company Claude Team — shared") so you know which one to revoke later.

Things to know

• Authentication settings (request headers) can't be edited after saving — to rotate the token, remove the connector and add it again.
• Web connections come from Anthropic's cloud servers, not your computer. If your StoreOps sits behind an IP allowlist, allow Anthropic's range (160.79.104.0/21).
• Anything the connector completes is still written to the StoreOps audit log. Calls refused by the token's own limits or as web-only never touch your data and leave no record; ones refused for insufficient permission or a closed period do leave one.

What about other AI platforms?

• ChatGPT: with Developer mode enabled you can add custom MCP connectors, but authentication is limited to OAuth or none — there is nowhere to enter a fixed token, so it can't connect to StoreOps yet.
• Cursor, opencode, Hermes and other tools with custom-header support: see the examples in AI Assistant Connection.