Authentication and scopes
SlideWeave MCP uses OAuth for user authorization. A compatible client discovers the authorization endpoints, opens a browser, and receives tokens only after you approve the request.
Available scopes
Section titled “Available scopes”| Scope | Grants |
|---|---|
presentations:read |
List presentations and read their editable source and metadata. |
presentations:write |
Create, update, and move presentations to trash. |
Write access does not implicitly replace read access. Most editing workflows request both because a safe update starts by reading the latest source and checksum.
Recommended permission model
Section titled “Recommended permission model”- Use
presentations:readfor cataloging, analysis, and review. - Add
presentations:writeonly when the client must create or modify decks. - Configure the client to ask for approval before write tools.
- Review connected clients periodically and disconnect anything you no longer use.
Token handling
Section titled “Token handling”Do not copy access or refresh tokens into prompts, chat messages, logs, or source control. The MCP client should store and refresh them using its own credential mechanism.
Revoking access
Section titled “Revoking access”Disconnect the integration from Connected apps in SlideWeave. Active authorizations for that account and client are revoked together, so an old parallel grant cannot keep the client connected.