Skip to main content
Merchkit exposes a remote MCP server so you can operate your catalog directly from Claude and other MCP-capable agents. The MCP layer is a thin shim over the same REST API, so its tools never drift from the documented surface.
Examples use https://www.merchkit.com as the base URL.

​
Endpoint and auth

​
MCP endpoint
string
https://www.merchkit.com/api/mcp — a remote MCP server over Streamable HTTP.
Authenticate with the same workspace API key you use for REST — a bearer mk_live_ token: 
Authorization: Bearer mk_live_...
The key’s scopes apply identically here: a read-only key can call the read tools but not the write tools. See Authentication for the scope model.

​
Connect from Claude Desktop

Claude Desktop connects to remote MCP servers through the mcp-remote bridge. Add Merchkit to your claude_desktop_config.json:
1

Open your config file

On macOS this is ~/Library/Application Support/Claude/claude_desktop_config.json. Create it if it does not exist.
2

Add the Merchkit server

{
  "mcpServers": {
    "merchkit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.merchkit.com/api/mcp",
        "--header",
        "Authorization: Bearer mk_live_..."
      ]
    }
  }
}
3

Restart Claude Desktop

Restart the app. The Merchkit tools appear in the tools menu, and you can ask Claude to search, inspect, and enrich your catalog.
Your API key is a secret. Anyone with this config file can act on your workspace with the key’s scopes — protect it accordingly.

​
Write tools require confirmation

Every write tool takes a confirm flag so the agent can preview a change before applying it.
1

Preview

Call the tool with confirm omitted or false. The tool returns a diff describing exactly what would change — and makes no change.
2

Apply

Call the same tool again with confirm: true to apply the change.
This two-step flow lets an agent show you the intended change and get your sign-off before anything is written.

​
Tools

The MCP tools mirror the REST API.

​
Read tools

ToolWhat it does
search_productsList and search products with the filter DSL, sort, and pagination
get_productFetch a single product’s full detail
list_attributesList attribute definitions for an entity type / channel
get_completenessCheck per-channel completeness for a product
get_referencesRead a product’s references (related entities)
get_historyRead an entity’s change history
list_channelsList the available channel catalog
get_jobPoll an async job

​
Write tools

ToolWhat it does
create_productCreate a product (optionally as a variant via a parent)
set_attribute_valuesSet attribute values on a product (enrichment)
set_parentSet a product’s parent entity
The relationship resource is called references — use get_references to read related entities. (There is no “connections” tool.)
There is no delete tool in the beta. Destructive operations are disabled across both REST and MCP and will be enabled in a later release. See Authentication.