pickfit

BrowseMCP servers

SEO Console

MCP server that joins Search Console data with a site crawl for prioritized technical SEO audits.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 20 or newer
  • Keys or accounts: Google Search Console service-account key
  1. install seo-audit-console globally

    npm install -g @houtini/seo-audit-console@0.5.1

Add it to your agent

claude mcp add seo-audit -e GOOGLE_APPLICATION_CREDENTIALS='<GOOGLE_APPLICATION_CREDENTIALS>' -- seo-audit-console
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "seo-audit": {
      "command": "seo-audit-console",
      "args": [],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>"
      }
    }
  }
}

You fill in

  • GOOGLE_APPLICATION_CREDENTIALS: Google Search Console service-account key (required)

Ask the user for GOOGLE_APPLICATION_CREDENTIALS; pickfit never had a value, so these are placeholders.

Add the server to your MCP client, then ask it to call seo_audit_help to see what it can do.

What it does

  • Combine Search Console data with a site crawl
    Not tested
  • Run a prioritised technical SEO audit
    Not tested
  • Get SEO fixes ready to paste
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 3 features work
  4. Works offline

Good for

  • run a technical SEO audit on a site
  • show keyword cannibalisation with evidence
  • diff two crawls to detect changes
  • find link prospects linking to rivals
  • export a shareable HTML audit report

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.5.1

An MCP client handshake over stdio listed 48 tools, and a call to seo_audit_help returned a result.

Differences the test machine hit

  • README: launch via npx -y @houtini/seo-audit-console@0.5.1
    In the test: npm install -g @houtini/seo-audit-console@0.5.1 then launch as seo-audit-console for PATH persistence and offline replay
  • README: --help prints help
    In the test: seo-audit-console --help starts the MCP server on stdio (log: running on stdio, GSC disabled — no credentials) instead of printing help; use MCP probe handshake instead

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.