--- title: "SEO in Claude Code on Mac: No Data API, No Account" description: "Run SEO tasks from Claude Code with local MCP tools. Capture live SERPs, read the AI Overview, check ranks. No data vendor, no project, no credits." date: 2026-08-28 author: "Ben Racicot" tags: ["SEO", "MCP", "SERP", "AI Overviews", "Privacy", "macOS"] type: "article" canonical: "https://modelpiper.com/blog/claude-code-seo-mac" --- # SEO in Claude Code on Mac: No Data API, No Account > Run SEO tasks from Claude Code with local MCP tools. Capture live SERPs, read the AI Overview, check ranks. No data vendor, no project, no credits. ## TL;DR ToolPiper exposes SERP capture, keyword discovery and rank checks as MCP tools your agent can call from Claude Code. The capture runs in the Chrome already on your Mac and returns the AI Overview with the domain it cites first. No API key, no data vendor, no project, no credits. Most SEO work inside an AI editor stalls on the same step. You ask the agent what ranks for a query, and it cannot look. So you open a browser, read a results page, copy a few lines back into the chat, and the agent reasons over your transcription instead of the page. The fix is not a better prompt. It is giving the agent a tool that fetches the results page itself. Model Context Protocol is the wire format for that, and an SEO MCP server is simply one that exposes search tasks as callable tools. ## What an SEO MCP server actually is It is a server that turns SEO tasks into tools an agent can call. Instead of you reading a results page and pasting the ranks into a prompt, the agent asks for the ranks. The difference matters most in a loop: an agent that can capture a SERP, read it, rewrite a title and capture again is doing the work, not narrating it. Nearly every SEO MCP server on the market is a protocol wrapper over a metered data API. That is a real architecture with real advantages, and it is why those servers can answer questions about search volume that this one cannot. Start with what this does not do. There is no search volume here, no keyword difficulty, no cost per click, no backlink index, no domain overview, no stored rank history and no site crawler. If you need any of those, a vendor backed suite such as OpenSEO has them and ToolPiper does not. OpenSEO is open source under MIT with nine agent skills, and its data is metered through DataForSEO on every keyword, SERP and backlink call. Verified 2026-08-28. ## What ToolPiper does instead ToolPiper captures the live results page in the Chrome already installed on your Mac, over the DevTools Protocol. Because it reads the rendered page rather than a vendor feed, the capture includes the People Also Ask block, the related searches, and on Google the AI Overview together with the domain it cites first. OpenSEO's SERP tool flattens every result to six fields, so an AI Overview arrives as a typed row with the contents dropped. The trade is legible. You give up volume and history. You get the answer box, its sources, and a flat price with no metering: no API key, no data vendor, no project, no credits. OpenSEO's MCP asks for a project on every call. This one asks for a query. ## What you need A Mac on Apple Silicon running macOS 26 or later, Google Chrome, ToolPiper, and any MCP client. Claude Code is the one used below; Cursor, Devin and Zed take the same server. ## Connect the server, then ask Once ToolPiper is registered as an MCP server, the SEO tools appear alongside every other tool the agent has. You do not call them by name. You ask for the outcome and the agent picks the tool. ## Limits worth knowing before you start ToolPiper needs macOS 26 or later on Apple Silicon, and the SERP capture drives Google Chrome over the DevTools Protocol, so Chrome has to be installed. One capture is a sample, not a measurement: AI Overview presence rotates by session, location and personalisation, so a single run tells you what happened once, in your browser, from where you are sitting. Search Console tools sit behind Google OAuth on your own account. ## Try it Download ToolPiper, add it to Claude Code with one command, and ask your agent who owns the AI Overview on a query you care about. The rung badge at the top of this page names the plan the SEO tools sit on, resolved from the pricing catalog rather than written here. _Part of the SEO tools guide for Mac. The roundup covers SERP capture, keyword discovery, rank checks, Search Console and listening in one place._ ## Steps ### 1. Install ToolPiper and register it with Claude Code Download ToolPiper from [modelpiper.com/download](/download) and launch it. Then register the MCP server: `claude mcp add toolpiper -- ~/.toolpiper/mcp`. Claude Code picks up the tools on its next start. ### 2. Ask what ranks, and let the agent capture the page Ask in plain language: "capture the Google results for seo mcp server and tell me who ranks." The agent calls `serp_search`, which drives your Chrome, reads the rendered page, and returns ranked organic results with title, URL, domain and snippet, plus People Also Ask and related searches. ### 3. Check whether an AI Overview answers the query first The same capture reports the AI Overview when Google shows one, along with the domain it cites first. Ask "is there an AI Overview on this query, and who does it cite?" before you plan a page. A query Google answers above the results is a different job from one it does not, and one capture is a sample rather than a verdict. ### 4. Turn a seed into the queries people actually type Ask the agent to expand a seed. It calls `serp_autocomplete`, which reads Google Suggest with no browser and returns the completions Google offers. These are presence, not volume: a suggestion proves people type the phrase, and says nothing about how many. ### 5. Check where you rank, then close the loop Ask "where does my domain rank for this query?" and the agent calls `serp_rank_check`, which captures the page once and reports your best organic position or null when you do not appear. Rewrite the title, publish, and ask again. That is the loop the tools exist for. ## FAQ ### Do I need an API key or a data vendor account? No. There is no API key, no data vendor, no project and no credits. The capture runs in your own Chrome, and Search Console runs on your own Google account over OAuth. ### Can it tell me a keyword's monthly search volume? No. `serp_autocomplete` returns presence, not volume. It tells you Google offers a completion, which proves people type it. If you need volume, difficulty or cost per click, a vendor backed suite has them and this does not. ### Does it detect AI Overviews? Yes, on Google. The capture returns the AI Overview and the domain it cites first. Presence rotates by session, location and personalisation, so treat one capture as a sample. ### Does my search query stay on my Mac? The query goes to Google or Bing, because that is what a search is. What does not happen is a third party in the middle: there is no data vendor receiving your queries and no account tying them to a project. ### How is this different from OpenSEO? OpenSEO is open source under MIT with nine agent skills, and covers volume, backlinks, site audits, local SEO and rank history, none of which ToolPiper has. Its data is metered through DataForSEO. ToolPiper captures the page in your browser, returns the AI Overview and its first cited source, and is unmetered. Verified 2026-08-28. ### Which MCP clients work? Any MCP client. Claude Code, Cursor, Devin, Zed and Claude Desktop all take the same local server over stdio or HTTP.