Troubleshoot Deckary MCP

Most Deckary MCP problems come from an incomplete OAuth flow, missing permission, inactive PowerPoint sharing session, or presentation state that changed after the agent read it. Start by identifying whether the task targets a saved Web Builder deck or a live PowerPoint presentation; each surface has different identifiers and recovery steps.

Sign-in keeps repeating#

Remove the Deckary connection from the AI client, add https://deckary.com/mcp again, and complete OAuth with the intended Deckary account. Finish the browser consent flow before returning to the client.

Do not paste your Deckary password into the conversation or configure it as an MCP credential.

Expected tools are missing#

The decks:edit permission exposes saved-deck tools. Live PowerPoint tools require the separate live-powerpoint:edit permission. Reconnect and approve the permission needed for the workflow.

If all tools are absent, confirm that the client supports remote Streamable HTTP servers and OAuth. A client limited to local standard-input MCP servers cannot connect directly to Deckary's remote endpoint.

No saved decks appear#

Confirm that the Web Builder presentation is saved under the same Deckary account used for OAuth. Remove any overly narrow list query, then call list_decks again. Do not substitute a live PowerPoint session ID for a saved deckId.

No live presentations appear#

In desktop PowerPoint:

1. Open the intended PPTX.
2. Open the Deckary task pane.
3. Sign in with the same Deckary account used by the MCP client.
4. Turn on MCP sharing.
5. Keep the task pane open and connected.

Then call list_live_presentations again. Deckary does not list closed files or presentations that have not been explicitly shared.

A live presentation disappeared#

The session ends when sharing is turned off, the user signs out, the task pane closes, or the connection disappears. Reopen the pane, enable sharing, list live presentations again, and use the new session ID, connection generation, and artifact version.

Do not reuse handles from the previous session.

Version conflict#

A version_conflict means the live presentation changed after the version supplied by the agent. The rejected write made zero mutation.

Read the current live presentation, reacquire any required slide or shape handles, update the proposed edit for the new state, and submit it once with the current artifact version. For a saved Web Builder deck, read the current deck revision and rebuild the authoring program against that revision.

Settlement unknown#

Do not automatically repeat author_slide after settlement_unknown. The command may have reached Office even though the final result was not confirmed.

Reconnect if needed, read the current presentation, and check whether the intended change is already present. Only prepare another write after current truth is known.

Validation issues#

Complete preflight validationIssues mean no Office mutation occurred. Follow the returned issues and repair the semantic program. Common causes include a missing placeholder action on slide creation, stale or invalid handles, an unsupported color token, or a malformed table or chart edit.

For live slide creation, use an exact current layoutId and satisfy every editable placeholder exposed by that layout. For patches, use current slide and shape handles.

An object or table is incomplete#

Use inspect_live_objects only for the current handles that need deeper detail. If a table response reports rangeRequired, request a bounded zero-based rectangular tableRange. Older PowerPoint hosts may preserve exact table text while reporting some formatting details as unavailable.

Slide rendering fails#

Refresh presentation truth first. Saved rendering requires current slide IDs; live rendering requires a current session, generation, artifact version, and slide handles. Request no more than four slides, and use visualDetail=atlas only for one live slide.

If the connection itself is healthy but the issue persists, use the contact page and include the tool name, bounded error code, approximate time, and whether the target was saved or live. Do not send confidential slide content unless support explicitly requests an approved sample.