01
MCP for AI clients
Connect Claude or any MCP client to /api/mcp. Two protocol revisions are supported, and the client sees the tools its grant allows.
// developer platform
An MCP server and REST API for the business.
The tools behind Ask Magistry are open to your own code and AI clients: a 181-operation API over MCP and REST, with OAuth 2.1 or API keys. Every operation is tagged as a read, an automatic write or a proposed write, and a proposed write waits for a person to approve it.
Live181 operations: 103 read, 44 automatic write, 34 proposed writeCounted 18 Oct 2026
// what you get
The same tools the product uses, with the same limits.
02
REST with an OpenAPI document
Every tool is also a REST operation under /api/v1/tools, described in a published OpenAPI document with its scope and risk tier.
03
OAuth 2.1 or API keys
Authorization code with PKCE for apps that act for a user, and API keys for your own scripts. Revoking a grant stops every token issued under it.
04
An app acts as an app
A third-party app reaches only the stores it was granted, and only writes if write access was granted. It never gets more than the user who installed it.
05
A contract with notice
Operations are supported for 365 days after a removal is announced, with Deprecation and Sunset headers on every affected response.
06
Outbound events
Signed webhook deliveries in CloudEvents format, with an AsyncAPI description. Not every event type publishes yet; the event catalog marks which do.
// get going
Connect, call, approve.
// 01 · connect
Create an API key in Magistry, or point your MCP client at /api/mcp and sign in with OAuth.
// 02 · call
Read orders, products, campaigns and customer threads, or call a tool that writes, within the scope you granted.
// 03 · approve
Proposed writes arrive as approval cards in Magistry, and nothing changes until a person approves. Every call is logged.
// get started
One API for the whole business.
Read the API reference, or start free and create a key.
MCP + REST · OAuth 2.1 · 365-day support window