🧺 Ironing Hero — MCP Server

Model Context Protocol · protocol 2025-06-18 · Streamable HTTP · JSON-RPC 2.0

This is a remote MCP server. AI agents (Claude Desktop, Cursor, any MCP client) can connect with a Bearer API key to submit and track laundry orders on behalf of an Ironing Hero customer account.

Endpoint: https://mcps.srv.ironinghero.com/
Discovery (no auth): /.well-known/mcp.json

Connect (Claude Desktop / Claude Code)

{
  "mcpServers": {
    "ironing-hero": {
      "type": "streamableHttp",
      "url": "https://mcps.srv.ironinghero.com",
      "headers": { "Authorization": "Bearer mcp_YOUR_KEY" }
    }
  }
}

Quickstart (curl)

curl -s -X POST https://mcps.srv.ironinghero.com \
  -H "Authorization: Bearer mcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

Tools

Tool	Description
`list_services`	List the laundry service types this MCP server can create orders for, with pricing unit (per kg / per piece / catalog) and current rates from business rules. Call this first to know what to offer and how to price.
`list_stores`	List laundry stores the customer can order from, with id, name, city and address. Use the returned id as storeId when creating an order or requesting a quote. Optionally filter by city name (case-insensitive).
`get_quote`	Estimate the price and planned deposit for a laundry order before creating it. Provide storeId + serviceType, then either weightKg (for per-kg services like wash_dry) or itemsCount (for per-piece services like iron). For catalog services (dry_clean, wash_dry_iron) you may pass an itemKey to price a specific item; without one, the available catalog items are returned.
`create_order`	Create a laundry order for the customer associated with your API key. Returns the order id, status, tracking URL and planned deposit. Payment is NOT collected online — it is arranged offline (cash, Revolut, MBway). Required: storeId, serviceType, pickupAddress, and either weightKg (for wash_dry) or itemsCount (for other services). deliveryAddress defaults to the pickup address if omitted.
`get_order_status`	Look up the status of one of the customer's orders by order id or order number. Only returns orders belonging to the API key's customer account. Includes status, service, costs and a public tracking URL.
`list_my_orders`	List the most recent orders for the API key's customer account (max 10), newest first, with status and tracking URL. Useful to answer 'where is my order?' questions.
`list_payment_methods`	List the accepted payment methods (e.g. cash, Revolut, MBway). Payment is ALWAYS arranged offline — no online payment is processed by this server. Use this to tell the customer how they will pay the driver/laundry.
`get_tracking`	Get the live tracking snapshot for one of the customer's orders: status, tracking URL, and — when the order is out_for_delivery — the driver's current GPS position. Use this to answer 'where is my order / where is the driver?'.

Orders are not paid online — payment is arranged offline (cash, Revolut, MBway). Security is calibrated for usability: a single revocable API key per customer. Get a key from the Ironing Hero operator (Gate PWA → API Keys).

Full spec: lavanda/docs/mcp/README.md