Skip to content
WeaversDocs
MCPAI connections ↗
Browse documentation

Weavers / MCP documentation

Troubleshooting

Resolve Weavers MCP sign-in, permissions, stale context, and connection errors.

Connection and sign-in

  • Start with the exact server URL and a client enabled for your account.
IssueWhat to do
Connection unavailable / 404Check the server URL and whether assistant access is enabled in your deployment. Contact Weavers if the configured connection is missing.
invalid_token / HTTP 401Restart authorization. The token may be expired, intended for another audience, or issued to an unrecognized client.
signin_requiredSign in through your assistant's Weavers connection flow. A browser cookie alone does not authorize MCP calls.
connection_requiredConnect or reconnect the assistant in AI connections, then authorize it again.
verified_account_requiredVerify your Weavers email before connecting.
recent_signin_required / flow_expired / signin_expiredSign in again and restart the connection in one browser session.

Tools and permissions

IssueWhat to do
insufficient_scopeAuthorize the specific permission required by the tool. Existing read access does not grant source, dataset or draft access.
not_foundUse an identifier from your own workflow and confirm you can open that resource in Weavers.
Invalid tool argumentsCheck required fields, UUID format, integer limits and extra fields against the tool reference.
assistant_draft_context_changedRefresh strategy/source/dataset metadata, review it, then prepare a new draft request.
python_assistant_proposal_invalidCheck paired nullable IDs/hashes/revisions and the current source context.
result_too_largeRequest fewer notebooks or a smaller source/data slice when the tool supports it.

Availability and retries

IssueWhat to do
HTTP 405Use POST for MCP messages. This server does not provide a GET event stream.
HTTP 403 with a browser OriginUse the supported assistant connection. Cross-origin browser calls are rejected.
HTTP 429Wait for Retry-After before trying again; avoid parallel retries.
HTTP 503 / tool_unavailable / assistant_unavailableRetry with backoff. For writes, preserve the same request and identifier; check for a saved draft or proposal first.

When contacting support

  • Share the tool name, error code, approximate time, and assistant application/version.
  • Leave access tokens, cookies, private Python source, and dataset rows out of screenshots and support messages.