Deckary MCP server

Give your AI agent a real presentation workspace

Connect an MCP-compatible AI agent to Deckary to list, inspect, render, and edit your browser presentations through an authenticated, typed presentation interface.

One authenticated interface. Four presentation tools.

The agent owns the request and creative judgment. Deckary owns identity, artifact structure, validation, pixels, and safe persistence.

list_decks

List the authenticated user's browser presentations and current revisions.

read_deck

Read the editable presentation structure and the exact state needed for a safe next action.

render_slides

Render exact 960×540 PNGs for up to four current slides so the agent can inspect the result.

author_deck

Create, revise, reorder, or remove presentation content through one validated authoring contract.

Connect an MCP-compatible agent

Your agent must support remote MCP servers and OAuth. Deckary will ask you to sign in and approve presentation access.

  1. 01

    Create or open a browser presentation

    Use Deckary's web presentation builder so the agent has an artifact to inspect and change.

  2. 02

    Add the remote MCP server

    Enter https://deckary.com/mcp in your agent's MCP connection settings.

  3. 03

    Authorize Deckary

    Sign in when your agent asks and approve the delegated decks:edit permission.

  4. 04

    Describe the presentation outcome

    Ask the agent to list your decks, read the target, render slides when visual context matters, and author the requested change.

Connection prompt

Connect to Deckary at https://deckary.com/mcp so you can list, read, render, and edit my presentations. Ask me to sign in when needed.

Deckary limits each agent to your presentations

OAuth scopes account access. Deckary's authoring contract validates each presentation change before saving it.

OAuth access is scoped to the signed-in user's presentations.

Every authored change passes the canonical Deckary presentation validator.

Revision checks reject stale writes instead of overwriting newer work.

Exact slide renders let the external agent inspect the committed pixels.

MCP changes browser presentations, not a live Office document.

The external agent uses its own model; the MCP server does not invoke Deckary AI.

MCP presentation questions

What can an external AI agent do through Deckary's MCP server?

After you authorize it, an MCP-compatible agent can list your Deckary web presentations, inspect their editable structure, render exact slide images, and create or revise slides through Deckary's typed authoring contract.

Can the MCP server edit a PowerPoint file that is open on my computer?

No. The MCP server works with your Deckary browser presentations. Use the Deckary PowerPoint add-in when an agent must inspect and change a presentation open in PowerPoint.

Does Deckary choose the model used by my external agent?

No. Your external agent owns its model, reasoning, and intent. Deckary supplies authenticated presentation tools, validates the authored changes, saves the canonical deck, and returns exact artifact state and slide renders.

How is access protected?

The remote MCP endpoint uses OAuth. Access is scoped to the signed-in Deckary user and the delegated presentation-editing permission. Revision checks reject stale agent requests before they overwrite newer work.

Create the presentation once. Let your agent keep working on it.