Agent Seo Engine

io.github.davidmosiahPublished by GitHub account davidmosiahv0.1.1Updated Oct 27, 2026

Agent-first local SEO quality, intent and opportunity engine with CLI and optional MCP server.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local-first SEO engine that lets an assistant classify search intent, score markdown drafts for SEO gaps and prioritize search opportunities.

What you can do
  • Classify search intent as informational, navigational, transactional or commercial investigation
  • Score markdown articles for SEO gaps and return exact failed checks and recommendations
  • Prioritize Google Search Console-style opportunities by impressions, position, CTR gap, conversions and commercial value
  • Audit image alt-attribute coverage in HTML pages
  • Report install guidance, local readiness and privacy boundaries before content tools run
When to use it
Use it when an assistant is about to rewrite, refresh or publish content and you want deterministic, repeatable SEO checks rather than guesses. It suits content and SEO workflows where drafts and search performance figures are reviewed locally.
Requirements
Runs as a local Python package installed with pipx (agent-seo-engine, with the mcp extra for the MCP server) and started via the agent-seo-mcp command over stdio. No API keys are required; it runs locally by default.
Before you install
The server reads local draft files and HTML pages you point it at, and its privacy audit is meant to clarify draft, analytics and credential boundaries before use. Opportunity scoring depends on figures you supply, such as impressions, clicks and position, so results are only as good as that input. The README asks for repository stars and lists contact channels; treat those as promotional, not required setup.

Installation

In SourceWeft

  1. Open Agent Seo Engine in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Agent SEO Engine

Local-first SEO scoring, search-intent and opportunity engine for AI agents.
Deterministic checks before agents rewrite, refresh or publish content.

[PyPI version] [Python versions] [License MIT] [Built for MCP]

[GitHub stars] [CI status] [Part of the Delx agent stack] [Category]

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

bash
pipx install agent-seo-engine

With MCP support:

bash
pipx install "agent-seo-engine[mcp]"

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

bash
agent-seo-engine manifest --client codexagent-seo-engine doctoragent-seo-engine privacy-auditagent-seo-engine intent "best ai agent framework"agent-seo-engine score --file examples/article.md --primary-keyword "ai agent testing"agent-seo-engine opportunity --impressions 4200 --clicks 80 --position 12.4 --commercial-intent 0.8agent-seo-engine image-alt --file page.html

All commands return structured JSON by default. Use --format markdown for human review.

MCP

bash
agent-seo-mcp

Hermes-style config:

yaml
mcp_servers:  agent_seo:    command: agent-seo-mcp    args: []    sampling:      enabled: false

Recommended first calls:

  1. agent_seo_connection_status
  2. agent_seo_privacy_audit
  3. agent_seo_score_content

Agent Surfaces

ToolPurpose
agent_seo_manifestInstall/runtime guidance for agent clients
agent_seo_connection_statusLocal/offline readiness and optional integration status
agent_seo_privacy_auditDraft, analytics and credential boundaries
agent_seo_detect_intentSearch intent classification
agent_seo_score_contentMarkdown quality checks with exact recommendations
agent_seo_prioritize_opportunityGSC-style opportunity scoring
agent_seo_check_image_altImage alt-attribute coverage audit for HTML

Copy-Paste Agent Prompt

text
Use agent-seo-engine. First call agent_seo_connection_status and agent_seo_privacy_audit.Score the draft, then propose only edits tied to failed checks or high-impact opportunities.

Agent Contract

Agents should not guess whether a draft is ready. They should call the scoring tool, read exact failed checks, then propose focused edits. The engine is intentionally deterministic and local so repeated agent runs can compare output over time.

Development

bash
python3 -m venv .venv. .venv/bin/activatepip install -e ".[dev]"pytestpython -m compileall -q src

📧 Contact & Support

Source: README.md at commit cb5865e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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