Use Scribe with AI agents and WebMCP
WebMCP lets a compatible AI agent work with the Scribe project you already have open. Scribe publishes typed site tools for intentional editor operations—such as inspecting scenes, editing text, arranging objects, adding keyframes, or preparing an export—without giving the agent raw application state or relying on button clicks.
Want the practical walkthrough? Start with Use Scribe Animator with ChatGPT/Codex Site tools, then return here for the compatibility, security, and developer reference.
What stays the same
- Agent actions update the real, visible project. There is no hidden second editor.
- Normal authentication, project permissions, plan limits, media limits, and export limits still apply.
- Reversible local edits use Scribe history, so Undo remains available.
- Locked objects stay locked until you explicitly unlock them.
- Scribe does not host an LLM for this feature. Intelligence comes from your compatible browser agent.
What an agent can do
The Desktop editor exposes a discoverable semantic catalog across projects, scenes, objects, selection, layout, text, equations, assets, vector tracing, boards and drawing materials, Smart Connectors, Timeline/keyframes/curves, Draw Steps, camera, path following, audio, video, screen recording, templates and AI JSON, persistence, export, sharing, account capabilities, plugins, and useful editor views.
The complete catalog remains searchable through a stable set of site tools. Core project, scene, history, selection, playback and job controls stay available for the session. For other tasks, an agent searches with scribe_search_capabilities, obtains the exact input schema with scribe_get_capability, and calls scribe_execute_capability. It can use any reachable capability without changing the browser's registered tools.
Existing prompts can still call scribe_activate_capabilities, which now records logical preferences only. It does not replace tool definitions or cancel running work.
Availability is contextual. For example, a search can find video-trim capabilities while explaining that they are unavailable when the project has no video object. Ask the agent to inspect capabilities and project state before making a complex change.
Shapes catalog versus primitive shapes
Scribe's Shapes tab contains a public catalog of editable SVG presets. A compatible agent can search that same catalog with the shape asset type, inspect stable preset metadata, and insert a selected result as a native drawing. This is separate from creating primitive rectangles, circles, or polygons. If you want a catalog arrow, star, or speech bubble, tell the agent to use the Shapes catalog rather than Drawings or primitive shape creation.
Reference-driven reconstruction
For reference-driven work, a visual target and supplied artwork can become independent editable objects rather than one flattened image. Follow the reference reconstruction workflow for asset inventory, vector-versus-native decisions, semantic naming, frame checks, narration timing, camera holds, and continuity safeguards. A reference alone does not guarantee a pixel-perfect match.
Start with the Site tools quickstart if you first need to confirm client support and make a safe edit.
For an original whiteboard or motion explainer, use the Scribe Animator Director workflow: plan the narrative, build the settled composition, add relationships and motion through their owning capabilities, then review exact frames and playback. The Director 2.0.0 skills package supplies instructions and offline validation; the open Scribe page supplies live WebMCP tools. Each has its own access prerequisites.
Current authoring and review behavior
| Task | Capability and behavior to inspect |
|---|---|
| Arrange existing timing | timeline.compose places exact Draw Steps or contiguous property-key ranges in sequence, parallel, or stagger while preserving durations. Eligible temporary Circumscribe/Trace Highlight annotations move with their sole Draw Step and visible range. Ownership conflicts reject the change. |
| Check attached connectors | connector.inspect returns persistedGeometry, evaluatedGeometry, and evaluatedAt. Supply the scene and local time; compare the evaluated endpoints with the displayed frame. |
| Set a static camera | camera.set_fixed_pose and camera.fit_to_objects update the fixed view. Repeating the same effective pose does not add a history entry. Camera world-center coordinates differ from editor viewport pan. |
| Inspect one rendered frame | ui.project_frame_preview displays an exact project-resolution overlay with fit or actual-size presentation. It returns metadata rather than pixels and preserves authored state and playhead. |
| Validate newly authored JSON | template.validate_json version 2 accepts json and optional mode. Request "canonical" for schema and authoring checks; omitted mode uses "import-compatible". Read all verdicts and warnings. |
| Cancel an automated video export | Inspect export.get_status, then use export.cancel with the active operationId. A matching running operation is cancelled; completed, failed, and cancelled history remains unchanged. |
The live schema and availability remain authoritative. This review of the current contract does not establish that your deployed editor or client has every listed capability. SVG export has been withdrawn from the public download UI and automation/WebMCP API; SVG import, vector assets, and drawing remain supported.
Human-controlled steps
WebMCP does not bypass protected browser or account surfaces. You still choose or approve:
- local files;
- the screen, window, or tab used for screen recording;
- microphone permission;
- credentials, OTPs, and reauthentication;
- purchases and billing approval;
- destructive confirmations such as account deletion; and
- browser/native download or share destinations when the platform requires it.
The agent can prepare the correct Scribe workflow, but the browser or operating system owns the protected choice.
Use a compatible client
- Open the Scribe Desktop web editor and the project you want to change.
- Open the page with a client that supports top-level imperative WebMCP tools.
- Inspect the site's available tools in the client before granting consequential work. For a specialized task, ask it to search Scribe capabilities, inspect the matching schema, and execute the capability through the broker.
- Start with a read-only request, such as “Inspect the current project and list locked objects.”
- Ask for a small reversible change and verify it on the canvas.
- Use Scribe Undo if you do not want the change.
For a client that labels WebMCP Site tools, check its current support and workspace policy, then verify discovery in the open editor. Availability depends on client version, rollout, workspace, browser, and model. A browser extension or installed Director skill does not establish live WebMCP support; the client must actually discover and invoke Scribe's registered tools.
If the browser does not implement document.modelContext, Scribe behaves normally and no site tools are registered.
Verify the session's support
Use the client's tool panel and scribe_get_webmcp_status to distinguish early
discovery from the initialized editor catalog. After project continuity is ready,
search capabilities, inspect their exact schemas, and make a small reversible
edit. A tool count by itself does not prove the required action is available.
automation.get_diagnostics can report a build identity when trustworthy build
metadata is present. Retain that identity, the current capability version, and
the project ID when reporting a support issue. After a reload or page replacement,
rediscover tools and verify the same project before continuing.
| Environment | What this guide establishes |
|---|---|
| Desktop web editor in a compatible WebMCP client | Semantic tools can operate on the open project when the client discovers them and Scribe reports availability. |
| Mobile Lite or native mobile app | The product has its own manual workflows; Desktop-only preview, composition, and Director browser acceptance are not established for these surfaces. |
| Assistant with the Director package but no live Site tools | It can draft AI JSON; running the bundled validator needs supported Node and file execution. Apply and inspect the result in Scribe separately. |
| Ordinary browser, CLI, web chat, or cloud agent | Package loading or browser access alone does not establish WebMCP compatibility. Verify actual tools or use the AI JSON/manual import route. |
Security and privacy
Scribe tools are same-origin by default and are not exposed to wildcard origins. Public share and embed routes do not receive editor tools. Project/template text and imported metadata are marked as untrusted content for compatible agents. Tool results exclude cookies, credentials, tokens, private signed upload details, media bytes, and private Zustand or React state.
This page is the public behavior and compatibility contract. Private repository structure and internal implementation modules are not public integration surfaces.
Public Example Projects
Use project.list_examples to inspect the published examples without loading a
package. project.open_example takes a stable exampleId and opens the same
editable project as the editor gallery, after workspace-replacement confirmation.
The compatible project.open_demo defaults to Scribe Animator Basics and honors
a supplied known demoId. Unknown IDs return NOT_FOUND.
A link such as https://app.scribeanimator.com/?example=how-to-start-a-startup
opens the gallery without downloading or replacing the current project.
Verification note
Reviewed on 7 October 2026 against the current Scribe schemas, handlers, and regression tests. Client rollout, fresh package installation, and deployed-build availability require separate observation in the session you use.