Test Scenarios Index
Overview
Section titled “Overview”This folder contains ten end-to-end test scenarios for SEO Navigator MCP. Each scenario is written so a screen-recorder can follow it frame-by-frame to produce a short tutorial clip. The server under test is https://seo-navigator-mcp.autumn-recipe-cac7.workers.dev.
Run them in order on the first pass — later scenarios reuse state created earlier (the connector, the test site, the token).
Scenarios
Section titled “Scenarios”| # | Scenario | One-line summary | Duration |
|---|---|---|---|
| 01 | Add OAuth Connector | Install the MCP as a Custom Connector in Claude Desktop and complete OAuth. | ~4 min |
| 02 | List Tools and Sites | Verify the 🔌 menu lists 31+ tools and list_sites returns expected rows. | ~3 min |
| 03 | Write a Blog Draft | Ask Claude for a 300-word draft and confirm it lands as a WP draft post. | ~5 min |
| 04 | Schedule and Unschedule | Schedule a draft for tomorrow then revert it back to draft. | ~4 min |
| 05 | Diagnose a Site | Run diagnose_site on a WP site and read the five-check report. | ~3 min |
| 06 | Create Page From Code | Vibe-code a pricing page in chat and deploy it as a Gutenberg HTML block. | ~5 min |
| 07 | GitHub Content Team Flow | Writer pushes a markdown draft with frontmatter via save_md_to_github. | ~5 min |
| 08 | GitHub Design Team Flow | Designer picks up ready-for-design markdown and deploys it as a WP draft. | ~5 min |
| 09 | Create and Verify Astro Route | Vibe-code HTML, push as Astro route, wait for CF Pages build, visit live URL. | ~5 min |
| 10 | Fallback: Bearer Token via mcp-remote | Install the server using mcp-remote + a legacy bearer token. | ~5 min |
Notes for the recorder
Section titled “Notes for the recorder”- Each scenario has a Setup state block that describes the exact starting frame.
- Steps are numbered and each carries an Action, Expected, and Animation note (
*Recorder: ...*). - Keep each clip under five minutes; trim long Claude responses to the first useful chunk.
- Capture both happy path and the edge cases listed at the bottom of each scenario file.