## **❗ What this error means**

The message “Given token not valid for any token type” means a Search Atlas authentication endpoint could not validate the supplied token. The token may be expired, malformed, or an unsupported type. This error does not mean your website data was deleted.

## **🔎 Common causes**

- An old token was copied after it expired or was replaced.
- Extra spaces, line breaks, or quotation marks were included with the token.
- A login session, password, or unrelated code was pasted instead of the MCP token.
- The token belongs to a different Search Atlas account than the one you are trying to connect.
- The connection in Claude still points to a token that was removed.

## **🛠️ Reconnect with a fresh token**

1. Sign in to Search Atlas with the account you want Claude to use. Confirm the email address on the account matches the one you intend to connect.
2. Open the Search Atlas MCP connection guide and select your Claude client. For Claude Desktop, follow the OAuth authorization steps; you do not manually create a connection token. For Claude Code, use Generate API key and follow the supplied setup instructions. Do not copy credentials from old chats, emails, or screenshots.
3. Select the full token and copy it once. It should be one continuous value with no spaces before or after it.
4. Reconnect the Search Atlas connector in Claude and complete authorization again. If reconnecting does not resolve the problem, remove the connector and add it again using the current Search Atlas instructions.
5. In Claude Desktop, open Customize → Connectors → Add → Add custom connector. Enter the Search Atlas connector name and the MCP URL supplied by Search Atlas. Select Add, then Connect, and complete Search Atlas authorization.
6. Save the connection, then start a new Claude chat and test a simple Search Atlas request.

## **✅ Check the token before you paste it**

- Paste the token into a plain text field first and remove any leading or trailing spaces.
- Do not add quotes, brackets, labels, or the words token or Bearer.
- Generate a replacement if the original token was shared, exposed, or copied more than once.
- Use the authentication method shown for your Claude client: Search Atlas OAuth authorization for Claude Desktop, or a valid Search Atlas API key for Claude Code. Do not paste your Search Atlas password or an unrelated service’s token into the connection configuration.

## **🔁 If the error continues**

If the wrong Search Atlas account was authorized, sign out and sign back in with the intended account, then reconnect Claude and complete authorization again. For Claude Code API-key connections, generate a replacement key if necessary and update the configuration. If reconnecting fails, remove and recreate the connection using the current setup guide. \*\*Setup evidence:\*\* `customer-frontend/src/modules/mcp-connect/v1/providers/claude.json:9–34` documents Desktop OAuth; lines `47–69` document Claude Code API-key generation and configuration.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.