Google Slides MCP Server

If you already use Google Slides, the google slides mcp server is the piece that lets your assistant work with it directly. MCP Server for Google Slides.

What the server does

This project provides a Model Context Protocol (MCP) server for interacting with the Google Slides API. It allows you to create, read, and modify Google Slides presentations programmatically.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Input — **
• Output — ** JSON object representing the created presentation details
• title — The presentation's title
• slideCount — Total number of slides
• lastModified — Revision information
• slides — Array of slide objects containing:
• slideNumber — Position in presentation
• slideId — Object ID of the slide
• content — All text extracted from the slide
• notes — Speaker notes (if requested and available)

Credentials and setup notes

Configuration is passed through the environment: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, YOUR_CLIENT_ID, YOUR_CLIENT_SECRET, YOUR_REFRESH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js (v18 or later recommended) * npm (usually comes with Node.js) * Google Cloud Project with the Google Slides API enabled. * OAuth 2.0 Credentials (Client ID and Client Secret) for your Google Cloud Project. * A Google Refresh Token associated with the OAuth 2.0 credentials and the necessary Google Slides API scopes.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google Slides's toolset — Input, Output, title and 7 more — is a fair guide to whether it matches your workflow. It is maintained by matteoantoci; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Google Slides's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Google Slides.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.