Troubleshooting

Sign-in says no workspace matches my email

Memoth resolves your workspace from your email domain or your existing membership. If neither matches, your organisation is not on Memoth yet or your account has not been activated. Ask your workspace administrator, or hello@memoth.ai.

The client keeps asking me to sign in

A 401 after a successful sign-in usually means the client presented a token for the wrong audience or an expired one it failed to refresh. Remove the server from the client and add it again. With mcp-remote, delete ~/.mcp-auth first.

403 insufficient_scope

WWW-Authenticate: Bearer error="insufficient_scope", scope="memory.write", resource_metadata="https://mcp.memoth.ai/.well-known/oauth-protected-resource/mcp"

The tool needs a scope your token does not carry. A current client re-authorizes on its own and shows you the consent screen with the extra scope. An older client needs the server removed and re-added. On /mcp/readonly a write is not a scope problem: the tool is simply not there.

Searches return nothing

Call whoami. If read_pool_ready is not_ready, no memory has been made visible to your identity yet; the note says what the server observed. If it is ready and a search still comes back empty, the result’s notice tells you whether nothing matched or nothing is visible.

429 rate limited

More than 60 requests in a minute from one identity. The Retry-After header says how long to wait. Agents polling in a loop should back off rather than retry immediately.

The call hangs, then fails

A tool call is bounded at 25 seconds. The transport writes nothing until the result is ready, so a slow search looks silent until it either answers or times out. A retry is a fresh request; nothing is held server-side.

405 Method Not Allowed

The client tried GET or DELETE on the endpoint. The server is POST-only Streamable HTTP with no event stream; use a client that speaks the current transport.

Unknown tool

The client called a tool this connection does not have: memory_write on the read-only endpoint, or memory_receipt from an agent credential. Check whoami’s tools_available.

Still stuck

Write to hello@memoth.ai with the client you use, the time of the failure and the whoami output. Never include a token.