A1-x-Tech/mcp-google-slides

**English** | Русский
**A1 Google Slides MCP** lets an AI app build and edit Google Slides presentations in plain language. Draft a deck, add and rearrange slides, write and style text, place shapes, images and tables, keep speaker notes, review comments and export the result as PDF or PPTX.
It uses the Google Slides API with your Google account. Everything inside a deck is addressed by explicit object ids, and it makes the limits of the Slides API explicit instead of implying that every presentation task is possible.
- **32 tools.** Inspect decks and pages, edit slides, text, shapes, images and tables, manage speaker notes and comments, render thumbnails and export files.
- **Connects from the conversation.** Say "connect Google Slides": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
- **Edits are atomic.** Changes ride the API's batchUpdate: one invalid request voids the whole batch, so a deck is never left half-edited.
- **Your Drive stays out of reach.** Comments, export and local-image upload use the Drive API strictly for the one presentation file — there are no tools to list, share, rename or delete Drive files.
- **Minimal Google scopes.** It needs presentations; Drive scopes are required only for local images, comments and export.
Start with a read-only question:
> Show me the slides in the quarterly report deck and what's on each of them.
Connect the server · Explore use cases · Open technical documentation
---
See it work in a minute
> **You:** List the slides of the Q3 review deck and what's on each one.
>
> **Assistant:** Shows a compact inventory: every slide's position, layout and elements with their visible text. Nothing changes.
>
> **You:** Prepare a new slide after the agenda titled “Roadmap”, with the key dates in the body.
>
> **Assistant:** Shows the target deck, the layout and the proposed text, then asks for confirmation before adding it.
>
> **You:** Confirm.
>
> **Assistant:** Adds the slide and fills its placeholders. It does not touch the other slides.
Contents
- Quick start
- What you can ask it to do
- How a presentation changes
- What can change
- Getting access
- Configuration
- Data, limits and background work
- Technical documentation
- Support
Quick start
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
1. Add the server to your AI app.
2. Say "connect Google Slides": the assistant walks you through creating the OAuth client and approving access without editing config files.
3. Ask the read-only question above.
Codex
**In the app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, enter the command npx -y @a1-x-tech/mcp-google-slides@latest and environment variables GOOGLE_SLIDES_CLIENT_ID, GOOGLE_SLIDES_CLIENT_SECRET, GOOGLE_SLIDES_REFRESH_TOKEN, then select **Save** and **Restart**.
**From the command line:**
Codex MCP documentation
Claude Code
Claude Code MCP documentation
Claude Desktop
The current official path is **Settings → Extensions**. For a custom desktop extension, open **Advanced settings → Extension Developer → Install Extension…**, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation
Cursor
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows: