Skip to content
Searcherries
Log inTry for free

Connect n8n to Searcherries

Add Searcherries to an AI Agent in n8n so a workflow can answer questions about your AI visibility, competitors, citations and connected Search Console, Bing Webmaster Tools and GA4 data, or send you a scheduled report built from that data.

You need paid-plan access in Searcherries (an active trial counts) with a project that has finished its first check, and n8n Cloud or a self-hosted n8n with the MCP Client Tool node. The AI Agent also needs a chat model credential, for example OpenAI, Anthropic or Google Gemini.

Create an access token

n8n connects to Searcherries with a personal access token. Browser sign-in (OAuth2) is not available for n8n; the token is the way to connect.

  1. Sign in to Searcherries and open MCP.
  2. Open the Other clients tab and find Access tokens.
  3. Enter a name such as "n8n" and select Create token.
  4. Copy the token right away. It is shown once.

The token guide explains expiry, replacement and revocation.

Add the MCP Client Tool node

  1. Open a workflow in n8n, add an AI Agent node and attach a chat model to its Chat Model input.
  2. Select the + on the agent's Tool input and add MCP Client Tool.
  3. Set Endpoint to the server URL below.
  4. Set Server Transport to HTTP Streamable.
  5. Set Authentication to Bearer Auth, create a new credential and paste the token.
  6. Leave Tools to Include on All.
https://app.searcherries.com/mcp/searcherries

Once the credential is saved, the node loads the nine Searcherries tools. All of them are read-only: the agent reads data Searcherries already stored and cannot change projects or refresh reports. Learn about MCP data access and data update schedules.

Try it in a chat

Add a Chat Trigger before the AI Agent, open the chat and ask:

List my Searcherries projects.

Check that the projects belong to the account that created the token. Then ask about one of them by name:

Using Searcherries, which customer questions do AI assistants answer without naming us, and which competitors do they name instead? Include the reporting dates.

Example: weekly AI visibility report

This workflow mails or posts a short report every Monday morning: Schedule Trigger → AI Agent (chat model + Searcherries MCP Client Tool) → Send Email or Slack.

  1. Schedule Trigger: set Trigger Interval to Weeks, every 1 week, on Monday at 08:00.
  2. AI Agent: attach the chat model and the Searcherries MCP Client Tool. Set Source for Prompt to Define below and paste the prompt from the next section with your brand name in it. In Options, add a System Message: "You are a marketing analyst reporting on AI visibility. Use only the data the Searcherries tools return, keep the reporting dates, and write plain text without markdown headings."
  3. Send Email or Slack: connect it after the agent and use {{ $json.output }} as the text: the Text field of Send Email (with Email Format set to Text), or Message Text of a Slack Send a message operation.

Prompt for the AI Agent:

Write the weekly AI visibility report for the Searcherries project "BRAND NAME".

Steps:
1. Call list-projects and use the project whose brand name matches.
2. Call get-project-summary with that project_id.
3. Call get-competitors with dataset "ranking".
4. Call get-ai-answers with prominence_max 1 to list the customer questions where our brand is missing from the answers.
5. Call get-citations with group_by "domain" to see which sources the AI platforms rely on.

Then write the report in plain text, under 300 words, with these sections: Visibility (score, change against the previous period, named share), Competitors (the three brands that gained the most and what the platforms say about them), Gaps (the three customer questions where we are missing and the domains cited for them), Next week (three concrete actions, each tied to one finding). Include the reporting dates. Use only data returned by the Searcherries tools and say so when a section has no data.

If it does not work

  • 401 Unauthorized when the node loads the tools or the agent calls one: the token was revoked or has expired. Create a new token on the MCP page and update the Bearer Auth credential.
  • The project list is empty: the account that created the token has no project yet, or the token belongs to a different Searcherries account than you expected. A project whose first check is still running is listed, but it has no answers until the check finishes.
  • The node cannot load the tool list: check the full server URL, including /mcp/searcherries, and that Server Transport is HTTP Streamable.

For anything else, contact support.

Need a hand? Contact support