AgentSEO integrations

SEO tools.
Inside your workflow.

Connect AgentSEO to Claude, Codex, Cursor, n8n, Make, or your own app. Bring search results, content gaps, ranking checks, and local audits into the tools you already use.

Find your setup Get a free API key

One AgentSEO account. API usage follows your plan and credit limits.

From your tool to search evidence
EditorAutomationYour app
MCP · HTTP · SDK

AgentSEO

Search, analyze, check, and track

Result or job to poll

Structured evidence → your next decision

Your client or orchestrator controls scheduling, follow-up actions, and publishing.

Choose your connection

Start with the tool you use.

Each card names the connection you will configure. n8n and Make guides use HTTP; OpenClaw has an AgentSEO plugin.

Claude Code

Hosted MCP

Research a keyword or inspect a content gap while you work in your codebase.

Remote endpoint with an API key; local MCP also available.

Connect Claude Code

Claude Desktop

Local MCP package

Bring search evidence into a conversation, then decide which check to run next.

Run @agentseo/mcp-server with Node.js and your API key.

Set up Claude Desktop

Codex

Hosted MCP configuration

Give your coding agent SEO tools for research, content planning, and page checks.

Streamable HTTP with a bearer token from your environment.

View Codex configuration

Cursor

Hosted MCP configuration

Use search results and competitor context alongside the pages you are building.

Add the AgentSEO URL and authentication header to MCP settings.

View Cursor configuration

n8n

HTTP workflow guide

Schedule SEO checks, wait for results, and route findings into your review queue.

Uses HTTP Request nodes and your stored credentials.

Build an n8n workflow

Make

HTTP workflow guide

Add keyword and page research to a scenario you can schedule and inspect.

Uses HTTP modules; configure polling for queued jobs.

Build a Make scenario

Your app or agent framework

REST · JavaScript · Python

Build a custom tool around the endpoints your product or agent needs.

Use the API or SDKs; check method coverage in the docs.

Explore SDKs and MCP

OpenClaw

First-party AgentSEO plugin

Add AgentSEO’s packaged SEO tools to an OpenClaw agent.

Install the plugin and allow the tools your agent should use.

Install the OpenClaw plugin

Make the first connection

Choose MCP for tool calls.
HTTP for explicit steps.

Use hosted MCP when your client should discover and call SEO tools. Use REST when you want to select the endpoint and control each step yourself.

Hosted MCP endpoint
https://www.agentseo.dev/mcp
Transport and authentication
Streamable HTTP. Use a server-side API key with no allowed browser domains. Send it as a bearer token or x-api-key header.

Tool discovery is public. Executing SEO tools requires your key and available credits. A visible tool list alone does not verify a successful paid request.

Authentication and key setup
Codex · hosted MCP

~/.codex/config.toml

[mcp_servers.agentseo]
url = "https://www.agentseo.dev/mcp"
bearer_token_env_var = "AGENTSEO_API_KEY"

Set AGENTSEO_API_KEY in the environment of the process running Codex, then add this entry to your config. Confirm the server appears in Codex’s MCP tool list.

Codex MCP documentation →
Cursor · hosted MCP

Private MCP configuration

{
  "mcpServers": {
    "agentseo": {
      "url": "https://www.agentseo.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_AGENTSEO_API_KEY"
      }
    }
  }
}

Add this server in Cursor’s MCP settings and replace the placeholder with your key. Keep the configuration private and out of source control.

Cursor MCP documentation →
Any HTTP workflow · REST

First search request

curl https://www.agentseo.dev/api/v1/search \
  -H "x-api-key: $AGENTSEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"seo automation tools","limit":5}'

Set AGENTSEO_API_KEY first. This request uses API credits and returns a queued job. Save its jobId and poll /api/v1/jobs/{jobId} with the same key until completed or failed.

Full request and polling guide →

Put the connection to work

Start with one repeatable job.

Developers & product teams

Research before you build

Compare a target page with search competitors, then use the evidence to plan an update.

agentseo_search → agentseo_content_gap

Explore this workflow →

Technical marketers

Turn checks into a review queue

Schedule keyword and location checks in your orchestrator. Store results and route changes for review.

agentseo_rank_track → agentseo_job_status

Explore this workflow →

Agencies & automation teams

Repeat research across clients

Run a defined audit for each client. Add project and workflow IDs to keep usage attributable.

agentseo_local_audit → agentseo_job_status

Explore this workflow →

These are workflow patterns you configure. Tool inputs, coverage, and job behavior vary by endpoint. Check the API reference before scheduling repeated calls.

Before you automate

Know what runs where.

Keep the first workflow small: connect, run one request, inspect the result, then add scheduling or agent decisions.

Can I use MCP inside n8n or Make?

Both offer MCP client features. Our linked AgentSEO guides cover HTTP workflows. For an MCP route, check Streamable HTTP and API-key support in your client version and test a single tool first. See n8n’s MCP Client Tool and Make’s MCP Client (currently open beta).

What about LangChain or another agent framework?

Use a framework’s MCP adapter if it supports our transport and authentication, or wrap the REST API as a tool. LangChain documents HTTP MCP connections with custom headers. This is a custom connection, not a dedicated AgentSEO framework package.

How do I control cost and long-running work?

Each executed API operation follows its credit cost; your AI client or automation service may bill separately. Handle queued jobs and failures, set workflow limits, and add x-project-id and x-workflow-id for attribution. Review plans and credit costs.

Does connecting an agent publish changes to my site?

These AgentSEO integrations return SEO evidence and recommendations. Your agent or automation controls downstream edits, messages, and publishing. Add your own review step before those actions.

Run your first SEO request.

Create a key, connect your tool, and inspect the response.

Open the quickstart

Connection guidance reviewed September 20, 2026 against our API, packages, and linked client documentation. Client settings can change. Tell us about a setup issue.