AGENT & DEVELOPER PREVIEW · COMING SOON

Shopify order editing
for your AI support team.

Alfred Order Edits includes a native Model Context Protocol (MCP) server and a REST API. Give your support tools the policy, context and safe next step for an order change, while your customer stays in control.

Join the launch waitlist Read the plain-text reference →

This is a prelaunch reference. Connect after installing Alfred Order Edits when it becomes available; the marketing website is not an authenticated MCP endpoint.

FIVE TOOLS, ONE POLICY

What your agent can actually do.

The same tools are available over REST and MCP. Tool access is enforced by Alfred, using the key's trust level.

get_edit_policy

Explain the policy

Read the store's editing window, allowed changes and payment rules in plain language.

Inputs: No inputs: {}
Read-only key: Available
Link-only key: Available

get_edit_options

Check this order

Check eligible changes, the closing time and a suggested reply. A link-only key can also trigger an eligible edit-link email.

Inputs: order_number, customer_email; optional action
Read-only key: Check only; no email
Link-only key: Check and email an eligible link

create_edit_link

Send the safe next step

Have Alfred email an action-specific link to the order's own address. The URL is never returned to the agent.

Inputs: order_number, customer_email, action
Read-only key: Not available
Link-only key: Email link to the order's address

preview_edit

Preview the outcome

Price a proposed change, including the resulting total, refund or balance. No order change is committed.

Inputs: order_number, customer_email, change
Read-only key: Available
Link-only key: Available

get_edit_history

Understand what happened

Read past changes, who made them and their timing. Address details are excluded from the response.

Inputs: order_number, customer_email
Read-only key: Available
Link-only key: Available

THE BOUNDARIES ARE PART OF THE PRODUCT

Helpful access.
A clear scope.

Read or link. No order writes.

Read-only keys check policy, eligibility, previews and history without emailing a link. Link-only keys can also ask Alfred to email one. Neither level commits an order change or changes your settings.

The link goes to the customer.

Order tools require an order number and matching customer email. Alfred sends the edit link only to the order's own email address. The agent receives a send result, never the link URL.

Keys you control.

Create store-scoped agent keys in Agents and API. Keys are shown once and stored as hashes. Trust levels are checked on each call; you can revoke a key or disconnect an agent.

Every tool call is audited by tool, outcome, order and timing; request and response bodies are not stored. Current limits are 60 calls/minute and 2,000/day per key, plus 3 link emails per order per day across keys. Limits may change before launch.

CHOOSE THE INTERFACE YOUR TOOL SUPPORTS

Native MCP. Straightforward HTTP.

Use an MCP client that supports Streamable HTTP and Bearer-token authentication, or configure an HTTP action in your helpdesk. Both routes use the same merchant rules and safeguards.

MCP

POST https://YOUR_ALFRED_APP_HOST/mcp
Authorization: Bearer YOUR_ALFRED_AGENT_KEY

Stateless Streamable HTTP with JSON responses. tools/list exposes the tools allowed by your key; tools/call runs them. No SSE stream or session lifecycle.

REST

POST https://YOUR_ALFRED_APP_HOST/api/v1/get_edit_options
Authorization: Bearer YOUR_ALFRED_AGENT_KEY
Content-Type: application/json

Send the tool's inputs as a JSON body. Use the real app host and your agent key after installation; these are placeholders, not working credentials.

Example MCP tool parameters

{
  "name": "get_edit_options",
  "arguments": {
    "order_number": "#1042",
    "customer_email": "customer@example.com",
    "action": "address"
  }
}

Illustrative result excerpt

{
  "can_edit": true,
  "link_sent_to_order_email": true
}

For an eligible order with a link-only key, the agent tells the customer to check the inbox for their order. The customer then makes and confirms the change.

THE DETAILS THAT MATTER

Agent & MCP questions.

What is the difference between the Agent API and MCP?

They expose the same five tools and use the same policy checks, Bearer-key authentication, trust levels, rate limits and call auditing. REST uses POST /api/v1/<tool>. MCP uses POST /mcp with stateless Streamable HTTP and JSON responses.

Does the agent receive the customer's edit URL?

No. Alfred emails links directly to the order's own email address. The agent receives link_sent_to_order_email and a suggested reply, so it can tell the customer to check their inbox. Read-only keys never trigger a link email.

Can the agent modify an order or merchant settings?

No. v1 tools can read, preview and request an edit-link email. They do not commit order changes, issue refunds themselves or change store settings. The customer confirms the actual change on the storefront edit page.

Which support tools can connect?

Use an MCP client that supports Streamable HTTP with a Bearer token, or an HTTP-based support action that can call the REST API. A Gorgias AI Agent HTTP action is documented in the app's setup guide. A dedicated Gorgias sidebar app is not part of v1; test your chosen client's authentication and action setup before launch.

Your store policy. A secure handoff. Customer confirmation.

Get Order Edits launch updates