MCP server

SKUHelm for your agents

A remote MCP server over Streamable HTTP at https://www.skuhelm.com/api/mcp. Its tools call the same code as the REST API, so the two always agree.

Connect

Two tools work without a key: validating rows, and reading any store's published feed by its slug. Add your key to read your own status and start syncs.

{
  "mcpServers": {
    "skuhelm": {
      "type": "http",
      "url": "https://www.skuhelm.com/api/mcp",
      "headers": { "Authorization": "Bearer ${SKUHELM_KEY}" }
    }
  }
}

Tools

validate_catalogValidate product feed itemsNo key needed · read only

Check up to 1000 product items against OpenAI's product feed spec. Returns a status per item (ready, needs_work or blocked) with each problem's field and reason. With an API key, the store's settings fill gaps first, exactly as its live feed would.

get_sync_statusGet catalogue and feed statusNeeds a key · read only

Where the store stands: item counts by status, the live feed's version and addresses, each connected source and the last few syncs.

sync_catalogSync the store nowNeeds a key

Re-read the store's connected shop now, record what changed and republish the feed. Pro plan. Takes up to a minute for large shops.

get_acp_feedRead a published feedNo key needed · read only

The live published feed for your store (or any store by its slug): version, counts and the first items. Use limit to read more, up to 500.

Details

Protocol versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05.
Stateless. Each POST is one JSON-RPC message and gets one JSON answer. Notifications get 202.
Limits: 240 a minute with a key, 60 a minute per IP address without.
A tool that fails returns isError: true with a sentence saying why, rather than a protocol error.