By the end of this guide, Claude will be able to create, read, update and delete presentations in your SlideWeave account. You connect it once with OAuth, in your browser, so no API key goes into Claude. The guide covers the two clients we have tested end to end, claude.ai and Claude Code, and it explains one behavior that surprises people the first time: a deck Claude creates is private until you share it.
SlideWeave’s MCP server is in public beta. Claude is not the only client it works with, and our compatibility table lists the status of each one.
What you need
- A SlideWeave account.
- Claude in the browser (claude.ai) or Claude Code in a terminal.
- Nothing else to install. The server lives at
https://api.slideweave.com/mcp, and you paste that URL exactly as written, with no trailing slash. The authorization step compares the URL you gave Claude with the one the server expects, so a different path or a slash at the end makes the connection fail.
Connect from claude.ai
In Claude, open Customize > Connectors, choose Add and then Add custom connector. Enter a name, paste the URL above and add the connector. A SlideWeave window opens in your browser. Sign in, read the permissions it asks for (read and write presentations) and approve.
Two details come from Anthropic’s help page, which we checked on October 31, 2026. Custom connectors are available on Free, Pro, Max, Team and Enterprise plans, and the Free plan allows one. On Team and Enterprise, an organization owner adds the connector under Organization settings > Connectors, and then each member connects with their own account. Anthropic also warns that custom connectors reach services it has not verified, so connect only to servers you trust. Menu names change over time, so if yours differ, look for the custom connector option in Claude’s connector settings.
Connect from Claude Code
Two commands are enough:
claude mcp add –transport http slideweave https://api.slideweave.com/mcp claude mcp login slideweave
The first registers the server, and Claude Code then shows it as needing authentication. The second opens SlideWeave in your browser, where you sign in and approve. Inside a Claude Code session you can run /mcp instead of the second command.
Ask Claude for a deck
Start with a request that names the audience and the decision, in the same way you would brief a person:
Use SlideWeave to create a four-slide presentation for our operations committee. The decision is whether to move the two smallest warehouses onto one carrier contract. Include a bar chart comparing last quarter’s shipping cost per order for each warehouse, using these numbers: …
Behind that request Claude uses a small set of tools. It calls get_slidelang_guide to learn how to write valid presentation source, writes the deck in the open ZiraDocs format, and calls create_presentation. SlideWeave validates the source before it stores anything, so a syntax mistake comes back as an error that Claude can fix and resubmit. If your client asks you to approve write calls, approve them after reading which deck the call touches.
Expect a little trial and error in how the model fills in tool arguments. In our tests Claude occasionally guessed a parameter name wrong, received an error and corrected itself on the next call, without any help from us.
Why the link does not open for other people
create_presentation publishes version 1.0, and the deck is private. The viewer link Claude returns opens only for you, signed in to SlideWeave. If you paste it into a message to a colleague, they will see a not-found page. None of the MCP tools makes a presentation public. To share the deck, turn on the public link in SlideWeave itself. Here “published” means the deck has a published version, which is different from a public link.
Edit it without overwriting your own changes
Ask Claude to refine the deck, for example to add speaker notes to every slide. Claude reads the presentation first with get_presentation, which returns the source and a current checksum, and then calls update_presentation with that checksum. If you edited the deck in SlideWeave in the meantime, the checksum is stale and the update returns CONFLICT. Claude should read the deck again, reapply its edit to the latest source and retry once. Do not let it resend the stale request in a loop.
One consequence of reading the deck back is worth knowing. The source that comes back is in its canonical form, so it can differ from the text Claude wrote, for instance by carrying extra attributes. That is expected, and it is the version your next update should start from.
Clean up and disconnect
Ask Claude to move the test deck to the trash. Deletion is recoverable, but Claude should name the exact deck and ask you first. To remove the connection, open Connected apps in SlideWeave and disconnect Claude. SlideWeave revokes its tokens, and the next request has to be authorized again.
If something fails
If Claude says it could not reach the MCP server or that authorization failed, check the URL first, then remove the connector and add it again. The troubleshooting page covers that case, CONFLICT and the other common errors.
Sources: Anthropic, Get started with custom connectors using remote MCP and Connect Claude Code to tools via MCP, both accessed October 31, 2026.