Blog

Claude Code | 7 min read | 2026-08-27 | By Variant Team

Google Slides with Claude Code: Two practical workflows

Use Google Slides with Claude Code through a Slides MCP server or an HTML-first workflow, with setup steps, prompts, tradeoffs, and export guidance.

Author: Variant Team. Variant is built by a small team working on HTML-native presentation tools, MCP workflows, and agent-editable decks.

You can use Google Slides with Claude Code, but the best workflow depends on where the deck needs to live while you make it.

If an existing deck must stay in Google Drive, connect Claude Code to a Google Slides MCP server and edit it in place. If Claude Code will draft the presentation, let it work in HTML and CSS, preview its work, then hand the finished deck to Google Slides.

#Quick answer

There are two workable ways to use Google Slides with Claude Code. Connect Claude Code to a Google Slides MCP server when a deck must remain live in Drive, or build the deck as HTML through Variant's MCP tools and export PPTX for import into Google Slides. The HTML-first path is usually better for drafting because Claude Code can write code and verify rendered previews, while the direct Google Slides path is better for weekly edits, comments, and organization permissions.

#Choose the path before you prompt

Choose direct Google Slides MCP when the file in Drive is the source of truth. Choose HTML first when Claude Code is the primary author and needs fast visual iteration. Google Slides is very good at browser-based collaboration, comments, familiar editing, and organization permissions. HTML gives a coding agent a source format it can revise directly.

For a deeper look at the integration model, read what a Google Slides MCP server gives an agent. The sections below focus on the daily workflow.

#Path A: Edit Google Slides through MCP

A Google Slides MCP server exposes presentation actions to Claude Code. Server URLs and tool names vary, so check the chosen server's documentation. The Claude Code command has this shape:

claude mcp add --transport http <name> <url>

If the server uses Google Cloud credentials, complete that setup first. Our Google Slides MCP server setup guide covers that job. Then verify the connection:

claude mcp get <name>

Then start with a constrained prompt. Do not ask for a complete redesign and ten content changes in one turn.

Open the quarterly planning presentation. Read the slide titles and summarize
the current structure before editing anything. Then update only the agenda slide
to match that structure. Preserve the existing theme and speaker notes.

This prompt requires inspection before editing and limits the test to one slide.

#What usually goes wrong

The common problem is not text generation. It is visual drift.

A model may compose Google Slides batchUpdate requests that reposition shapes and text boxes. The API can accept them even when the result looks awkward. Without a rendered preview, Claude Code cannot reliably see the changed slide.

After a few edits, mistakes accumulate. Text overflows, objects stop aligning, or a title wraps. The model may change coordinates again without a trustworthy visual reference.

Keep edits narrow. Change one or two slides, then stop for review. Request a preview after each change when the server supports it. Otherwise, inspect the deck yourself between batches.

#Path B: Draft in HTML, then import

The second workflow treats Google Slides as the destination. Claude Code builds HTML and CSS slides in Variant, checks previews, fixes weak slides, and exports a PPTX.

Connect Claude Code to Variant's hosted MCP endpoint:

claude mcp add --transport http variant https://mcp.variant.art/mcp
claude mcp get variant

The first MCP request opens a browser for OAuth. Then give Claude Code a clear audience, purpose, length, and review loop:

Create a 9-slide deck for engineering managers deciding whether to adopt an
internal developer portal. Start with an outline and wait for my approval.
After approval, create the deck in Variant using HTML slides. Keep each slide
to one claim. Use a restrained blue and warm-gray palette. Preview every slide,
then revise any slide with clipped text, weak contrast, or crowded content.

Claude Code can use deck.create to start the deck. Slides use HTML for structure and CSS for layout. The useful part is the review loop: slide.preview returns a rendered view, so the model can inspect its output.

When two slides are wrong, ask Claude Code to call slide.get, make a targeted change with slide.edit, and preview again. Our guide to making a slide deck with Claude Code covers this loop.

When ready, use deck.export to request PPTX. In Google Slides, use File, Import slides. People who never use Variant or Claude Code can then edit the result.

#Direct Google Slides MCP vs HTML first

Direct Google Slides MCP is an integration workflow. HTML first is an authoring workflow. For the broader distinction, see MCP vs API for AI agents.

#Be honest about the round trip

