Skip to content
MagicSlides logo

MagicSlides MCP server

Create PowerPoint presentations from topics, summaries, or YouTube videos using AI.

MagicSlides is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
3
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the MagicSlides MCP server

Connect MagicSlides once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches MagicSlides and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

MagicSlides tools your AI can run

Once connected, your assistant can call any of these MagicSlides actions by asking in plain language.

  • Create PPT from Topic

    Generates a PPT presentation from a given topic.

    13 fields

  • Create PPT from Text/Summary

    Generates a PPT presentation from provided text or summary.

    11 fields

  • Create PPT from YouTube Video

    Generates a PPT presentation from a YouTube video link.

    11 fields

Give your assistant MagicSlides

Connect MagicSlides once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

MagicSlides MCP, answered.

No. That is the point of it. One Activepieces server exposes MagicSlides alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect MagicSlides in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 3 tools, including Create PPT from Topic, Create PPT from Text/Summary, Create PPT from YouTube Video, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.