Google Slides

@Google Slides create a new presentation called 'Q1 Product Roadmap' and show me the first slide thumbnail

I've created a new presentation titled 'Q1 Product Roadmap' with a blank title slide. The presentation ID is 1a2b3c4d5e6f7g8h9i0j. Here's a thumbnail preview of the first slide: [thumbnail URL]. The slide currently contains placeholder text boxes for a title and subtitle. You can now add content using markdown or direct API updates.

This example shows the basic create-and-preview workflow. The MCP returns a presentation ID that you'll need for all subsequent operations on this deck. OAuth scope 'presentations' is required. The thumbnail generation may take a few seconds on first request.

@Google Slides update presentation 1a2b3c4d5e6f with markdown content: slide 1 has title 'Roadmap Overview' and bullets for 'Launch mobile app', 'Expand API', 'New pricing tier' --- slide 2 has title 'Timeline' and text 'Q1: Design phase'

I've updated the presentation with two slides. Slide 1 now displays 'Roadmap Overview' as the title with three bullet points below. Slide 2 shows 'Timeline' with the Q1 milestone text. The markdown '---' separator automatically created the page break. Both slides use the default template layout. The changes are live in your Google Slides account.

This demonstrates the markdown-to-slides conversion, which is faster than raw API calls for simple content. The MCP applies basic formatting heuristics (headers become titles, lists become bullets). For precise positioning or custom shapes, you'd need the raw API mode instead.

@Google Slides retrieve presentation 1a2b3c4d5e6f and summarize the key points from all slides into a one-paragraph executive summary

I've fetched the presentation, which contains 8 slides covering your Q1-Q2 product strategy. The deck outlines three major initiatives: a mobile app launch targeting 50K users by March, API expansion to support third-party integrations, and a new enterprise pricing tier. Timeline milestones span January design work through June beta testing. The final slide requests $200K additional budget for the mobile team. Overall, the roadmap emphasizes growth through platform openness and premium offerings.

This example pairs the MCP's read capability with AI reasoning to extract insights. The MCP returns the full presentation object (slides, text, images), which the AI then synthesizes. Useful for quick briefings before meetings. Note that image content is described by alt-text only; the AI doesn't perform OCR on slide graphics.

When Google Slides MCP beats manual deck-building for recurring updates

A 12-person startup runs Friday all-hands with a standing deck: OKR progress, metrics dashboard screenshots, and a rotating spotlight section. The ops lead used to copy-paste from Notion and re-export charts every week. With the Google Slides MCP, they script the deck refresh: pull OKR data from their project tracker, generate markdown sections for each department update, and push the whole thing to Slides in one batch. The markdown-to-slides tool handles the layout split automatically using '---' separators. This works because the deck structure is stable and the content sources are already structured. If your all-hands is more freeform or you're designing net-new slides each week, the MCP won't save time—manual layout still wins for one-off creative work. But for templated recurring decks where the content changes and the structure doesn't, this cuts 90 minutes of copy-paste down to a 5-minute script run.

Why this MCP falls short for high-touch sales decks

A 6-person creative agency pitches 3-4 new clients a month. Each proposal deck needs custom layouts, brand-matched colors, and image-heavy case study slides. The Google Slides MCP can create a blank presentation and batch-update text blocks, but it doesn't handle image placement, custom fonts, or theme overrides with the precision a sales deck demands. The markdown mode is great for text-heavy content, but proposals are 60% visual. The agency tried scripting their intro and pricing slides, then manually finishing the portfolio section—but context-switching between code and GUI killed the workflow. If your decks are text-first (like internal reports or training materials), the MCP is a fit. For image-driven, brand-sensitive client work, you'll spend more time fighting the API than you save. Stick with Figma-to-Slides exports or manual builds until your proposal format stabilizes into a true template.

When batch markdown updates make demo decks trivial

A 5-engineer product team demos shipped features every two weeks. They used to screenshot Jira tickets, paste into Slides, and write bullet summaries by hand. Now they pull completed ticket titles and descriptions from their project tracker, format them as markdown with '---' breaks between features, and push the whole batch to a standing demo deck using the markdown-to-slides tool. The MCP auto-generates one slide per feature with consistent layout. They still manually add screenshots for the big wins, but the text scaffolding is instant. This works because demo decks are repetitive and text-heavy—each slide is a ticket summary, not a custom design. If your demos need heavy annotation or you're presenting to external stakeholders who expect polished visuals, you'll still need manual touch-up. But for internal sprint reviews where speed beats polish, this MCP turns 45 minutes of deck prep into a 2-minute script.