DispatchSEO

io.github.NeoZi12Published by GitHub account NeoZi12v1.1.0Updated Nov 9, 2026

Open-source SEO manager for coding agents: keyword research, content PRs, rank + Search Console.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for DispatchSEO, an SEO manager that lets an agent research keywords, queue and build articles, and track rankings and Search Console data.

What you can do
  • Research keywords and trend topics, and queue ideas with reasoning attached
  • Review the idea queue: approve, reject or reorder pending articles
  • Build guides and small free tools, delivered as pull requests to a GitHub repo or posted to WordPress
  • Read rankings, Search Console stats, tracked pages and site profile data
  • Work with backlink prospects and reports
  • Manage multiple sites, each with its own token and data
When to use it
Use it when you want a coding agent or the Claude app to run ongoing SEO work for a site you control: finding winnable keywords, drafting and publishing articles, and checking how pages rank. It suits teams already publishing through a GitHub repo or self-hosted WordPress.
Requirements
A remote endpoint at dispatchseo.com with OAuth sign-in. Self-hosting needs a machine with Docker (about 1 GB RAM) that stays awake for schedules, Google Search Console access, and either a self-hosted WordPress site with an application password or a GitHub repo for your site's source. An AI agent drives the work; optional SerpApi or DataForSEO keys add SERP and volume data.
Before you install
The server writes to your site: it opens pull requests or posts to WordPress, and auto mode can skip the approval queue, so review before enabling it. It needs Google Search Console access and, for WordPress, an application password, plus a per-project MCP token. Optional SerpApi and DataForSEO tiers can incur per-call charges. Hosted plans beyond the free two articles a month are paid.

Installation

In SourceWeft

  1. Open DispatchSEO 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/io.github.NeoZi12%2Fdispatchseo/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": {
    "dispatchseo": {
      "type": "http",
      "url": "https://dispatchseo.com/api/mcp"
    }
  }
}

README

[DispatchSEO logo]

DispatchSEO

[License: AGPL-3.0] [Built for Claude Code, Codex, and Cursor] [Self-host in one command] [Join the Discord]

Free SEO automation: researched articles, published to your site on autopilot


DispatchSEO: an open-source alternative to SEObot, Outrank and RightBlogger.

 DispatchSEO researches keywords with real search demand, writes fact-checked articles and publishes them for you,
as pull requests to your GitHub repo or on a hosted blog, then shows the Google visitors they bring.
Two articles a month are free on dispatchseo.com, no card. Paid plans publish 1, 3 or 5 a week.

Self-hosting it instead? The whole thing runs in your own accounts, driven by Claude Code, Codex, or Cursor over MCP, including the unattended overnight builder.


[Install now]   [Read the docs]

Website  ·  Discord  ·  Discussions  ·  Hosted version

Self-hosted has zero feature limitations. Everything the paid
cloud does, this repo does today, in your own accounts, at $0.


⚡ How it works

  1. Your AI researches. The Claude app at claude.ai, or a coding agent (Claude Code, Codex, Cursor), connects to DispatchSEO over MCP, reads the served playbook, and mines keywords from your Search Console data, Google Autocomplete, and what it already knows about your product. Ideas land in a queue with the reasoning attached.
  2. You approve, or don't. Each idea is a card on the dashboard: the keyword, why it's winnable, the angle. Approve, reject, or reorder. Prefer full autopilot? Flip on auto mode and skip the queue entirely.
  3. The pipeline builds. Every morning a scheduled job picks the oldest approved idea and builds it into a real pull request against your site's repo: a guide or a small free tool, checked against the live SERP and run through a sameness reviewer so page twelve doesn't read like page three.
  4. It tracks what happened. Daily rank checks, hourly Search Console snapshots, index verification, and a journey view that tells you which SEO stage you're actually in. When a scheduled job breaks, you get a red banner and an email instead of silence.

The backend is deliberately boring: state, scheduling, and an approval gate. The thinking happens in your agent, where your product knowledge already lives.

