Connect Claude to Searcherries

Use Searcherries as a custom remote connector in Claude to analyze your stored project data from a Claude conversation.

You need paid-plan access in Searcherries and a Claude account or workspace that allows custom connectors. Available connector controls depend on your Claude account and workspace settings.

Add the plugin

The quickest way is the Searcherries plugin in the Claude directory: Add Searcherries to Claude. It adds the connector and seven GEO workflows you can run as /searcherries:action-plan, /searcherries:geo-audit, /searcherries:content-gaps, /searcherries:competitor-gap, /searcherries:page-brief, /searcherries:question-review and /searcherries:weekly-report. After installing, open the plugin's Connectors tab, connect Searcherries and approve access in your browser. The plugin also loads in your Claude Code sessions.

Or add the connector by hand

1. Sign in to Searcherries and open MCP.
2. Select the Claude instructions.
3. Copy the Remote MCP server URL.
4. Copy the OAuth Client ID displayed on the page.
5. In Claude, open Settings → Connectors and choose Add custom connector.
6. Enter Searcherries as the name, paste the server URL, and supply the OAuth Client ID in the appropriate advanced field if requested.
7. Continue with the connection and approve the Searcherries authorization screen in your browser.

The server URL is https://app.searcherries.com/mcp/searcherries. Claude's custom connector guide describes its connector controls and workspace requirements.

The OAuth Client ID identifies the connector application. It is a public identifier shared across users; it is not your password and does not grant account access without your authorization. Copy the value from Searcherries rather than using an example from another account setup guide.

Verify the connection

In a conversation where the connector is enabled, ask:

List the projects available in my Searcherries account.

Check that the returned projects belong to the account you intended to authorize. Then select one by name or project ID and ask for an analysis.

A more focused request is:

For this project, compare the leading competitors and cited URLs. Separate observed data from your recommendations and include the reporting dates.

If it does not connect

Check the full server URL, including /mcp/searcherries. Confirm that you completed browser authorization and have active paid access in Searcherries.

If the expected projects are missing, the browser may have authorized a different Searcherries account. Disconnect the connector in Claude and reconnect using the correct account.

If the OAuth Client ID is unavailable in Searcherries or your Claude workspace does not allow the connector, contact support or the relevant workspace administrator.

The connection is read-only and does not refresh reports. Learn about MCP data access and data update schedules.

Use the built-in prompts

Once the connector is active, Claude lists the Searcherries prompts in its prompt menu: action-plan, geo-audit, content-gaps, competitor-gap, page-brief, question-review and weekly-report. Each prompt gives Claude a step-by-step recipe: which Searcherries tools to call, in which order, and what to deliver. Pass the project name or id as the project argument when the account has more than one project; competitor-gap needs a competitor name and page-brief a page URL. action-plan also takes an audience of business, marketing or seo.

In Claude Code the same prompts appear as slash commands under the server name, so an audit can end with Claude Code editing the pages it recommends, with every change shown to you first. The tool reference lists every tool and argument the prompts use.