AltoRank MCP server

AltoRank

An AI SEO content engine where every publish is somebody's decision.

It researches a keyword, writes the article, scores it, checks its claims, and publishes it to your CMS. Who decides that it ships is yours to choose per workspace: approve each draft by hand, or set a rule that publishes after a hold unless you hold it. Either way the approval is recorded under a named person, and the article is tracked after - indexing, rank, AI-search visibility.

Open source, the whole product. No feature-gated tier, no ee/ directory.

Status: pre-launch

Read this before you invest time in it.

attached to it, and that is on purpose.

• No paying customers, no case studies. Nothing here has a growth figure

apps/web/scripts/cli.ts into an altorank binary (npx altorank auth whoami once it is published); until then, npm run cli from apps/web drives the same agent API from a checkout. skills/altorank/SKILL.md is the skill file a coding agent reads, and it does install with npx; see below.

• The CLI is publishable, not yet on npm. packages/altorank-cli bundles

Supabase and your own API keys.

• The hosted dashboard is what runs today. It works locally against your own

If you want a finished product, wait. If you want to read how it works or run it yourself, everything is here.

The publishing decision

One gate, two ways through it. lib/publishing/core.ts refuses any article that is not approved (or scheduled with approved_by set), and nothing else in the code path writes live. What can write an approval:

publish cron runs the same checks the Approve button runs - active plan, no unsourced figure, no failing audit item, SEO score at or above the floor - after a hold window (default 24h) during which the drafted email carries a one-click Hold. approvedby is whoever turned the rule on; approvalkind says auto. Held drafts carry the reason on their own row. See lib/publishing/auto-approve.ts.

• A person, from the editor (approveArticle), recorded as approved_by.
• A rule the workspace owner set (auto_approve, migration 079): the

What cannot write an approval: an agent. The MCP server and the agent API expose no publish or approve tool - not disabled, absent. See the comment at the top of apps/web/scripts/mcp.ts.

Competing tools ship the words "you stay in control" as copy. The difference is checkable here: every live row points at a person, by click or by rule.

What works today

Publishing destinations (apps/web/lib/cms/adapter.ts) — thirteen adapters covering ten CMS platforms; WordPress is reachable two ways, and git and webhook are publishing targets rather than CMSs. Framer, Ghost, git, HubSpot, Magento, Notion, Shopify, Webflow, webhook, Wix, WooCommerce, WordPress, and the WordPress plugin — a second, recommended route to WordPress that installs a plugin and takes a per-site token instead of an application password (apps/web/lib/cms/wordpress-plugin.ts), which is why WordPress appears twice.

Install the skill

npx skills add AltoRank/altorank

Shortened. The full README is on GitHub.