Skip to content
Woodander Docs
EN

Google Search Console MCP: connect Claude or Cursor to your data

Let Claude Code, Claude Desktop or Cursor read your Woodander data and, under your rules, make changes.

Connect in one command

With Claude Code, after you create a token in Workspace, Settings, API & MCP:

bash
claude mcp add --transport http woodander https://woodander.com/mcp --header "Authorization: Bearer <token>"
  1. 1. What is Woodander MCP? Woodander MCP lets your own Claude or Cursor read your Woodander data and, under your rules, make changes. Here is what it does and what it never does.
  2. 2. Get a Woodander API token Create a personal access token in Workspace Settings, pick the right scopes, set an expiry, and keep it safe. Every scope explained.
  3. 3. Connect Woodander to Claude Code Add the Woodander MCP server to Claude Code with one command, check that it works, and try your first prompts.
  4. 4. Connect Woodander to Claude Desktop Connect Claude Desktop to the Woodander MCP server through mcp-remote with a small JSON config, then test it with whoami.
  5. 5. Connect Woodander to Cursor Add the Woodander MCP server to Cursor with a short JSON config and check it works with whoami and your first read-only prompts.
  6. 6. Modes and approvals Manual, Hybrid and Autonomous: what your assistant may do on its own, what waits for your approval, where to approve, and how to roll back.
  7. 7. Recipes: ready prompts for Woodander MCP Eleven prompts to paste into Claude or Cursor, with the tools they call and what you have to approve. SEO review, tracking fixes, project page and more.
  8. 8. Limits and errors Plan requirements, rate limits and the errors you may meet (401, 403, 404, 422, 429 and more), with what to do about each.
  9. 9. Woodander MCP FAQ Answers on privacy, plans, costs, revoking access, safety and what your assistant can and cannot do with the Woodander API and MCP.