Your site plan is a list of concrete work: a page URL, the evidence, ordered steps, an outline, the facts you must supply, and copy to paste. That is exactly what a coding agent needs. This page shows how to hand it over, what the agent can and cannot do, and how you see the result.
What the agent can do
- Read the plan and every page we crawled, item by item.
- Make the changes in your repo or CMS with its own tools.
- Mark each item done with a one-line note and the URL it changed. We re-read that page within seconds and tell the agent whether the issue is gone.
- Ask you for facts it does not have (prices, limits, hours) and record them so the paste-ready sentence is complete.
- Draft a planned article through Autopilot on Pro, then tell us where it was published.
What it cannot do
Start a scan, crawl the site, or publish anything. Those stay behind a click by you. Every write the agent makes is logged with the agent's name, shown on the plan, and can be undone.
1. Connect
Create an API key on the Plan & settings page and set its scope to read and write. Then:
Claude Code, one command:
claude mcp add --transport http tangentflow https://tangentflow.com/api/mcp/site --header "Authorization: Bearer tf_…"
Cursor, Claude Desktop, Windsurf: paste into the MCP config.
{ "mcpServers": { "tangentflow": { "url": "https://tangentflow.com/api/mcp/site", "headers": { "Authorization": "Bearer tf_…" } } } }
Any agent that reads files: download PLAN.md from the plan page, or point the agent at https://tangentflow.com/api/sites/<site id>/plan.md?key=tf_…. Every item carries its key. To mark one done without MCP:
POST https://tangentflow.com/api/sites/<site id>/plan/items/<key>/complete
Authorization: Bearer tf_…
{ "note": "Rewrote the pricing page as sentences", "changed_urls": ["https://example.com/pricing"], "client": "codex" }
2. The prompt that works
Use the tangentflow MCP server. Call get_plan for site N with status todo. Work through the technical and fact items first, in priority order. For each item: read the page with get_plan_item, make the change in this repo, then call complete_item with a one-line note and the URL you changed. For fact items, ask me for any fact you do not have before writing it. Do not create new pages until every technical item is done. Stop after 10 items and show me what changed.
Replace N with your site id, shown in the plan page URL.
3. A note for your repo
Drop this in CLAUDE.md or AGENTS.md so every session knows the rules:
## TangentFlow site plan
The AI-visibility plan for this site lives on the tangentflow MCP server (site N).
- Start with get_plan status=todo. Do technical and fact items before creating pages.
- Never invent facts, prices, numbers or customers. Ask before writing anything under facts_needed.
- After each change, call complete_item with the URL. If it comes back unchanged_page, read page_check.detail and fix it.
- Keep the site's existing voice. Do not remove content to satisfy a check.
Tools
| Tool | What it does |
|---|---|
get_plan |
Items still to do, with url, evidence, steps, outline, facts needed, copy. status: all includes finished items. |
get_plan_item |
One item plus the crawled page: title, H1, H2s, word count, signals, first 1,500 characters. |
get_pages |
Every page read: path, role, title, words, issues. |
complete_item |
Marks done, re-reads the changed URL, returns verified_page or unchanged_page with what is still missing. For a new page, pass published_url. |
dismiss_item, reopen_item |
Not applicable, with a reason; and undo. |
supply_fact |
Sends facts from you as name → value and returns the sentence with them filled in. |
draft_article |
On Pro: drafts a planned article through Autopilot and returns the markdown. |
get_activity |
What agents and you did recently, so a new session can continue. |
list_sites, get_visibility, get_questions, get_tasks, get_history |
The read tools that were already there. |
What verification means
- On the page, in seconds. When an item is completed we fetch the URL and re-run the check that raised it: a thin page needs at least 250 words; a missing title must be present; noindex must be gone; a fact must appear in the text; a new page must be live with text.
- In the answers, in weeks. Every weekly check re-asks the same questions. When a question the item targeted flips to naming you, the item becomes verified: answers moved. Four quiet checks mark it no change.
Limits
600 tool calls and 60 page re-checks per key per day. Re-checks only fetch pages on your own domain. Notes and facts are stored as plain text. A read-only key can call every get_ tool and nothing else.