Headless Guides & Surveys: Manage Guides and Surveys from the Developer API, CLI, and MCP
Guides and surveys are finally fully supported for headless operation. Customers and their AI agents can list, read, create, edit and archive guides and surveys through the Amplitude Developer API, the amp CLI, and Amplitude MCP.
What it is
Description: Guides and surveys are finally fully supported for headless operation. Customers and their AI agents can list, read, create, edit and archive guides and surveys through the Amplitude Developer API, the amp CLI, and Amplitude MCP. They can draft an onboarding tour from AI agents, copy a survey into another project from a script, or bulk-update copy across dozens of guides, without opening the editor.
Why: Teams are building with agents, and external MCP tools for Guides and Surveys only supported read operations and even those were fairly limited. Agents could already read a chart or find a drop-off but couldn't ship the guide or survey that addresses it. Now the whole loop (find the problem, draft the guide, review it) can run headless. It runs on the same validation, permissions and version history as the editor, so anything an agent creates looks and behaves like something built in the UI.
What's in it:
- Developer API:
GET/POST /v1/projects/{project_id}/guidesand/surveys, plusGET/PATCH/DELETEon single items. Writes useguides:write/surveys:writescopes, anIdempotency-Key, andlatest_versionso concurrent edits can't overwrite each other. - CLI:
amp guides list|get|create|update|archiveandamp surveys list|get|create|update|archive- scheduled for forthcoming CLI release. - MCP:
run_ampcovers guides and surveys, so any MCP client can do the same through natural language. - Safe by default: new guides and surveys are always created as unpublished drafts. Edits to a live guide save as unpublished changes. Archiving a published guide or survey is refused. Publishing, targeting and flag changes remain in the UI for human review.
Where: