Deckary PowerPoint MCP documentation
Connect an external AI agent to saved Deckary presentations or a live PowerPoint deck through Deckary's remote MCP server.
Last verified: 2026-09-04
Deckary is a remote PowerPoint MCP server that lets an MCP-compatible AI agent inspect, render, and edit presentations. The agent can work with saved decks in Deckary's Web Builder or with a PowerPoint presentation that you explicitly share from the Deckary add-in. Your external agent owns the reasoning; Deckary supplies deterministic presentation tools and validates writes.
MCP endpoint#
Use this Streamable HTTP endpoint:
https://deckary.com/mcp
Authentication uses OAuth. Your MCP client should open a sign-in and consent flow rather than asking you to paste a Deckary password or long-lived API key.
For the protocol details behind this connection, see the official MCP Streamable HTTP transport specification and MCP authorization specification.
Choose the presentation surface#
| Surface | Use it when | What the agent can access |
|---|---|---|
| Live PowerPoint | The presentation is open in desktop PowerPoint | Only presentations explicitly shared from the Deckary add-in while the live session remains connected |
| Saved Web Builder deck | The presentation is stored in your Deckary account | Owner-scoped saved decks that your OAuth permission allows the client to access |
Both surfaces support reading current presentation state, rendering slide images, and authoring changes. They use different identifiers and concurrency checks, so an agent should not mix a saved deck revision with a live PowerPoint artifact version.
Read Work with live PowerPoint or Work with saved Web Builder decks for the exact flow.
How Deckary MCP works#
- Add
https://deckary.com/mcpas a remote MCP server in a compatible client. - Sign in to Deckary and approve the requested presentation permissions.
- Let the agent discover a saved deck or an explicitly shared live PowerPoint session.
- The agent reads only the slides and objects needed for the task.
- Deckary checks the current revision or artifact version before applying a write.
- The tool returns fresh presentation state and, for authoring, visual evidence of the committed result.
Deckary's MCP server does not call a second model. The model, conversation history, source files, and planning remain in the AI client you chose. This separation makes Deckary a presentation execution layer rather than another chat interface.
What the MCP server exposes#
The server currently exposes five tools for saved Web Builder decks and five tools for live PowerPoint. The tools cover deck discovery, semantic reads, exact slide renders, detailed object inspection where needed, and validated authoring.
See the MCP tool reference for all ten tool names and their mutation behavior. The tool definitions returned by your connected MCP client remain authoritative for the exact input schema.
Start here#
- Follow Getting started to connect a compatible remote MCP client.
- Use Live PowerPoint when an open PPTX must remain native and editable in Office.
- Use Web Builder decks when the presentation lives in Deckary's browser workspace.
- Review Security and data handling before authorizing a client.
- Use Troubleshooting for authentication, session, version, and settlement errors.
For product positioning, supported workflows, and common questions, see the Deckary MCP integration overview.