set_step_blurRedact without opening the editor
Ask your assistant to blur an email, an API key or a customer name. It looks at each step's screenshot, finds the spot and draws the blur box for you.
Connect Claude, ChatGPT, Cursor or VS Code to Escourtly through the Model Context Protocol. Blur sensitive data, rewrite captions, read drop-off analytics and publish your product demo, all from one chat.
https://escourtly.com/api/mcpIn my onboarding demo, blur the email address on step 3.
Example conversation. Demo names and numbers are illustrative.
Works with the AI assistants you already use
The Escourtly MCP server gives your assistant the same controls you have in the demo editor. You say what you want; it finds the right demo and step and does the work, as you.
set_step_blurAsk your assistant to blur an email, an API key or a customer name. It looks at each step's screenshot, finds the spot and draws the blur box for you.
update_stepShorten every caption, match your brand voice or translate a whole interactive demo in one message instead of editing step by step.
get_demo_analyticsFind the step where viewers drop off, compare demos, and get a suggested fix, straight from your funnel data.
copy_steps_from_demoCopy your login flow into every product demo, duplicate a step, reorder the story or drop the steps where you were just scrolling.
configure_lead_captureGate a demo with a lead form, change the CTA button and link, and pull your newest leads into the chat.
publish_demoEdits land in the draft, exactly like the editor. Say the word and your assistant publishes the interactive demo to its share link.
Add https://escourtly.com/api/mcp to Claude, ChatGPT, Cursor, VS Code or any client that speaks the Model Context Protocol.
Your assistant opens the Escourtly sign-in page. You see exactly who is asking, then click Allow access. No API key to copy.
"List my demos." "Blur step 3." "Publish it." Your assistant calls the Escourtly MCP tools and reports back.
Works in Claude on the web and in Claude Desktop.
Need an API key for a script instead? See API keys in the docs.
Read demos, analytics and leads; edit steps, blur, zoom, hotspots and branding; then publish. Edits land in the draft, so your live interactive demo only changes when you publish.
list_demosget_demoget_demo_analyticslist_leadslist_deleted_stepsupdate_demoupdate_stepmove_stepreorder_stepsset_step_blurset_step_zoomset_step_hotspotset_step_calloutset_step_render_moderevert_content_editscopy_steps_from_demoduplicate_stepdelete_steprestore_stepupdate_customizationconfigure_lead_capturepublish_demounpublish_demodelete_demoRecording new screens still happens in your browser with the Escourtly Chrome extension. Your assistant builds on what you record.
The assistant only sees and changes your own demos and leads, through the same permission checks as the editor.
PKCE, one-hour access tokens bound to the Escourtly MCP server, and an approval screen before anything is shared.
Deleting, unpublishing or reverting is flagged so your assistant confirms with you. Deleted steps sit in the trash for 30 days.
Every connected app is listed with when it was last active. One click cuts off new access. API keys are stored only as fingerprints.