Skip to main content

​
The client cannot start the adapter

Check the absolute executable path, file permissions, and whether your client supports stdio MCP servers. Ensure the key is present in the adapter process’s environment; a variable in a different terminal may not reach a desktop app.

​
Authentication fails

Check PROTODESK_AUTHORING_KEY, expiry, revocation, and help:read. Set PROTODESK_API_ORIGIN to https://api.protodesk.io without /v1. The adapter requires HTTPS by default. PROTODESK_ALLOW_LOCAL_HTTP=true is only for a loopback development server.

​
A tool is missing

Read-only keys do not expose proposal tools. Article-set tools also depend on the capability returned by the server. Reconnect after changing the key or its permissions, then call authoring_context again.

​
A write returns a conflict

Check the workspace, article revision, and idempotency key. Do not reuse a key with different content. If the article changed, read the current version and prepare a new proposal.

​
A request is too large

Authoring requests must fit within 64 KiB of JSON. Article sets allow at most 20 candidates. Reduce the number or size of articles in one proposal.

​
A request times out

Do not assume a timed-out proposal failed. Retry only with the same arguments and idempotency key. If you already received an ID, read the proposal or article set to check its status. Resolve the returned path against https://app.protodesk.io and sign in to the authorized workspace. A review link never substitutes for dashboard access.