SearchLink

com.namubase.searchlinkPublished by searchlink.namubase.comOfficial publisherv1.0.3Updated Oct 24, 2026

Google Search Console in your AI: overview, opportunities, index gaps, page checks, long history.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP server that brings Google Search Console data into an AI assistant: overview, opportunities, index gaps, page checks and long history.

What you can do
  • Read Search Console performance overviews for a site.
  • Surface ranking and click opportunities.
  • Inspect indexing gaps and coverage issues.
  • Run checks on individual pages.
  • Review longer historical search data.
When to use it
Useful for SEO and site-owner work where you want an assistant to interpret Search Console performance, spot opportunities and indexing problems, and check specific pages without switching to the Google interface.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or environment variables. OAuth sign-in is required, so the user needs a Google account with access to the relevant Search Console properties.
Before you install
OAuth grants the server access to the user's Search Console data, which is sent to the remote service and to the AI assistant. Review the requested scopes and the provider's data handling before connecting; the tool list is not published, so confirm what it can read or change.

Installation

In SourceWeft

  1. Open SearchLink in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.namubase.searchlink%2Fsearchlink/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "searchlink": {
      "type": "http",
      "url": "https://searchlink.namubase.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.3LatestSep 20, 2026
  2. v1.0.1Sep 19, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Namubase integrations