Give AI agents a safe presentation workspace
Presentation generation is only the first step. An agent also needs a stable artifact to inspect, a controlled way to write changes, and a human review surface. TweakSlides exposes that finish layer through MCP and its agent API.
Create a reviewed session
Start with a proposal link so the user can inspect the deck before granting direct edit access.
Connect the MCP client
Use the app-provided session ID and bearer secret for a trusted session.
Patch with version checks
Read the current deck, submit structured operations with a base version, validate, and render before export.
get_active_deck → patch_deck(baseVersion, operations) → validate_deck → render_slide_preview
A version-checked change that can be inspected in the browser and reverted through deck history.
Semantic tools, not DOM automation
The MCP surface works with deck meaning: Markdown, outline, slide operations, themes, validation, previews, and exports. An agent does not need to click through the visual editor or infer state from pixels.
Optimistic version checks prevent a stale agent from silently overwriting a newer browser edit. Linear snapshots make accepted changes reversible.
Current local-first model
The open browser tab owns the active deck, while the server relays proposals and commands. This keeps the first workflow lightweight, but it also means the current tab or server session must remain available for trusted direct edits.
- Tokenless proposals for first contact
- Bearer-protected direct edits for trusted sessions
- Structured slide insert, update, delete, and move operations
- Validation, preview rendering, and export tools
Security boundary
A direct-edit secret grants access to the current session and should be treated like any other bearer token. Do not paste it into public issues, logs, or shared prompts. Prefer the proposal flow whenever an agent has not yet been trusted.
What it does not do yet
- The current primary workflow is local-first rather than a durable team workspace.
- Direct edits require session credentials and an active bridge.
- The agent must handle version conflicts by rereading the deck.
Questions, answered plainly
Is the MCP endpoint public and unauthenticated?
No. Direct edit tools require trusted session credentials. Tokenless access is limited to review proposals.
Does the agent edit the browser DOM?
No. It works through semantic deck operations, Markdown, validation, rendering, and export APIs.
What happens when two edits conflict?
The base-version check rejects stale operations so the agent can reread the current deck and prepare a new patch.