Four tools, one brand’s catalog
The MCP endpoint is /mcp on your provisioned API host. Catalog calls use an Authorization: Bearer nxt_… credential scoped to one brand. There is no cross-brand search or multi-brand cart. Use a catalog-scope key, not the admin credential used to operate the console.
| Tool | Job |
|---|---|
| search_products | Find compact cards from a sentence and optional exact filters. |
| get_product | Read variants, prices, availability, policies and the next action. |
| create_checkout | Validate and pay for a variant-level cart when API checkout is enabled. |
| get_order | Read the order resulting from a checkout. |
Search first, then read the product details
Search cards summarize enough information to choose what to inspect next. Price, size and stock phrases are parsed in English and German; explicit filters override inferred values. Attribute filters match recorded values, so missing data needs investigation rather than a confident guess.
The product detail response exposes the variants an agent can actually buy. A product identifier is not a variant identifier. The agent must select the right options and price before constructing a cart.
{
"query": "waterproof running shoes under 150 EUR size 44",
"filters": { "in_stock": true },
"limit": 10
}Set up your MCP client
Add your HTTPS /mcp URL and catalog key to a trusted client that supports remote MCP with bearer authentication. If you’re building the integration yourself, keep the key on the server, not in public browser code.
Siroua uses streamable HTTP and doesn’t require an initialize call before its catalog tools. Try tool discovery and a few calls with the client you intend to use; clients don’t all behave the same way.
You still need to configure the connection in your client. Publishing an MCP endpoint doesn’t automatically add your catalog to Claude or another assistant.
Follow the next action before checkout
Product responses identify the next action. With checkout disabled, that action is open_url for the brand’s product page. With checkout enabled, the agent can call create_checkout using a variant-level cart, buyer details and a delegated payment token supported by the integration.
Send the quoted unit price and reuse the same idempotency key for retries of the same intended purchase. Checkout computes its own total, validates against the current catalog and stores the response for replay. Tool access is not permission to buy without the shopper’s agreement.
Test errors as part of the integration
Test a revoked key, an unknown product, an unavailable variant and an invalid filter. Siroua returns a stable error code and a readable message. Use the code to decide what to do next, and show the shopper a useful explanation. Don’t retry a payment to resolve an account-access error.
Use your deployed API’s tool schemas and OpenAPI documentation when building the integration. The examples here explain how it works; you’ll receive your API host and credentials during setup.
References
Connect your catalog
Join the waitlist and tell us which MCP client you’re using. We’ll help you check the feed and connection.
Join the waitlist