Presentations.AI

Presentations.AI MCP Server

Official Model Context Protocol server for Presentations.AI. Create designed slide decks from a topic or your notes, apply your brand, then share or download them, from any MCP client.

Endpoint

https://api.presentations.ai/mcp

A Presentations.AI account is required. Most clients open a browser to sign in the first time they connect. Clients without OAuth support can send an API key instead:

Authorization: Bearer pai_live_...

Create a key at api.presentations.ai.

Tools

Source material goes in inline as text. File upload, admin, and usage operations are REST-only; see the API docs.

Clients that support the MCP Skills extension also get two skills, create-presentation and manage-presentations.

Full reference: docs.presentations.ai/docs/agents.

Example prompts

Make a 10-slide deck on our product roadmap for the leadership team.

Turn these meeting notes into a short deck: Show me an outline first, then build the deck with the Presentations.AI brand kit. Find my onboarding deck and give me a fresh download link. Share my "Q3 results" deck with teammate@example.com as a viewer.

Connect from your MCP client

• Claude (claude.ai and Claude Desktop): docs/clients/claude-desktop.md
• Claude Code: docs/clients/claude-code.md
• ChatGPT: docs/clients/chatgpt.md
• Cursor: docs/clients/cursor.md
• VS Code: docs/clients/vs-code.md
• Visual Studio: docs/clients/visual-studio.md
• Kiro: docs/clients/kiro.md
• Cline: docs/clients/cline.md
• Gemini CLI: docs/clients/gemini-cli.md

Stdio wrapper

For clients that only run local servers, src/index.js forwards stdio to the hosted endpoint with an API key. It needs Node.js 22 or later:

git clone https://github.com/slidecraft-in/presentations-ai-mcp-server

cd presentations-ai-mcp-server && npm ci

{

"mcpServers": { "presentations-ai": { "command": "node", "args": ["/path/to/presentations-ai-mcp-server/src/index.js"], "env": { "PRESENTATIONSAI_API_KEY": "pai_live_..." } } } }

The client's config file then holds the key, so keep it private.

Or with Docker: docker build -t presentations-ai-mcp ., then docker run -i --rm --init -e PRESENTATIONSAI_API_KEY presentations-ai-mcp, which passes the key from your environment.

Without a key, the wrapper lists the tools from src/snapshot.json and tool calls return an error asking for one. To refresh the snapshot from the live server, set PRESENTATIONSAI_API_KEY in your environment and run npm run snapshot. Set PRESENTATIONSAI_MCP_URL to read a different https endpoint.

Data and security

• The server acts as the signed-in account, or the owner of the API key, within that account's permissions and the scopes the sign-in or key grants. Tools a connection isn't allowed to use are hidden.
• Seven tools only read. The other six change or share work and carry MCP's destructiveHint annotation, so clients can ask before running them: create_presentation and create_outline spend credits, share_deck creates a public link, patch_deck can change who can open a deck, create_grant shares a deck by email, and delete_deck moves a deck to trash.
• Download links from get_export and get_deck work without signing in and expire after 15 minutes, so share them only with people who should have the file.
• Treat an API key like a password: keep it out of chats, code, and shared config files. If a key is exposed, revoke it in the API keys dashboard or with DELETE /api-keys/current, then create a new one.

See the privacy policy and terms of service.

Troubleshooting

Related repos

• presentations-ai-skills: the create-presentation and manage-presentations Agent Skills
• presentations-ai-gemini-extension: Gemini CLI extension with this server and both skills

Support

Email support@presentations.ai with the client you use, the tool that failed, when it happened, and the error message. Never include an API key or an Authorization header.

More help: docs.presentations.ai/docs/support.

License

MIT, see LICENSE.