Google Slides MCP: Official but Developer-Preview
Google does have an official MCP server for Slides — but it’s not something you can just switch on. It ships under the Google Workspace Developer Preview Program, and using it means creating a Google Cloud project, enabling two APIs, and configuring an OAuth consent screen yourself. It’s easy to miss, too: Google’s general Workspace MCP page lists servers for Gmail, Drive, Calendar, Chat, and People, and Slides isn’t on it — but Slides has its own dedicated server on a separate page. So if you searched “Google Slides MCP” expecting a one-click connector, the honest answer is: it exists, it’s real, and it’s built for developers first.
Even once it’s running, an MCP server only ever hands your presentation to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your decks for you, nothing fires when a slide changes, and nothing runs while the chat is closed. Here’s what the Google Slides MCP server actually does, what setting it up involves, where it stops even for developers who use it — and what to use instead if you just want Slides work to happen on its own.
Google Slides is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
What the Google Slides MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, Google Antigravity, and others — talk to an outside app through a shared interface. Google’s own Slides MCP docs describe it plainly: Google Slides offers a remote MCP server that lets AI agents securely read and act on your presentation data, built to work with AI applications like Google Antigravity and Claude.
It exposes exactly two tools:
read_presentation— reads a “verbalized” version of a deck by its presentation ID: the structure, styles, and layouts, described in a form an AI can reason over rather than raw slide coordinates.update_presentation— mutates layouts, slides, and elements and runs visual structural batch updates — adding or reordering slides, editing text, restyling elements, all through a single batch call.
That’s it. No third tool for searching your Drive for a deck, no tool for watching a presentation for changes, no tool for exporting to PDF. It reads one presentation and writes to one presentation, both by ID, both inside whatever chat session invoked it.
How to set up the Google Slides MCP server
This is the part that separates Slides from something like HubSpot’s remote MCP server, which any non-developer can point a client at in a few clicks. The Slides server requires actual Google Cloud setup:
- Create a Google Cloud project (or use an existing one).
- Enable two APIs — the Google Slides API (
slides.googleapis.com) and the Google Slides MCP API (slidesmcp.googleapis.com) — viagcloudor the Cloud console. - Configure an OAuth consent screen — set an app name, support email, audience (internal or external, with test users added), and add the scopes the server needs:
presentations.readonlyanddrive.readonly. - Create an OAuth 2.0 web client ID and secret, then add the server’s endpoint (
https://slidesmcp.googleapis.com/mcp/v1) to your MCP client’s config — Google’s instructions currently cover Antigravity and Claude by name, each with its own OAuth redirect URI.
None of that is unreasonable for a developer. It is not something a person who just wants an AI to help build a deck is going to do on a Tuesday afternoon. If you’d rather skip Google Cloud entirely, community-built servers like matteoantoci/google-slides-mcp wrap the Slides API with a simpler local setup — but those are third-party projects, not Google’s own, and you’re trusting their code with your account scopes.
Where the Google Slides MCP stops
Even fully configured, the same limits that apply to every MCP server apply here:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch your presentations; it waits for you to ask.
- No triggers. A comment left on a slide, a deck shared with you, a new version saved before a meeting — none of these can start anything through MCP. There’s no “when this happens in Slides, do that.”
- It’s one app at a time. The Slides MCP server knows Slides. Turning a spreadsheet of numbers into a chart slide, or pushing a finished deck into Slack and an email, means wiring up a separate MCP server for each and hoping your client can juggle them in one turn.
- You own the plumbing, the project, and the scopes. The Google Cloud project, the OAuth consent screen, the client secret, and the blast radius of
presentations.readonlyanddrive.readonlyaccess are all on you to maintain.
So even for the developers who go through the setup, the Slides MCP server is a way to ask about a deck and make one-off edits mid-conversation. It is not a way to make Slides work run — to have something happen on a schedule or in reaction to an event, across the other tools a presentation touches.
Running Google Slides work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits — without any Google Cloud project, OAuth consent screen, or gcloud command. Carly connects to Google Slides natively, plus the ~260 other apps it supports and anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Slides work happens whether or not anyone has a chat window open.
A few things MCP can’t do but a Carly workflow can:
- When a deal closes in your CRM → generate a branded recap slide from a template and drop it into the shared client deck automatically.
- Every Monday morning → pull the week’s numbers from a Google Sheet, build the metrics slides, and email the updated deck to the team for review.
- When a new deck is shared into a folder → summarize its key slides and post the summary to the right Slack channel.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Slides connection and everything downstream.
If you’re a developer who wants to interrogate or edit a deck from inside Antigravity or Claude, Google’s own MCP server is the real, official tool for that — it’s just gated behind a Cloud project setup, not a switch in your Google account. If you want Slides to actually do things on a trigger or a schedule, across every app a presentation flows through, that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Google Slides have an official MCP server?
Yes. Google publishes an official remote MCP server for Slides at slidesmcp.googleapis.com, currently under the Google Workspace Developer Preview Program. It offers two tools, read_presentation and update_presentation, and is documented for use with clients like Google Antigravity and Claude. It isn’t listed on Google’s general Workspace MCP page, which covers Gmail, Drive, Calendar, Chat, and People — Slides has its own dedicated setup page instead.
Can I just turn on the Google Slides MCP server from my Google account? No. Unlike a simple account connection, it requires creating a Google Cloud project, enabling the Slides API and the Slides MCP API, and configuring an OAuth consent screen with specific scopes. It’s built for developers, not a one-click consumer feature.
Can the Google Slides MCP server trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Slides work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Google Slides to AI without coding or hosting a server? Yes. You don’t have to touch Google Cloud, OAuth consent screens, or MCP at all. Carly connects to Google Slides for you and lets you build the automation in plain language — describe what you want to happen and it wires up Slides and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
