エージェントを強化
公開元自身の URL です。PlugMCP のエンドポイントではありません。
キーとログ付きでコピーをホスト。
https://dispatchseo.com/api/mcp上の Claude ボタンを押すと、名前と URL が入力された状態で Claude が開きます。確定の操作は Claude 側で行います。
claude mcp add --transport http neozi12-dispatchseo https://dispatchseo.com/api/mcpRun in a terminal.
{ "mcpServers": { "neozi12-dispatchseo": { "command": "npx", "args": [ "-y", "mcp-remote", "https://dispatchseo.com/api/mcp" ] } }}claude_desktop_config.json
リモート URL か、手元のマシンのコマンドか 2 つのインストール方法の違い
PlugMCP で実行
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
起動公開元より
Free SEO autopilot: researched articles published to your site, for any site in a GitHub repo, including Lovable sites. Hosted at dispatchseo.com (2 free articles per month), or self-host this repo and drive it with Claude Code, Codex or Cursor over MCP. Open source (AGPL).
The backend is deliberately boring: state, scheduling, and an approval gate. The thinking happens in your agent, where your product knowledge already lives.
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.
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.
That's the whole list. No API keys to buy, and no account on our side.
Everything is at dispatchseo.com/docs - every page, every setting, every tool.
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.
Once the wizard is done, the loop is small on purpose:
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.
Nothing, unless you want paid data. The tiers stack:
Free mode finds keywords you can win. Paid mode also knows which ones are worth winning.
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.
git clone https://github.com/NeoZi12/dispatchseo
cd dispatchseo
pnpm install
cp .env.local.example .env.local
pnpm 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.
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.
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.
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.
Free SEO autopilot: researched articles published to your site, for any site in a GitHub repo, including Lovable sites. Hosted at dispatchseo.com (2 free articles per month), or self-host this repo an
{ "mcpServers": { "neozi12-dispatchseo": { "url": "https://dispatchseo.com/api/mcp", "headers": {} } }}概要
Free SEO autopilot: researched articles published to your site, for any site in a GitHub repo, including Lovable sites. Hosted at dispatchseo.com (2 free articles per month), or self-host this repo and drive it with Claude Code, Codex or Cursor over MCP. Open source (AGPL).
ツール
ツール一覧はまだありません。リモートサーバーは、最初のヘルスチェック後に取得されます。
よくある質問
このページで Cursor、Claude Desktop、Claude Code、VS Code 用の http 設定をコピーできます。PlugMCP のプロキシではなく、公開元のインストール方法を使います。
このレコードに必須の環境変数は記載されていません。
Dispatchseo には HTTP で接続します。
最終チェックは 2026-11-15 です。 Free SEO autopilot: researched articles published to your site, for any site in a GitHub repo, including Lovable sites. Hosted at dispatchseo.com (2 free articles per month), or self-host this repo and drive it with Claude Code, Codex or Cursor over MCP. Open source (AGPL).