Variant MCP

Variant MCP

Variant MCP is the hosted Model Context Protocol server for Variant, an AI-native presentation editor. It lets MCP clients such as Claude Code, Cursor, and Codex create, edit, preview, and export HTML/CSS slide decks through structured tools.

Quick answer: connect an MCP client to https://mcp.variant.art/mcp with HTTP transport. Use OAuth for interactive clients or a scoped bearer token for headless workflows.

#What is Variant MCP?

Variant MCP is a remote MCP server for presentation work. Agents call structured tools instead of guessing how to manipulate slide files. The tools map to real product operations: read a deck, inspect a slide, edit one element, render a preview, upload an asset, read brand context, and export the final deck.

The hosted endpoint is public to connect to, but access is authenticated. Deck content stays tied to your Variant account and credential scopes.

Hosted MCP endpoint
https://mcp.variant.art/mcp

#Why it matters for AI-generated slides

Most AI slide workflows are one-shot generators. They make a first draft, then every small change risks regenerating the slide. Variant uses MCP so the agent can work in a loop: read current state, make a targeted edit, preview the result, and try again.

Because Variant slides are HTML and CSS, the source stays inspectable by agents and editable by humans. That makes later changes cheaper than prompt-only tools or binary slide formats.

#Connect with OAuth

OAuth is the default for desktop and interactive agents. Add the endpoint, restart the client, then sign in when the first Variant tool call asks for authorization.

MCP config
{
  "mcpServers": {
    "variant": {
      "transport": "http",
      "url": "https://mcp.variant.art/mcp"
    }
  }
}

#Use scoped tokens for headless workflows

Bearer tokens are useful for CI, remote sandboxes, or clients that cannot open a browser. Generate a token in Variant with the smallest scope set that fits the job.

Bearer-token config
{
  "mcpServers": {
    "variant": {
      "transport": "http",
      "url": "https://mcp.variant.art/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_VARIANT_MCP_TOKEN"
      }
    }
  }
}

#Core tool groups

Variant MCP exposes deck tools, slide tools, preview tools, asset upload, brand context, comments, version restore, and export. The common edit loop is deck.listSlides, slide.get, slide.edit, then slide.preview.

  • decks.list
  • deck.create
  • deck.listSlides
  • slide.get
  • slide.edit
  • slides.batchUpdate
  • slide.preview
  • brand.context
  • asset.upload
  • deck.export

Variant MCP at a glance

QuestionAnswer
Endpointhttps://mcp.variant.art/mcp
TransportHTTP
AuthOAuth or scoped bearer token
Best clientsClaude Code, Cursor, Codex, and other HTTP MCP clients
Slide formatHTML and CSS
Primary workflowCreate, edit, preview, and export decks through tools

#Common questions

What is Variant MCP?

Variant MCP is the hosted Model Context Protocol server for Variant. It lets MCP clients create, edit, preview, and export HTML/CSS presentation decks through structured tools.

What is the Variant MCP URL?

https://mcp.variant.art/mcp. Use HTTP transport.

Is Variant MCP a local server?

No. Variant MCP is hosted by Variant. It is a remote HTTP MCP server, not a local stdio process.

Can agents edit existing decks?

Yes. With write access, agents can read an existing deck, apply targeted slide edits, preview the result, and export the deck.

Is the Variant MCP implementation public?

No. The public GitHub repo documents setup and examples. The hosted server implementation remains internal to Variant.