MagicSlides MCP server for AI agents

Live

API KEY

PRESENTATIONS

AI

MagicSlides gives your agent AI presentations: generate decks from a topic, pasted text, or a web page, build designed Studio decks, fill template slots with your own copy, and get editor, PPTX, and PDF links.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
MagicSlides
agent · Acme Q3
Run
Make a deck from our latest blog post on agent auth.
S
magicslides_generate_presentation_from_url
124ms
Presentation agent
A 12-slide deck is ready in the MagicSlides editor, where you can edit it and download it as PPTX or PDF.
Sources: 1 web page
magicslides
12 slides
18:29
Message Claude...

Tools your presentation agent reaches for on MagicSlides, scoped per user.

CALL ANY TOOL
9 tools for presentations in MagicSlides: generate decks from a topic, text, or URL, generate designed template and Studio decks, render Studio decks from your own slot copy, and list templates.
magicslides_create_studio_presentation_from_slots
Create studio presentation from slots
Render a designed MagicSlides Studio deck from slide copy you wrote for a template's slots. MagicSlides writes none of the text. Returns status, previewImageUrl (PNG of the first slide), previewUrl (live slideshow), shareUrl, editUrl (opens in MagicSlides Studio), pdfUrl, slideCount, templateKey and conversationId. Free. Use magicslides_create_studio_presentation_from_slots when you have written the content. Use magicslides_generate_studio_presentation to have MagicSlides write it. Call magicslides_get_studio_template_schema first for the same template_key to get the layoutKey and slot keys of each slide.
Parameters
Name
Type
Required
Description
slides
array
Required
The deck's slides, 3 to 20, in order. Each slide gives the layoutKey from the schema and a slots object that maps every slot key from the schema to your text. Image slots ending in _URL take an image link; slots ending in _QUERY take a search phrase. Example: [{"layoutKey": "cover", "slots": {"TITLE": "Q3 Product Update", "SUBTITLE": "What shipped and what is next"}}].
template_key
string
Required
The same slotsReady Studio template key you got the schema for from magicslides_get_studio_template_schema. Example: editorial-pitch.
include_images
string
Optional
How to fill image slots that you gave a search phrase (_QUERY) but no image link (_URL) for: stock for stock photos, ai for AI-generated images, none for no image. MagicSlides uses stock when omitted. One of: `stock`, `none`, `ai`.
language
string
Optional
Language of the slide text as an ISO 639-1 code. Example: en, es, fr, de, ja. Defaults to en when omitted.
title
string
Optional
Title of the deck. Example: Q3 Product Update.
magicslides_generate_presentation
Generate presentation
magicslides_generate_presentation_from_url
Generate presentation from url
magicslides_generate_studio_presentation
Generate studio presentation
magicslides_generate_template_presentation
Generate template presentation
magicslides_get_current_user
Get current user
magicslides_get_studio_template_schema
Get studio template schema
magicslides_list_studio_templates
List studio templates
magicslides_list_templates
List templates
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// MagicSlides tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["magicslides"], toolNames: [
    "magicslides_list_templates",
    "magicslides_generate_template_presentation",
    "magicslides_generate_presentation_from_url"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Turn our latest blog post into a deck with PPTX and PDF links" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["magicslides"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Turn our latest blog post into a deck with PPTX and PDF links" }],
  tools,
});

// Execute the tool call with the user's vaulted MagicSlides API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["magicslides"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Turn our latest blog post into a deck with PPTX and PDF links" }],
  tools,
});

// Tool call runs with the user's vaulted MagicSlides API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["magicslides"] }, pageSize: 100,
});

const agent = new Agent({
  name: "presentation_agent",
  model: "gemini-2.5-pro",
  instruction: "MagicSlides tools scoped to this user",
  tools,
});

await agent.run("Turn our latest blog post into a deck with PPTX and PDF links");
Try these prompts
Copy any prompt into your agent. Each maps directly to a MagicSlides tool. Click to copy, paste into your agent, done.
Generate decks
Copy the prompt
Copied
Make a deck on Q3 product updates from these notes.
Copy the prompt
Copied
Turn this blog post URL into a presentation.
Copy the prompt
Copied
Create a deck about our onboarding program in a designed template with a PPTX link.
Studio decks
Copy the prompt
Copied
List the Studio templates that are ready for my own copy.
Copy the prompt
Copied
Show the slide plan and text slots for the creative-design template.
Copy the prompt
Copied
Render a Studio deck from the copy I wrote for each slot.
Templates and account
Copy the prompt
Copied
Which MagicSlides plan is our account on?
Copy the prompt
Copied
List the templates available for template presentations.
Copy the prompt
Copied
Generate a Studio deck on remote work best practices.
SEE HOW AUTH WORKS
Each user connects their own MagicSlides API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
MagicSlides
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
MagicSlides
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
MagicSlides
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
MagicSlides
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other AI and productivity connectors.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Support and Ops Teams
Meeting prep
Pulls agenda, participant context, and open action items before every meeting.
Test other agents
See the same per-user auth pattern across other AI and productivity connectors.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
OPS
Meeting prep agent
Assemble the agenda, HubSpot attendee history, and open action items from Gmail before every meeting on the calendar.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared MagicSlides API key looks fine in a demo. In production every deck generation looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
MagicSlides today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access MagicSlides as the user or through a shared API key?
As the user. Each user connects their own MagicSlides API key once, and Scalekit sends it with every call. Audit logs attribute every deck generation to that user, not a shared service account.
Where is the MagicSlides API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in MagicSlides?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example the free template and schema tools plus magicslides_create_studio_presentation_from_slots, without the generate tools that use MagicSlides credits. No MagicSlides tool deletes a deck. Scalekit also enforces scope checks before every API call.
What happens when a user revokes MagicSlides access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which tools use MagicSlides credits?
The generate tools, such as magicslides_generate_presentation and magicslides_generate_studio_presentation, use credits and take up to about a minute. Listing templates, reading a template schema, and rendering a Studio deck from your own slot copy are free.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""magicslides"": {
""url"": ""https://mcp.scalekit.com/magicslides"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.magicslides]
url = ""https://mcp.scalekit.com/magicslides""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""magicslides"": {
""url"": ""https://mcp.scalekit.com/magicslides"",
""type"": ""http""
}
}
}