Deckcast MCP

Privacy and data handling

Deckcast processes only files and tool inputs you explicitly provide to create podcast summaries. The MCP server does not read your full chat history.

Data collected

Deckcast stores your account identity, OAuth connection metadata, uploaded source files, extracted slide/page text, generated summaries, generated podcast scripts, audio files, job status, billing/usage events, and operational logs.

Processing providers

Deckcast may send extracted content and rendered slide/page images to configured AI providers for extraction, summarization, scripting, and text-to-speech. Provider-specific API keys are held server-side and are never shared with MCP clients.

Retention and deletion

Uploaded files and generated MCP deck artifacts remain available under DeckCast retention policy. Ephemeral export artifacts (HTML, PDF, PPTX) are kept for up to seven days from creation, or about twenty-four hours after an agent confirms the file was saved locally. Capability download links are unauthenticated bearer URLs—treat them as secrets. You can revoke links for a build via MCP tools when available. Temporary upload sessions expire automatically. Short-lived storage redirects used after link validation typically expire within about one minute.

Revocation

You can disconnect Deckcast in Claude or ChatGPT at any time. OAuth grants can also be revoked through Deckcast account controls as they become available.