Skip to main content
Client-specific nits live on that client’s tutorial. This page is the shared list.
Almost always a typo in the URL. It is /mcp/crm or /mcp/studio, not /crm and not /mcp.Check the server is up first:
200 means Sailer is fine and the problem is your URL or client config.
The email you used at Auth0 is not a member of any Sailer workspace. Sign in with the address your Sailer account uses, or ask an admin to invite you.
Your account exists but belongs to no workspace. An admin has to add you to one.
A connection is bound to one workspace for its lifetime. The binding lives inside the token, which is why no URL names a company.Remove the connector and add it again, then pick the other workspace — or approve the write scopes — at consent. Same reconnection for both.You cannot point one URL at two workspaces at once.
OAuth tokens are minted for exactly one server. Using a CRM grant on Studio is 401, not 403. Audience mismatch is not a missing scope. Reconnect to the other URL. Retrying will loop.
Expected for a custom connector. Claude and ChatGPT only render a logo for directory listings, where the icon is uploaded separately. The server does publish its icon; those clients do not read it here yet.
MCP errors are written for the model, which is about to decide what to do next.
  • Unknown field — name the key and often a suggestion. Call describe_schema. Do not retry the same key.
  • Not found — deleted, other workspace, or outside your ACL. Same next step: list or search again. Do not retry the id.
  • Missing scope — the message names the scopes and says retrying will not help. It won’t. Reconnect and grant them.
A 401 on the HTTP layer (expired or wrong-audience token) is different: the client should re-authorize, not the model retry the tool.