Troubleshooting

Most connection problems have a quick fix. Find your symptom below.

The client doesn't show any Shippp tools

• Check the URL — it ends in /api/mcp/mcp (the path segment appears twice).
• Make sure the server is added as a remote HTTP server, not as a local command.
• In Claude Code, run /mcp to see the server status and start the sign-in.
• Restart the client after adding the server.

“This authorization link is missing or has expired”

The sign-in link timed out. Start the connection again from your MCP client — don't reuse an old browser tab.

“Your account has no workspace yet”

Sign in to Shippp once, finish onboarding and create a workspace. Then connect again.

The client says it can't edit

The connection has Read access. Open Settings → MCP → Change access → Read and write, then sign in again from the client when it asks. Viewers can't use MCP at all — you need an editor seat.

The client works on the wrong file or can't find my selection

• Open the file in the Shippp editor in your browser, and select what you mean.
• If several Shippp files are open, close the others or tell the client which file to use.
• On an older single-workspace connection, check that the file is in that workspace — or expand the connection with Work in all workspaces in Settings → MCP.

The client shows as Inactive or asks to reconnect

The client can't reach Shippp right now — usually after you changed its access or disconnected it. Reconnect from the client; Settings → MCP shows reconnect needed next to it.

MCP is blocked in my company workspace

An admin may have turned on Turn off MCP for external people in workspace security, or your organization manages connectors centrally (for example in Claude Team or Enterprise). Ask your admin.

“Rate limited” or my usage ran out

Wait a minute if you see Rate limited. If your weekly units are used up, they reset on Monday at 00:00 UTC — or upgrade your plan. See Usage units.