DocsCheckout

Checkout with MCP

Let your agent create a checkout, follow progress, and answer questions.

Add the server

MCP client configuration

{
  "mcpServers": {
    "shopstack": {
      "command": "npx",
      "args": [
        "-y",
        "shopstack-mcp"
      ]
    }
  }
}

The server uses private local Shopstack profiles. Do not put an API key in this configuration.

Select a user profile
Call list_profiles, then use_profile with profile. With no account, use start_signup and poll_signup. A developer uses create_user to create an end-user profile.
For Link, check list_connections before you include payment_provider.
Create and follow
Pass the request fields directly to create_checkout. Use its returned ID for later calls.
poll_checkout · argument shape
```
{
  "checkout_id": "<returned checkout.id>"
}
```
Poll every two seconds for queued, started, and submitting; every five seconds for help_required and approval_required. Stop at a final state.
Answer or hand off
Use send_message for ordinary missing information. If card entry or approval is required, hand the existing checkout ID to a trusted payment interface using the SDK or API.
MCP has no card-entry or payment-approval tool. Do not start another checkout run to handle an existing MCP checkout: that creates a new checkout.

create_checkout: The checkout request fields
Creates one checkout and returns its ID and current state.
poll_checkout: checkout_id
Reads status, activity, intent, required input, approval, and available result.
send_message: checkout_id, content
Answers an ordinary question. Does not approve payment.
cancel_checkout: checkout_id
Requests cancellation before submission.

MCP results include available order and amount facts. Merchant account credentials are removed from the tool result.