Official description7 sourcesMCP servers8d ago
davidmosiah/agent-seo-engine
Local-first SEO quality, s
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add agent-seo-engine -- npx -y agent-seo-engine
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 0 ★ · davidmosiah/agent-seo-engine · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
davidmosiah/agent-seo-engine；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Agent SEO Engine
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Local-first SEO scoring, search-intent and opportunity engine for AI agents. Deterministic checks before agents rewrite, refresh or publish content.
mcp-name: io.github.davidmosiah/agent-seo-engine
> ⭐ **If this agent-first tool helps your workflow, please star the repo.** Stars make this tooling easier for other builders to discover and help Delx keep shipping open infrastructure.
> 🧱 Part of the Delx agent stack — 15 open-source MCP servers across **body, reach and coordination**.
---
Agent-first SEO scoring, search-intent detection and opportunity prioritization. It packages the useful parts of a production content pipeline into a clean local CLI plus an optional MCP server for Codex, Claude, Cursor, Hermes, OpenClaw and other agent runtimes.
Use it when an agent needs deterministic SEO checks before rewriting, refreshing or publishing content.
What It Does
- Classifies search intent: informational, navigational, transactional and commercial investigation
- Scores markdown articles for agent-readable SEO gaps
- Prioritizes GSC-style opportunities by impressions, position, CTR gap, conversions and commercial value
- Exposes manifest, connection_status and privacy_audit surfaces before content tools
- Runs locally by default with no required API keys
Install
With MCP support:
Published on PyPI: agent-seo-engine. Release automation uses PyPI Trusted Publishing, so GitHub Actions can publish future versions without long-lived PyPI tokens. See docs/pypi-publishing.md.
CLI
All commands return structured JSON by default. Use --format markdown for human review.
MCP
Hermes-style config:
Recommended first calls:
1. agent_seo_connection_status
2. agent_seo_privacy_audit
3. agent_seo_score_content
Agent Surfaces
| Tool | Purpose |
|---|---|
| agent_seo_manifest | Install/runtime guidance for agent clients |
| agent_seo_connection_status | Local/offline readiness and optional integration status |
| agent_seo_privacy_audit | Draft, analytics and credential boundaries |
| agent_seo_detect_intent | Search intent classification |
| agent_seo_score_content | Markdown quality checks with exact recommendations |
| agent_seo_prioritize_opportunity | GSC-style opportunity scoring |
| agent_seo_check_image_alt | Image alt-attribute coverage audit for HTML |
Copy-Paste Agent Prompt
mcp-name: io.github.davidmosiah/agent-seo-engine
> ⭐ **If this agent-first tool helps your workflow, please star the repo.** Stars make this tooling easier for other builders to discover and help Delx keep shipping open infrastructure.
> 🧱 Part of the Delx agent stack — 15 open-source MCP servers across **body, reach and coordination**.
---
Agent-first SEO scoring, search-intent detection and opportunity prioritization. It packages the useful parts of a production content pipeline into a clean local CLI plus an optional MCP server for Codex, Claude, Cursor, Hermes, OpenClaw and other agent runtimes.
Use it when an agent needs deterministic SEO checks before rewriting, refreshing or publishing content.
What It Does
- Classifies search intent: informational, navigational, transactional and commercial investigation
- Scores markdown articles for agent-readable SEO gaps
- Prioritizes GSC-style opportunities by impressions, position, CTR gap, conversions and commercial value
- Exposes manifest, connection_status and privacy_audit surfaces before content tools
- Runs locally by default with no required API keys
Install
With MCP support:
Published on PyPI: agent-seo-engine. Release automation uses PyPI Trusted Publishing, so GitHub Actions can publish future versions without long-lived PyPI tokens. See docs/pypi-publishing.md.
CLI
All commands return structured JSON by default. Use --format markdown for human review.
MCP
Hermes-style config:
Recommended first calls:
1. agent_seo_connection_status
2. agent_seo_privacy_audit
3. agent_seo_score_content
Agent Surfaces
| Tool | Purpose |
|---|---|
| agent_seo_manifest | Install/runtime guidance for agent clients |
| agent_seo_connection_status | Local/offline readiness and optional integration status |
| agent_seo_privacy_audit | Draft, analytics and credential boundaries |
| agent_seo_detect_intent | Search intent classification |
| agent_seo_score_content | Markdown quality checks with exact recommendations |
| agent_seo_prioritize_opportunity | GSC-style opportunity scoring |
| agent_seo_check_image_alt | Image alt-attribute coverage audit for HTML |
Copy-Paste Agent Prompt
- Source
- awesome · https://github.com/davidmosiah/agent-seo-engine
- Browse by field
- MCP servers
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.