Official registry + Smithery + npm package live

SEO MCP server for Claude Code, Codex, and AI agents.

Connect AgentSEO once and give your agent 45 live SEO tools for SERP analysis, keyword research, content briefs, backlinks, rank tracking, local SEO, and AI visibility.

Start with free credits Copy install command

MCP tools

Publicly discoverable via tools/list

install paths

Hosted HTTP or local npm stdio

agent surface

Claude Code, Codex, Cursor, and more

agentseo.mcp

Hosted MCP

claude mcp add --transport http agentseo https://www.agentseo.dev/mcp \
  --header "Authorization: Bearer sk_live_your_key" \
  --header "x-project-id: client-alpha" \
  --header "x-workflow-id: nightly-refresh"

First useful prompt

Use AgentSEO to find content gaps for example.com around "seo api for ai agents". Then turn the best opportunity into a content brief with title, outline, evidence, and next actions.

Install paths

Hosted when you want speed. Local when you want control.

AgentSEO is listed with both remote and package metadata, so MCP clients can choose the connection shape that fits the workflow.

Hosted Streamable HTTP

Best for Claude Code, custom agents, and no-wrapper trials.

claude mcp add --transport http agentseo https://www.agentseo.dev/mcp \
  --header "Authorization: Bearer sk_live_your_key" \
  --header "x-project-id: client-alpha" \
  --header "x-workflow-id: nightly-refresh"

Local npm stdio

Best for desktop clients and repo-local MCP config.

{
  "mcpServers": {
    "agentseo": {
      "command": "npx",
      "args": ["-y", "@agentseo/mcp-server"],
      "env": {
        "AGENTSEO_API_KEY": "sk_live_your_key",
        "AGENTSEO_API_URL": "https://www.agentseo.dev/api/v1"
      }
    }
  }
}

What agents can do

Not another dashboard tab. A toolbelt your agent can actually call.

The MCP shape is strongest when the model has a goal and needs live evidence: find the gap, inspect the SERP, draft the brief, check the page, then monitor what changed.

SERP and keyword research

Give your agent live search intelligence instead of asking it to infer the market from stale context.

Content briefs and QA

Turn gaps, SERP outlines, schema plans, internal links, and draft QA into repeatable agent workflows.

Backlinks and competitors

Ask for backlink summaries, competitor intersections, referring domains, and link opportunities from one MCP server.

Local and rank tracking

Run local audits, local visibility checks, rank tracking, and job status polling inside your agent loop.

AI search visibility

Monitor prompt sets, AI Overview extraction, and answer-surface visibility where search is turning agentic.

Production-safe auth

Public discovery is open; paid tool execution stays behind server-side API keys and workflow attribution.

Proof that compounds.

AgentSEO is published in the official MCP Registry, live on Smithery, and available as an npm package. That means discovery, install, and validation are not trapped in one marketplace.

Official MCP Registry

dev.agentseo.www/agentseo-mcp v0.1.4 includes both hosted remote and npm package metadata.

Smithery

agentseo/agentseo-mcp is live and scanner-discovered 45 tools.

npm

@agentseo/mcp-server ships local stdio setup with the correct mcpName.

FAQ

Questions before the first tool call

Is AgentSEO a hosted MCP server or a local npm MCP package?

Both. Use the hosted Streamable HTTP endpoint when you want no local wrapper, or install @agentseo/mcp-server with npx for local stdio workflows.

Does AgentSEO work with Claude Code and Codex?

Yes. AgentSEO is built for MCP-capable agent clients including Claude Code, Codex-style coding agents, Cursor, Claude Desktop, and custom MCP clients.

Do I need an API key?

Yes for tool execution. Discovery calls such as initialize and tools/list are public so directories and clients can inspect the server. Paid tools/call execution requires an AgentSEO API key.

What should I run first?

Start with a content-gap or local-audit workflow. They produce visible next actions quickly and prove the agent can move from live SEO evidence to a useful recommendation.

Why use MCP instead of REST?

Use REST when you are coding a direct backend integration. Use MCP when the model should discover, choose, and call SEO tools while it is planning, writing, debugging, or monitoring.

Give your agent live SEO hands.

Start with free credits, connect the MCP server, and run one real workflow: content gap, local audit, SERP outline, or AI visibility check.

Get API key Read quickstart