Give your agent a practical SEO playbook.

Connect a compatible agent

1. Create an organization and choose a monthly subscription.
2. Add a website you own or are authorized to manage.
3. Create a key for that website. Choose read-only access or allow audits.
4. Configure a Streamable HTTP MCP client that supports a custom Authorization header.

MCP endpoint: https://rankpropel.com/mcp
Authorization: Bearer YOUR_WORKSPACE_KEY

JSON API: POST https://rankpropel.com/api/agent
Content-Type: application/json
Authorization: Bearer YOUR_WORKSPACE_KEY

{"tool":"list_playbooks","arguments":{}}

This release uses workspace keys. Clients that require an OAuth-only connection are not supported yet. Keep keys in your agent’s secret store and send them only to rankpropel.com.

Example with Codex CLI

Make your workspace key available as RANKPROPEL_AGENT_KEY in the environment that launches Codex. Register the connection, then launch Codex from that same terminal:

codex mcp add rankpropel \
  --url https://rankpropel.com/mcp \
  --bearer-token-env-var RANKPROPEL_AGENT_KEY

codex

Use /mcp in Codex to check the connection. A desktop app may need its own environment setup. Codex MCP setup documentation.

Ask your agent to audit and prepare a fix

“Use RankPropel to list the playbooks and read the relevant guidance. Collect public HTML snapshots from my registered website and run an audit. Show the evidence, the improvement plan, and anything you could not verify. Review the content against the playbooks too. Prepare edits in my website project for me to review. After I approve and publish them, audit fresh snapshots and compare the two reports.”

Your agent needs its own browser or fetch tool to collect snapshots and separate permission to edit your website. RankPropel provides guidance and reports; the MCP key does not grant access to your CMS or hosting account. Automated checks cover a limited set of technical issues, so useful content review remains part of the agent's work.