MCP access tokens and other clients

Use a personal access token when an MCP client cannot complete browser authorization. A token lets that client read the Searcherries data available to your account.

For clients that support OAuth, use the browser sign-in flow instead. Token creation is a fallback, not a required step for every connection.

Create a token

1. Open MCP in Searcherries.
2. Find Access tokens.
3. Enter a descriptive Token name, such as “Analytics assistant on my laptop.”
4. Select Create token.
5. Copy the displayed value immediately and store it securely.

The token is shown once and cannot be recovered from the page later. If you lose it, revoke it and create another.

An account can have up to five active personal access tokens. The table shows each token's creation and expiry dates. Use the displayed expiry rather than assuming a token lasts indefinitely.

Configure a compatible client

Use a remote or Streamable HTTP MCP connection with this server URL:

https://app.searcherries.com/mcp/searcherries

Configure an HTTP authorization header:

Authorization: Bearer YOUR_TOKEN

YOUR_TOKEN is an example placeholder. Replace it with the value you generated, using the client's secure credential field or environment-variable support when available.

Some clients use a configuration similar to this:

{
  "mcpServers": {
    "searcherries": {
      "type": "http",
      "url": "https://app.searcherries.com/mcp/searcherries",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Configuration formats vary by client. The Other clients tab on the Searcherries MCP page provides the connection details to adapt to your client.

Revoke access

Find the personal token in the table and select Revoke. Confirm the action. Clients using that token lose access immediately, so update or disconnect any client that relied on it.

The personal-token table manages tokens created there. For a connection established through OAuth, use the external client's connector controls to disconnect it; do not assume revoking an unrelated personal token disconnects OAuth too.

Keep the token private

Do not put tokens in public repositories, shared documents, support messages, or screenshots. If a token is exposed, revoke it and issue a replacement.

If the Access tokens section is unavailable, use OAuth where supported or contact support. No server administration commands are required from you.