What is Woodander MCP?

Woodander MCP is a door into your Woodander account for the AI assistant you already use. Claude Code, Claude Desktop or Cursor connects to it, reads your data (SEO reports, Search Console, Google Analytics, project stats, articles) and, if you allow it, asks for changes.

MCP (Model Context Protocol) is a standard way for an assistant to call tools. Woodander runs an MCP server at https://woodander.com/mcp. It also offers the same things as a plain REST API at https://woodander.com/api/v1. Same names, same arguments, same rules.

What can your assistant do with it? #

Think of it as two kinds of work.

Reading. Your assistant can pull:

• Search Console numbers for your sites: clicks, impressions, CTR, position, top queries and pages, and search opportunities.
• Google Analytics (GA4) sessions, top pages and traffic sources.
• Site audits with scores, issues and fixes.
• Your Discover projects, their analytics, leads and reviews.
• Your Woodander Media articles and drafts.
• Keyword ideas, tracked keywords and rank history.
• Uptime status and your white-label PDF reports.
• The contents of your Google Tag Manager container, plus a check of what tracking is missing or duplicated.

Changing things, with your approval. Depending on your plan and your token, it can:

• Propose or make changes in Google Tag Manager, inside a separate workspace named "Woodander".
• Edit the draft of your Discover project page (tagline, description, highlights, FAQ, links), add screenshots, post a Newsroom Brief, reply to a review, and update a lead's status.

Which of these runs at once and which waits for you is decided by a mode you set. See Modes and approvals.

Why would you want it? #

Your assistant already knows your code and your site. What it lacks is your numbers. With Woodander connected, you can say "which of my pages lost clicks this month, and what should I fix?" and it answers from your real Search Console data, then opens the right file in your repo.

You skip the export-and-paste dance, and you keep working in the tool you already like.

Who is it for? #

• Founders and indie makers who run their own site and use Claude Code or Cursor.
• Marketers who want a weekly SEO review without opening five dashboards.
• Makers with a project in Discover who want help keeping the page fresh.

You need a plan with API access. A Project Pro pass opens the API and MCP for Discover, your own Newsroom and Market only. See Limits and errors for plan details.

What it never does #

• It never sees other people's data. A token only sees what its owner can see in the Workspace.
• It never publishes on its own unless you said so. In the default Manual mode, every change is a proposal that you approve in the Workspace.
• It can never confirm its own changes. Confirmation happens only in the Workspace. A request that carries a token is refused there.
• It does not edit your live Tag Manager workspace. Changes go to a workspace called "Woodander".
• It does not write to your live project page directly. Edits go to your draft first.
• It does not leak secrets. Responses carry no secrets, and other users' emails are never returned.

Connect in a minute #

Pick your client. Each tab has the same server and the same token; only the place you paste it differs. The full steps are in the connect guides.

claude mcp add --transport http woodander https://woodander.com/mcp --header "Authorization: Bearer <token>"

{
  "mcpServers": {
    "woodander": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://woodander.com/mcp", "--header", "Authorization:Bearer <token>"]
    }
  }
}

{
  "mcpServers": {
    "woodander": {
      "url": "https://woodander.com/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Where the tool-by-tool reference lives #

This guide set explains how to use it. The full list of tools, arguments and examples is generated from the live API and sits on the developers page. OpenAPI JSON is at /api/v1/openapi.json.

Next step #

Create a token: Get a token.