Use case
Build an SEO Content Agent
Automate keyword research, draft SEO-optimized articles, and publish them to a CMS without manual handoffs.
Most content workflows break at the handoff points. A writer researches in one tab, drafts in another, and manually pastes into a CMS. An SEO content agent collapses those steps: it reads a keyword brief, searches for top-ranking competitors, drafts structured content with proper heading hierarchy, and posts to your CMS via API. The people building these are growth engineers and solo founders who have a content strategy but not the headcount to execute it at volume.
The stack
Each pick is a real entry on the index. Click any one for the full detail page.
- 1A Agents Orchestrator
Claude Code
by Anthropic
Why this: Claude Code runs the full pipeline as a scripted agent: read keyword list, trigger search, draft article, call CMS API. It handles branching logic like skipping keywords already covered and reformatting drafts that fail a readability check.
Full entry - 2M MCP Keyword Research
Brave Search MCP
by Brave (reference implementation)
Why this: Brave Search MCP gives the agent live SERP data without hitting rate limits or requiring a browser. It pulls top-ranking URLs and titles for a keyword so the agent can analyze what format and depth is ranking before drafting.
Full entry - 3M MCP Competitor Scraping
Playwright MCP
by Microsoft
Why this: For URLs returned by Brave, Playwright MCP fetches the actual page content so the agent can read heading structure, word count, and internal linking patterns. This grounds the draft in what is actually ranking, not assumptions.
Full entry - 4M MCP CMS / Draft Store
Notion MCP Server
by Notion
Why this: Notion MCP writes the finished draft into a database with status, target keyword, and word count fields. Teams that review before publishing use Notion as the approval layer before a second agent posts to the live CMS.
Full entry - 5S Skills Source Discovery
Deep Research Skill
by Community
Why this: The research skill handles multi-source synthesis: pulling from search results, pulling citations, and normalizing them into a references block the agent appends to each draft. This keeps the content grounded rather than hallucinated.
Full entry
Get this running with Enterprise DNA.
Enterprise DNA gives the SEO agent a project context so every keyword batch is tracked as a work item with status and output. Secrets for your CMS API key and Brave API key live in the EDNA secrets store, not in the script. The inbox layer routes approval requests back to the operator when a draft needs human review before posting.
Get the Stack Blueprint
A printable architecture card with every tool, role, and rationale on one page.
Enter your email. We send one useful update per week. Unsubscribe any time.
In the print dialog, choose "Save as PDF" as the destination.
Alternative stacks
Different angles on the same outcome.
Content Publishing Pipeline
If your bottleneck is publishing and scheduling rather than research and drafting, the content publishing pipeline covers CMS integration, scheduling queues, and social syndication.
See the alternative AlternativeMulti-Agent Research Team
For high-volume or high-accuracy content that requires parallel research across many sources before a single draft is written.
See the alternativeOther use cases
More curated stacks from the index.
Build a customer support agent
A working customer-support agent that triages tickets, answers from your docs, and escalates with full context.
See the stack Use caseBuild a research agent
An agent that watches sources, synthesises findings, and ships you a briefing on the days something matters.
See the stack Use caseBuild a sales outreach agent
An outreach agent that drafts personal-feeling email, qualifies replies on the phone, and updates the CRM without anyone copy-pasting notes.
See the stack