HTML to PPTX is a handoff, not a sync. Changes made later in Google Slides do not flow back into the HTML deck, and changes made later in Variant do not update the imported Google Slides file.

Conversion has limits. Unavailable fonts may be substituted. Exotic CSS may change. Complex browser layouts do not always map neatly to presentation objects. Do not expect pixel-perfect PPTX export.

Review font substitution, line breaks, charts, overlapping objects, and slides with unusual CSS after import. Keep HTML as the working source only if the team accepts the same handoff for future releases.

If the deck must stay live in Drive and receive edits every week, use direct Google Slides MCP despite the extra friction. Google Slides wins when collaboration history, comments, permissions, and continuous in-place editing matter more than agent-native authoring.

#Prompts that produce better slide work

The prompt should control the work sequence, not only describe the topic.

#Ask for the outline before the deck

Propose an 8-slide narrative for a sales kickoff. For each slide, give the title,
single claim, and evidence needed. Do not create the deck until I approve the outline.

This separates argument design from layout, so you can fix a weak story first.

#Require a preview after each slide

Create one slide at a time. After each slide, render a preview and inspect it for
overflow, low contrast, awkward wrapping, and inconsistent spacing. Fix those
issues before moving to the next slide.

This makes visual review part of the task. It works best where slide.preview is available.

#Protect a shared Google Slides deck

Read the existing deck first. Change only slides 4 and 7. Preserve the theme,
speaker notes, comments, and all other slides. Summarize each proposed change
before applying it, then stop after those two slides.

This limits scope and gives the reviewer a clear boundary.

#Fix selected slides without restarting

Slide 3 has too much text and slide 6 lacks a clear conclusion. Read only those
slides, revise each around one claim, preview both, and leave every other slide
unchanged.

Targeted prompts preserve approved work.

#A simple decision list

Use direct Google Slides MCP when:

• The presentation already lives in Google Drive.
• Your team reviews through Google Slides comments.
• Organization permissions must apply during the whole process.
• Claude Code is making bounded updates rather than inventing the visual system.

Use Variant and export to Google Slides when:

• Claude Code is drafting most of the presentation.
• You want HTML and CSS as the working format.
• The agent needs to preview and correct its visual output.
• Google Slides is the final collaboration or delivery format, not the live source during drafting.

You can inspect the full set of Variant MCP tools before choosing the second path.

#Related reading

• Connect Claude Code to an MCP presentation editor
• Google Slides MCP server setup
• Claude Code MCP documentation

#FAQ

#Can Claude Code edit Google Slides directly?

Claude Code can edit Google Slides when it is connected to an MCP server that exposes Google Slides operations. The result depends on that server's tools, Google credentials, and whether Claude Code can inspect a rendered preview after making changes.

#What is a Google Slides Claude MCP workflow?

A Google Slides Claude MCP workflow connects Claude Code to a server that translates MCP tool calls into Google Slides actions. It is a good fit for editing a presentation that must remain in Google Drive.

#Is Variant a Google Slides MCP server?

No. Variant is an HTML-native presentation editor with MCP tools. Claude Code can build and preview a deck in Variant, then export PPTX for import into Google Slides.

#Can I import a Variant deck into Google Slides?

Yes. Export the Variant deck as PPTX, then use File, Import slides in Google Slides. Review the imported deck for font substitutions, line wrapping, and layouts that relied on unusual CSS.

#Does the Google Slides file stay synced with Variant?

No. PPTX export and Google Slides import create a handoff, not a live sync. Later edits in either tool do not automatically update the other copy.

#Which workflow is best for a deck that changes every week?

Direct Google Slides MCP is usually best for a deck that stays live in Drive and changes every week. It preserves the team's Google Slides comments, permissions, and editing habits despite a more constrained agent workflow.

#Which workflow gives Claude Code better layout feedback?

An HTML-first Variant workflow gives Claude Code a direct preview loop through slide.preview. A Google Slides MCP workflow can provide comparable feedback only when its server returns useful rendered previews.

#The short version

Use direct Google Slides MCP to maintain a shared Drive deck. Use Variant when Claude Code is creating the first draft and needs HTML, CSS, and rendered previews to produce stronger slide layouts. Importing PPTX into Google Slides is a practical handoff, but it is not a sync and it needs a review pass. If continuous Google collaboration is the main requirement, Variant is the wrong choice for the working file.