SERP Agent SEO

com.serp-agentPublished by serp-agent.comOfficial publisherv1.0.1Updated Nov 2, 2026

Full-cycle SEO automation for AI agents: technical audits, SEO articles, machine-readable pricing.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

SERP Agent MCP server that lets an assistant run technical SEO audits, generate SEO articles and manage SEO projects through a hosted API.

What you can do
  • Create, list and inspect SEO projects
  • Run technical audits and retrieve the resulting audit report
  • Generate SEO articles and fetch generated articles
  • Check account status and list available plans and pricing
  • Long-running audits and articles return a job id that is polled with the matching get tool
When to use it
Use it when you want an assistant to handle recurring SEO work — auditing a site's technical health, producing SEO articles, or tracking projects — without building your own integration to the SERP Agent API.
Requirements
A SERP Agent API key (sk_...) supplied as the SERPAGENT_API_KEY environment variable for the npm stdio bridge, or as an Authorization Bearer header when connecting to the remote HTTP endpoint. Node.js/npx is needed only for the local bridge. Network access to the SERP Agent service.
Before you install
The API key is a secret; keep it out of shared configs and logs. The server creates projects, runs audits and generates articles, which writes data and may consume paid plan quota — check account status and plans first. Content and requests are sent to the third-party SERP Agent service.

Installation

In SourceWeft

  1. Open SERP Agent SEO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.serp-agent%2Fseo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "serp-agent-seo": {
      "type": "http",
      "url": "https://serp-agent.com/mcp"
    }
  }
}

README

serpagent-mcp

SERP Agent — full-cycle SEO automation for AI agents — as an MCP server.

This package is a thin stdio bridge for MCP clients that cannot speak Streamable HTTP directly. It proxies stdio ⇄ HTTP to the remote server at https://serp-agent.com/mcp (via mcp-remote). If your client supports remote HTTP servers, connect directly instead — see serp-agent.com/docs/mcp.

Tools

create_project, list_projects, get_project, run_technical_audit, get_audit_report, generate_article, get_article, get_account_status, list_plans — a thin layer over the SERP Agent REST API. Long-running jobs (audits, articles) return a job id immediately; poll the matching get_* tool.

Auth

Set SERPAGENT_API_KEY to your sk_... key. No key yet? Free sandbox key in one call, no CAPTCHA:

bash
curl -X POST https://serp-agent.com/v1/accounts \  -H "content-type: application/json" \  -d '{"email":"[email protected]"}'

Optional: SERPAGENT_MCP_URL overrides the server URL (default https://serp-agent.com/mcp).

Install

Claude Code

Prefer the direct HTTP transport:

bash
claude mcp add --transport http serpagent https://serp-agent.com/mcp \  --header "Authorization: Bearer sk_..."

Or via this stdio bridge:

bash
claude mcp add serpagent --env SERPAGENT_API_KEY=sk_... -- npx -y serpagent-mcp

Cursor

~/.cursor/mcp.json (or project .cursor/mcp.json):

json
{  "mcpServers": {    "serpagent": {      "command": "npx",      "args": ["-y", "serpagent-mcp"],      "env": { "SERPAGENT_API_KEY": "sk_..." }    }  }}

Direct HTTP alternative: { "serpagent": { "url": "https://serp-agent.com/mcp", "headers": { "Authorization": "Bearer sk_..." } } }

VS Code (Copilot agent mode)

.vscode/mcp.json:

json
{  "servers": {    "serpagent": {      "type": "stdio",      "command": "npx",      "args": ["-y", "serpagent-mcp"],      "env": { "SERPAGENT_API_KEY": "sk_..." }    }  }}

Links

License

MIT

Source: README.md at commit 6b6d999

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.