Connect Claude & MCP to Magistry
Use Magistry from Claude or any MCP client: a remote MCP server and REST API with OAuth 2.1 or API keys, reads under your access, writes as proposals.
// what magistry does with it
What Magistry does with Claude & MCP
A remote MCP server — works with Claude custom connectors, Claude Desktop, Cursor and any client that speaks Streamable HTTP MCP.
The same tools the dashboard's assistant uses: catalog, ads, orders, helpdesk, disputes and analytics, scoped to the stores you grant.
A 178-operation REST API with an OpenAPI document, the same tools as plain HTTP calls.
Writes arrive as approval cards in your dashboard unless you allowed a connection to apply them.
OAuth 2.1 with store and scope selection, or API keys with fine-grained scopes. Revoking a connection stops its tokens.
// setup
How to connect Claude & MCP
- 1In Claude, add a custom connector pointing at Magistry's MCP endpoint, shown in Settings → Developers.
- 2Sign in, pick the store and select scopes.
- 3Or create a scoped API key in Settings → Developers and connect any MCP client with it.
// faq
Common questions
Can Claude make changes to my store?
Write tools default to proposals: they become approval cards in your dashboard, and nothing changes until you approve. Applying directly is a separate opt-in per connection.
Is there a rate limit?
Yes, per credential: 120 requests a minute by default, set by your plan.
Is there a plain REST API too?
Yes. Every tool is callable over REST with a scoped API key, described by an OpenAPI document.
// 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