[The dashboard Home: the agent's daily briefing in plain language, the journey stage, publishing pace, and live Search Console stats for a connected site]
[The queue: keyword ideas with volume and difficulty, each waiting for approval or set to auto][A pull request the pipeline built: target keyword, SERP gate verdict, archetype, and information-gain asset, all named in the description]
[Search traffic: clicks and impressions from Google Search Console, snapshotted hourly][Keyword rankings: daily position checks with 30-day trend sparklines]

🤖 Which coding agent

DispatchSEO talks to your agent over MCP, so "which agent" is a real question with a real answer — including the parts that aren't finished yet.

AgentConnect + every toolUnattended overnight builder
Claude Code✅✅
Codex✅✅
Cursor✅ one-paste connect, all 61 tools✅ via its API key (any plan mints one)
Gemini CLI · Copilot · any MCP client✅❌

Connecting is one paste and gets you the whole tool set: research, the queue, approvals, backlinks, reports, and building a guide when you ask for one. The overnight builder is the separate thing — scheduled jobs that run an agent with nobody watching — and all three do that. Every workflow carries every agent and asks the dashboard which to run, so switching agent takes effect on the next scheduled run with no repo change.

The honest difference is who pays: Claude Code runs on a subscription you already have, Cursor runs on your Cursor plan's API key, and Codex is metered by OpenAI per run.

You can also skip coding agents entirely. Add DispatchSEO to the ordinary Claude app at claude.ai as a custom connector and your Claude does the research and the writing on the subscription you already have, then hands the article back for the backend to check, finish and publish. It won't build interactive tools or run the overnight builder, and claude.ai has to be able to reach your install, so that path wants a public URL rather than a laptop. ChatGPT can't connect yet.

docs/AGENTS.md has the details, the support tiers, and how to add an agent.

✅ What you need before you start

  • Somewhere to publish. Either WordPress you host yourself, connected once from Settings with an application password and posted to directly, or your site's source in a GitHub repo, where content arrives as pull requests. Wix, Squarespace, Shopify, Webflow and Ghost have neither door and won't work.
  • An AI to drive it. Your AI is the engine, and it can be the ordinary Claude app at claude.ai or a coding agent. Claude Code runs on the Claude subscription you already pay for; Codex and Cursor do everything Claude Code does here, including the overnight builder. Codex is metered by OpenAI per run, and Cursor builds draw on your Cursor plan's included usage. See the table above.
  • A machine with Docker (~1 GB RAM). A laptop works for a test drive, but a machine that stays on is much better for daily use - a $5 VPS, a Raspberry Pi, a desktop that never sleeps. Schedules only run while the machine is awake.
  • Google Search Console access to your site.

That's the whole list. No API keys to buy, and no account on our side.

📖 Documentation

Everything is at dispatchseo.com/docs - every page, every setting, every tool.

New hereWhat DispatchSEO is · How it works · Cloud or self-hosted
InstallQuickstart - your own computer, a VPS, or from source
Set upInstall Claude Code · Install Codex · Install Cursor · The setup wizard · Search Console · Keyword data · Publishing · Connect your site
Use itDay to day · The dashboard · Automations · Agent commands
ReferenceConcepts · MCP tools · Environment variables · Schedules · Architecture
HelpTroubleshooting · Common questions · Security · Upgrading

Pointing an agent at this? Add .md to any docs URL for clean markdown, or fetch the entire documentation set in one request: llms-full.txt. There's an index at llms.txt and a SKILL.md that walks an agent through connecting a site.

Stuck during setup? The troubleshooting page covers the errors people actually hit. If yours isn't there, ask in the Discord or in Discussions - questions get answered and usually turn into a docs fix.

🗓️ Using it day to day

Once the wizard is done, the loop is small on purpose:

WhenYou doIt does
Once a week, 5 minutesOpen the dashboard, work through the queue - approve, reject, reorderRefills the queue with researched ideas and the reasoning behind each one
Every morningNothingBuilds the oldest approved idea into a pull request on your repo
When a PR landsReview and merge (or let auto-merge do it)Logs the page, requests indexing, starts tracking its keyword
Whenever you wantAsk your agent: "research keywords for me", "what should I write next?", "how are we ranking?"Answers from live data over MCP - same state the dashboard shows

The dashboard's Home page always names the next action, so you don't have to work out what to do when you open it.

🧰 What's in the box

  • MCP server with the full tool set: the queue, keywords, rankings, pages, GSC stats, backlink prospects, trend topics, site profile. Anything the dashboard can do, your agent can do over MCP; parity between the two is a hard rule in this codebase.
  • Trend radar: scan for rising topics in your niche, expand a topic into concrete guide angles, and queue the good ones.
  • Guide and tool builders: guides publish at most one per day, flat and permanent (so a queue of thirty approved ideas doesn't become thirty posts in a week); free-tool ideas build on approval.
  • Backlink playbook: a prospect list prefilled with your product's copy, tracked per submission.
  • Multi-site: one deployment manages any number of sites. Each project gets its own MCP token, its own data, its own settings.
  • A password-gated dashboard for the one human in the loop.

💵 What it costs to run

Nothing, unless you want paid data. The tiers stack:

TierPriceWhat you get
Search Console only$0Rankings from GSC, keyword ideas from Autocomplete plus your own impression data
+ SerpApi free key$0Live SERP checks, real positions weekly (250 free searches/month)
+ DataForSEOpay per callSearch volume, keyword difficulty, domain rating

Free mode finds keywords you can win. Paid mode also knows which ones are worth winning.

☁️ Cloud version

There's a hosted version for people who'd rather not run a machine: we host it, bundle the SERP + volume data into one bill, and replace the Google service-account ritual with one click. It's at dispatchseo.com. Self-hosting stays feature-complete either way - the cloud sells convenience, not capability.

🧑‍💻 Developing from source

bash
git clone https://github.com/NeoZi12/dispatchseocd dispatchseopnpm installcp .env.local.example .env.localpnpm dev

This is the contributor path, not the way to self-host - that's the one-command Docker install behind the button at the top. Fill in .env.local (Supabase + the three secrets) before starting, then open the dashboard on localhost:3000.

pnpm build is the typecheck - run it before opening a PR. There is no separate lint or test setup.

🏗️ Architecture, briefly

Next.js App Router, Postgres for state (a bundled container when self-hosted, Supabase in the cloud version), mcp-handler for the MCP server at /api/mcp. Schedules and builds run in-stack (cron + builder containers) or on GitHub Actions. One deployment is multi-tenant: the MCP bearer token selects the project, crons loop over all projects, the dashboard switches with a cookie.

Architecture covers this properly. CLAUDE.md has the full conventions; it's written for agents, which turns out to make it decent documentation for people.

🤝 Contributing

Issues before PRs, and you must understand every line you submit, including the AI-assisted ones. Details in CONTRIBUTING.md. Questions go to Discussions or the Discord; vulnerabilities go through private reporting.

📄 License

AGPL-3.0. Use it, self-host it, fork it. If you run a modified version as a service, share the source. That's the whole deal.

Built by NeoZi12 · If DispatchSEO is useful to you, a ⭐ helps other people find it.

Source: README.md at commit a0a6a25

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

85% 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