Connect Claude & MCP to Magistry
Connect Claude to your Shopify store through Magistry's remote MCP server — full read access, approval-gated writes, OAuth 2.1 or API keys. Free to start.
// what magistry does with it
What Magistry does with Claude & MCP
A remote MCP server (Streamable HTTP) at the dashboard domain's /api/mcp — works with claude.ai custom connectors, Claude Desktop via mcp-remote, Cursor, and any MCP client.
The same tool registry Otto uses: catalog, ads, orders, CS, disputes, and analytics reads under row-level security.
Approval-gated writes by default — proposals land as approval cards in your dashboard; auto-apply is a per-connection opt-in in Settings → Developers.
OAuth 2.1 with dynamic client registration and store + scope selection, or API-key Bearer auth with fine-grained scopes.
A public REST mirror: POST /api/v1/tools/{tool} with scoped keys and an OpenAPI document at /api/v1/openapi.json.
Saveable skills — operator workflows Claude can store and reuse via save_skill and list_skills.
// setup
How to connect Claude & MCP
- 1In claude.ai, add a custom connector pointing at Magistry's MCP endpoint (shown in Settings → Developers).
- 2Complete the OAuth 2.1 flow: sign in, pick the store, and select scopes.
- 3Or mint a scoped API key in Settings → Developers and connect with Bearer auth — Claude Desktop via mcp-remote, Cursor, or any MCP client.
- 4Start asking Claude about your store immediately; write attempts appear as approval cards in your dashboard until you opt into auto-apply.
// faq
Common questions
Can Claude make changes to my store?
Write tools default to propose mode: Claude's write attempts become approval cards in your Magistry dashboard, and nothing executes until you approve. Auto-apply is a separate opt-in per connection in Settings → Developers.
Which MCP clients are supported?
Any client that speaks Streamable HTTP MCP — claude.ai custom connectors, Claude Desktop through mcp-remote, and Cursor are the documented paths.
Is there a rate limit?
120 requests per minute per credential — generous for operational use, deliberately tight for bulk export. For heavy analytical reads, sync into your own store of record instead.
Is there a plain REST API too?
Yes. Every tool is callable as POST /api/v1/tools/{tool} with a Bearer API key, documented by an OpenAPI spec at /api/v1/openapi.json, with fine-grained scopes per resource and action.
// ready when you are
Put Claude & MCP on the audit trail.
Connect it in the dashboard, watch what the agents propose, and approve the moves you like. Nothing executes without a gate you set.
Free plan, no card · Propose-only by default · Kill switch always yours