Your AI assistant can already write copy and answer questions. What it could not do — until now — is open your store’s SEO state, see what is actually broken, fix it, and verify the fix landed. That is what RankEngine’s MCP server adds: a direct, permissioned connection between Claude (or any MCP-compatible agent) and your store’s SEO engine.

What your agent can do once connected

The connection exposes ten tools in two groups. The read tools give the agent your live SEO picture: site score and scan freshness, the full issue queue from the last scan, per-product SEO detail (meta fields, checklist, focus keyword), your AI-generated blog posts with quality scores, and the status of any background job.

The act tools do real work — through the exact same pipelines the RankEngine app uses, not a parallel path:

  • Run a scan to refresh the site score and issue queue from your store data.
  • Apply fixes: set a specific meta title or description (validated to 60/160 characters, keyword-first), run the one-click fix engine across missing meta and alt text, or launch the batch optimizer that pushes products toward a 95+ SEO score. Every fix is re-fetched from Shopify and verified before it is marked complete — the agent cannot claim success it did not achieve.
  • Draft blog posts: full pipeline with SERP research, quality gates, and a hero image. Drafts only — publishing from an agent is disabled at the server. You publish from Content Studio when you have read the post.

A typical session: “What are my worst products for SEO?” → the agent reads the issue queue → “Fix the missing meta on those five” → it launches the fix job, polls it, and reports back which fixes verified and how each product’s score moved. Real numbers from your store, not summaries of generic advice.

Setup in two minutes

  1. In your Shopify admin, open RankEngine → Settings → Connect an AI agent and click Generate pairing code.
  2. In Claude, add a custom connector (or in Claude Code / Codex, add a remote MCP server) with the URL https://app.rankengine.app/mcp.
  3. Your browser opens a RankEngine approval page. Tick what the agent may do — read, scan, fix, draft — and enter the pairing code.

That is the whole flow. The client handles OAuth discovery, registration, and token exchange automatically; you never copy a token by hand.

The security model, honestly

Agent access is a real attack surface, so the design is conservative:

  • Consent equals pairing-code authority. Only someone who can open your RankEngine settings inside the Shopify admin can mint a pairing code — so only they can approve an agent.
  • Per-tool permissions. At the approval page you grant scopes: read-only, scans, fixes, blog drafts. A read-only grant means the fix tools do not even appear in the agent’s tool list.
  • No Shopify credentials involved. The agent talks to RankEngine; RankEngine talks to Shopify with its own app permissions. Tokens are SEO-scoped, hashed at rest, expire after 90 days, and revoke instantly from Settings.
  • Same quotas as the app. Agent-triggered work draws on your plan’s existing limits — an agent cannot spend what your plan does not allow.
  • Verified or honest. Fixes report verified only after a live re-check against Shopify; failures come back as failures. The drafts-only rule for blog content is enforced server-side.

Why this matters for where search is going

Discovery is shifting toward AI surfaces — answer engines that read stores directly and agents that act on a shopper’s behalf. Merchants are starting to operate the other side of that shift too: using their own agents for daily operations. SEO work is unusually well-suited to it, because the work is structured — issues, fixes, verification — and an agent with the right tools can carry the loop end to end while you keep approval over anything public-facing.

If you already use RankEngine, the MCP connection is the same engine with a conversational interface on top. If you are evaluating Shopify SEO apps, agent access is worth adding to your checklist — it is the difference between an app you operate and an app your tools can operate with you.