Deckary PowerPoint MCP documentation
Connect an external AI agent to saved Deckary presentations or live PowerPoint, Excel, and Word documents through Deckary's remote MCP server.
Last verified: 2026-10-06
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, Excel workbook, or Word document that you explicitly share from the Deckary add-in. Your external agent owns the reasoning; Deckary supplies deterministic 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, Excel, Word | The file is open in Office with the Deckary task pane | Only documents 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 state, rendering images, and authoring changes. They use different identifiers and concurrency checks, so an agent should not mix a saved deck revision with a live artifact version. The three live hosts share one set of tools and one safety model.
Read Work with live PowerPoint, live Excel, live Word, 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 document.
- The agent reads only the slides, cells, or sections 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 exposes six tools for saved Web Builder decks, five live document tools that work the same way for PowerPoint, Excel, and Word, and two shared tools for the authoring vocabulary and account skills. The tools cover discovery, semantic reads, exact Office renders, detailed object inspection where needed, the complete authoring vocabulary, and validated authoring.
See the MCP tool reference for every tool name and its 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, Live Excel, or Live Word when an open Office file must remain native and editable.
- Use Web Builder decks when the presentation lives in Deckary's browser workspace.
- Use Embed in your product when your own agent builds decks for your users and they edit them in an embedded Deckary editor.
- 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.