Developer · Remote MCP server

AgentSEO

Live SEO workflow tools for Claude Code, Codex, and AI agents.

Visit AgentSEO's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
dev.agentseo.www/agentseo-mcp
Version
0.1.4
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-07-20
Updated
2026-07-20
Publisher
dev.agentseo.www
Namespace
Namespace verified by the MCP Registry via the domain www.agentseo.dev or a parent domain of it · how
Website
www.agentseo.dev
Repository
github.com/AgentSEO-dev/agentseo-clients
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://www.agentseo.dev/mcpx-api-key (required, secret), x-project-id, x-workflow-id

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
AgentSEO Hosted MCP 0.1.0 · protocol 2025-06-18
Tools discovered
45 - show namesagentseo_search, agentseo_extract, agentseo_analyze_serp, agentseo_local_audit, agentseo_content_gap, agentseo_opportunities_find, agentseo_opportunities_brief, agentseo_content_refresh_brief, agentseo_content_serp_outline, agentseo_content_brief, agentseo_content_draft_qa, agentseo_content_schema_plan, agentseo_content_internal_links, agentseo_content_title_meta, agentseo_content_keyword_map, agentseo_content_technical_qa, agentseo_content_action_plan, agentseo_site_sitemap_audit, agentseo_serp_volatility, agentseo_page_cro_qa, agentseo_ai_visibility_prompt_set, agentseo_content_programmatic_template, agentseo_content_cannibalization, agentseo_content_competitor_gap_matrix, agentseo_keyword_ideas_suggest, agentseo_keyword_metrics_overview, agentseo_domain_ranked_keywords, agentseo_domain_relevant_pages, agentseo_domain_competitors, agentseo_domain_intersection, agentseo_domain_traffic_estimate, agentseo_backlinks_summary, agentseo_backlinks_list, agentseo_backlinks_anchors, agentseo_backlinks_referring_domains, agentseo_backlinks_domain_pages, agentseo_backlinks_competitors, agentseo_backlinks_new_lost_timeseries, agentseo_backlinks_page_intersection, agentseo_backlinks_opportunity_finder, agentseo_page_intersection, agentseo_ai_overview_extract, agentseo_local_visibility_track, agentseo_rank_track, agentseo_job_status
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@agentseo/mcp-server0.1.3stdioAGENTSEO_API_KEY (required, secret), AGENTSEO_API_URL, AGENTSEO_PROJECT_ID, AGENTSEO_WORKFLOW_ID

How to connect AgentSEO

AgentSEO is a remote MCP server: there is nothing to install. Its endpoint is https://www.agentseo.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares HTTP headers for the connection: x-api-key (required, secret), x-project-id and x-workflow-id. A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.

It can also run locally from a Node.js package published to the npm registry: @agentseo/mcp-server version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @agentseo/mcp-server@0.1.3. It reads these environment variables: AGENTSEO_API_KEY (required, secret), AGENTSEO_API_URL, AGENTSEO_PROJECT_ID and AGENTSEO_WORKFLOW_ID; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "agentseo-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentseo/mcp-server@0.1.3"
      ],
      "env": {
        "AGENTSEO_API_KEY": "<secret>",
        "AGENTSEO_API_URL": "<value>",
        "AGENTSEO_PROJECT_ID": "<value>",
        "AGENTSEO_WORKFLOW_ID": "<value>"
      }
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
AGENTS.md GeneratorAnalyzes codebases with tree-sitter and generates AGENTS.md files for AI coding agents.Local · stdioPyPI: agents-md-generator
AgentscoreMCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.Local · stdionpm: @agentscore-xyz/mcp-server
AgentsealVerifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain.Local · stdionpm: agentseal-mcp
Agentsearch MCPLLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.Remote · HTTPLive check: ✓ handshakeagentsearch-mcp.vercel.app
Agentshield MCPDetect prompt injection, jailbreak, and social-engineering attacks in LLM agents.Local · stdionpm: @eigenart/agentshield-mcp
agentsim.devControl plane for agent auth walls. Connector 0 handles SMS OTP with US test numbers.Remote · HTTPLive check: sign-in requiredmcp.agentsim.dev
AgentsJunctionDiscover MCP servers, A2A agents, and shared agent knowledge through a read-only MCP gateway.Remote · HTTPLive check: ✓ handshakeagentsjunction.com
Agentskillupdategate MCPPaid remote MCP for Claude Code skill update gate MCP, structured receipts, audit logs, and reviewer.Remote · HTTPLive check: ✗ no handshakeagentskillupdategate.clauxel.com