No-code automation
Use HTTP workflow pages when the user wants to wire AgentSEO into orchestrators like n8n or Make without waiting for a native app or node.
Integration library
Pages for real integration intent, not generic logos on a homepage
This hub groups AgentSEO integration paths by how the product actually works today. Some are official packages, some are MCP setups, and some are disciplined HTTP workflow recipes.
MCP clients
Use MCP pages when the runtime should call AgentSEO tools directly from a model-driven environment such as Claude Code.
Agent runtimes
Use runtime-specific pages when AgentSEO ships a real package, plugin, or adapter that deserves first-party setup guidance.
First-wave pages
Launch pages with enough product truth behind them
SEO hub + spokes
No-code automation
n8n
Run AgentSEO inside n8n with HTTP Request nodes so SEO checks, content-gap jobs, and rank alerts can flow into broader automations.
Open guide
No-code automation
Make
Connect AgentSEO to Make with HTTP modules so search-intelligence jobs can trigger CRM updates, alerts, reports, and client handoffs.
Open guide
MCP client
Claude Code
Use AgentSEO inside Claude Code through MCP so the model can call SEO tools directly instead of scraping pages and guessing at next steps.
Open guide
MCP client
Claude Desktop
Use AgentSEO in Claude Desktop through the local MCP package so Claude can run SEO workflows without manual copying between tools.
Open guide
Agent runtime
OpenClaw
Install the first-party AgentSEO OpenClaw plugin to give OpenClaw agents direct access to SEO and GEO workflows with allowlisted tools.
Open guide
Editorial rule
Match the page promise to the actual integration type
Say this plainly
n8n and Make work through HTTP workflows. Claude Code works through MCP. OpenClaw has a published first-party AgentSEO plugin. That distinction is what keeps these pages credible.
Hold for later
Add Codex or other agent IDE pages only after there is a tested setup path with repeatable snippets and a clear conversion story.