Skip to content
Searcherries
Log inTry for free

Connect Cursor, VS Code and other MCP clients

Searcherries is a standard Streamable HTTP MCP server. Clients that support OAuth register themselves against the server URL and sign in through the browser. A client that cannot do that can use a personal access token.

The server URL is:

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

You need paid-plan access in Searcherries (an active trial counts). The MCP page has a tab with a copyable configuration for each client.

Cursor

The quickest way is the install link: Add Searcherries to Cursor. Cursor opens and asks you to install the server. Then select Connect next to Searcherries in the MCP settings and approve access in your browser.

To add it by hand instead:

  1. Open Cursor settings and find MCP. Open the global MCP configuration, or open ~/.cursor/mcp.json directly.
  2. Paste the configuration below and save. If the file already has servers, add Searcherries inside its existing mcpServers object.
  3. Enable Searcherries in the MCP list. Select Connect or the sign-in prompt and approve access in your browser.
  4. Open an Agent chat and ask: "List my Searcherries projects." Allow the Searcherries tool call when prompted.
{
  "mcpServers": {
    "searcherries": {
      "url": "https://app.searcherries.com/mcp/searcherries"
    }
  }
}

To use the server in one project only, save the same configuration in .cursor/mcp.json in that project. Cursor's MCP guide describes its settings.

VS Code with GitHub Copilot

The quickest way is the install link: Install Searcherries in VS Code. VS Code opens and asks you to install the server. Then start the server, confirm trust and sign in to Searcherries in your browser.

To add it by hand instead:

  1. Open the Command Palette: Ctrl+Shift+P on Windows and Linux, Cmd+Shift+P on Mac.
  2. Run MCP: Add Server, choose HTTP and paste the server URL.
  3. Name the server searcherries. Choose Global for all projects or Workspace for the current one.
  4. Start the server, confirm trust and complete the Searcherries sign-in when prompted.
  5. Open Copilot Chat in Agent mode, enable Searcherries in Configure Tools and ask: "List my Searcherries projects."

You can also add the server to .vscode/mcp.json. Keep any existing servers inside the servers object.

{
  "servers": {
    "searcherries": {
      "type": "http",
      "url": "https://app.searcherries.com/mcp/searcherries"
    }
  }
}

The Codex extension inside VS Code has its own MCP settings; follow the Codex guide for it. VS Code's MCP server guide describes the Copilot side.

Any other client

  1. Find MCP servers or Integrations in your app and add a remote server named Searcherries.
  2. Choose Streamable HTTP, paste the server URL and use OAuth or browser sign-in when available.
  3. If the app only supports a bearer token, create one as described below and set the Authorization header to Bearer YOUR_TOKEN.
  4. Save, enable the server and ask: "List my Searcherries projects."

A client that only supports local command (stdio) servers needs its own remote HTTP adapter.

Access tokens

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. Clients that sign in through the browser do not need one.

Create a token

  1. Open MCP in Searcherries.
  2. Open the Other clients tab and 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 the client

Use a remote or Streamable HTTP MCP connection with the server URL above and 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.

Need a hand? Contact support