ExplainPlan for Agents

ExplainPlan turns a plain-text script into a live, shareable, animated presentation. The markup is the native medium of LLMs — agents author decks directly, no browser and no design tools required.

Connect

Remote MCP server (Streamable HTTP): https://explainplan.ai/mcp

Add that URL as an MCP connector in any Model Context Protocol host. No install, no SDK. The full machine-readable guide is llms.txt; the grammar manifest is /grammar/v3.json.

Hand this to your agent

Human handing off to an agent? Paste this:

Make a presentation using ExplainPlan. Connect to the MCP server at
https://explainplan.ai/mcp and read https://explainplan.ai/llms.txt
for the authoring guide. Author the script, validate it with
validate_script, inspect it with scene_report, render a scene with
render_scene to see it, then ask me to sign in so you can save the
deck with create_deck.

Tools

Anonymous (no sign-in)Requires sign-in
get_grammar, list_themes, list_layouts, get_examples, validate_script, scene_report, search_images, begin_login create_deck, update_deck, update_scene, get_deck, list_decks, delete_deck / restore_deck, list_revisions / restore_revision, render_scene, render_deck, list_assets, upload_asset, search_feedback, upvote_feedback, submit_feedback

render_scene returns a PNG of one scene — the true visual, exactly as rendered — so you can verify a layout, not just read a structural summary (requires sign-in).

The loop: get_grammar → author → validate_script → scene_report → render_scene (see it) → revise → save → deliver the /p/ link.

Sign-in (step-up)

A save tool called without a token returns HTTP 401, ERR_AUTH_REQUIRED, with a WWW-Authenticate challenge pointing at the OAuth protected-resource metadata (/.well-known/oauth-protected-resource). Two ways through:

  1. Standard OAuth 2.1 (authorization code + PKCE, dynamic client registration supported) — use the flow advertised in the metadata. Scopes: openid email profile offline_access.
  2. begin_login — for environments that cannot catch a browser redirect (VMs, CLI agents): call the tool, show the human the returned authorize_url, then poll poll_url with the poll_secret until status: complete delivers an access token (one-time delivery). Send it as Authorization: Bearer <token>.
  3. Refreshing — access tokens last about an hour. POST {"refresh_token": "…"} to the refresh_url that begin_login returns for a new access token (keep the newest refresh token); only re-run begin_login if refresh fails. OAuth connector clients should request offline_access.

Machine-readable index

ResourceURL
Agent guide/llms.txt · /llms-full.txt (complete docs, one fetch)
API catalog (RFC 9727)/.well-known/api-catalog
MCP discovery/.well-known/mcp
OAuth protected-resource metadata/.well-known/oauth-protected-resource
Agent card (A2A)/.well-known/agent-card.json
Grammar manifest/grammar/v3.json
Human reference/reference · /playground