Errors

Failures surface at two layers: the HTTP status (did the request reach the server and authenticate?) and the JSON-RPC envelope (did the call itself succeed?). Check both.

HTTP status codes

Status	Meaning
200	The request was processed — but the body may still carry a JSON-RPC error (below)
401	Missing x-api-key, or the key isn't enabled for MCP — see Authentication & access
5xx	Transient server-side failure — safe to retry with backoff

JSON-RPC errors

A failed call returns an error envelope instead of a result:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": { "code": -32602, "message": "Invalid arguments" }
}

Code	Meaning	Usual cause
-32600	Invalid request	Malformed envelope, or a missing MCP-Protocol-Version header when hand-rolling HTTP
-32601	Method not found	Wrong method name — or a wrong tool name; tools are namespaced (mdmcp-search_brands, not search_brands)
-32602	Invalid params	Arguments don't match the tool's input schema — check the tool's Reference page
-32603	Internal error	Server-side failure while executing — safe to retry

Empty results aren't errors

A search that returns an empty list succeeded — no match cleared the relevance threshold. Rephrase the query, make it more specific, or batch several phrasings in one call (see Concepts → Tools).

Retrying

Every EDITED MCP tool is a read-only search with no side-effects, so retries are always safe. Retry 5xx and -32603 with exponential backoff; don't retry 401 or -32602 — those need a fix (key or arguments), not patience.

Getting help

If you're stuck, email support@edited.com with:

• the tool name and arguments you called,
• the full error envelope you got back,
• your session ID — read the mdmcp+data://session_id resource right after the failing call so EDITED can find your requests in the logs.