How do I install Google Slides MCP?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Google Slides MCP need an API key?

The publisher lists these environment variables: GOOGLE_SLIDES_CLIENT_ID, GOOGLE_SLIDES_CLIENT_SECRET, GOOGLE_SLIDES_REFRESH_TOKEN, GOOGLE_SLIDES_ACCESS_TOKEN, GOOGLE_SLIDES_OAUTH_PORT, GOOGLE_SLIDES_API_BASE, GOOGLE_SLIDES_DRIVE_API_BASE, GOOGLE_SLIDES_TIMEOUT_MS, GOOGLE_SLIDES_MAX_RETRIES.

What transport does Google Slides MCP use?

Google Slides MCP runs locally over stdio.

When was Google Slides MCP last checked?

Last checked 2026-11-11. MCP server for the Google Slides API: presentations, slides, text, shapes, images and tables.

Google Slides MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @a1-x-tech/[email protected]

Credentials from the publisher

GOOGLE_SLIDES_CLIENT_ID — Google OAuth2 client id (refresh-token flow).
GOOGLE_SLIDES_CLIENT_SECRET — Google OAuth2 client secret (refresh-token flow). Treat it as a secret.
GOOGLE_SLIDES_REFRESH_TOKEN — Google OAuth2 refresh token, exchanged for access tokens automatically. Treat it as a secret.
GOOGLE_SLIDES_ACCESS_TOKEN — Static OAuth2 access token (~1h lifetime) — alternative to the refresh-token trio, mostly for testing.
GOOGLE_SLIDES_OAUTH_PORT — Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.
GOOGLE_SLIDES_API_BASE — Slides API root override.
GOOGLE_SLIDES_DRIVE_API_BASE — Drive API root override (used internally for comments, export and image upload).
GOOGLE_SLIDES_TIMEOUT_MS — Per-request timeout in milliseconds.
GOOGLE_SLIDES_MAX_RETRIES — Retries on transient errors (429 always; 5xx/network for reads).

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1GOOGLE_SLIDES_CLIENT_ID=<value> GOOGLE_SLIDES_CLIENT_SECRET=<secret> GOOGLE_SLIDES_REFRESH_TOKEN=<secret> GOOGLE_SLIDES_ACCESS_TOKEN=<secret> GOOGLE_SLIDES_OAUTH_PORT=<value> GOOGLE_SLIDES_API_BASE=<value> GOOGLE_SLIDES_DRIVE_API_BASE=<value> GOOGLE_SLIDES_TIMEOUT_MS=<value> GOOGLE_SLIDES_MAX_RETRIES=<value> claude mcp add io.github.a1-x-tech-mcp-google-slides -- npx -y @a1-x-tech/mcp-google-slides@1.1.2

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.a1-x-tech-mcp-google-slides": {4      "command": "npx",5      "args": [6        "-y",7        "@a1-x-tech/[email protected]"8      ],9      "env": {10        "GOOGLE_SLIDES_CLIENT_ID": "<value>",11        "GOOGLE_SLIDES_CLIENT_SECRET": "<secret>",12        "GOOGLE_SLIDES_REFRESH_TOKEN": "<secret>",13        "GOOGLE_SLIDES_ACCESS_TOKEN": "<secret>",14        "GOOGLE_SLIDES_OAUTH_PORT": "<value>",15        "GOOGLE_SLIDES_API_BASE": "<value>",16        "GOOGLE_SLIDES_DRIVE_API_BASE": "<value>",17        "GOOGLE_SLIDES_TIMEOUT_MS": "<value>",18        "GOOGLE_SLIDES_MAX_RETRIES": "<value>"19      }20    }21  }22}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Google Slides MCP

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.

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.

Add the server to your AI app.
Say "connect Google Slides": the assistant walks you through creating the OAuth client and approving access without editing config files.
Ask the read-only question above.

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 add google-slides \
  -- npx -y @a1-x-tech/mcp-google-slides@latest

codex mcp list

Codex MCP documentation

claude mcp add \
  --transport stdio --scope user google-slides \
  -- npx -y @a1-x-tech/mcp-google-slides@latest

claude mcp list

Claude Code MCP documentation

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:

{
  "mcpServers": {
    "google-slides": {
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-slides@latest"]
    }
  }
}

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

Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:

{
  "mcpServers": {
    "google-slides": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-slides@latest"]
    }
  }
}

Cursor MCP documentation

Run MCP: Open User Configuration and add:

{
  "servers": {
    "google-slides": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-slides@latest"]
    }
  }
}

Check it with MCP: List Servers.

VS Code MCP documentation

What you can ask it to do

Inspect a deck

List the slides of this presentation and what's on each one.
Read the speaker notes for slide 5.
Render a thumbnail of the title slide.

Build and rearrange slides

Create a presentation for the Q3 review.
Add a “Roadmap” slide after the agenda, duplicate the template slide, move the summary to the end.
Insert an image from a URL or a local file, add a 4×3 table, create a text box or a rounded rectangle with its caption.

Write and polish text

Put this text into the title placeholder and make the deadline bold and red.
Replace “Q2” with “Q3” across the whole deck.
Rewrite the speaker notes of slide 3 to be shorter.

Review and hand off

List the open comment threads and reply to the first one, resolving it.
Delete the draft slide we no longer need.
Export the deck as PDF or PPTX for someone without Google access.

How a presentation changes

create_presentation creates a deck with one title slide; only the title is honored at creation.
Everything inside a deck — slides, shapes, images, tables — is addressed by object ids. list_slides is the compact inventory to start from before any edit.
Edits go through the API's atomic batchUpdate: one invalid request voids the whole batch, so nothing is half-applied.
Tool inputs are in points; the API stores EMU (1 pt = 12700 EMU). The server converts both ways.

The Slides API cannot delete, rename or share the presentation file — those are Drive file operations outside this server's scope. It cannot import a theme (only instantiate layouts the deck already has) and cannot anchor a new comment to a specific slide. Export is capped at 10 MB, and thumbnail URLs expire after about 30 minutes.

What can change

Operation	What happens	Confirmation boundary
Inspect a deck, page, notes or comments; render a thumbnail; export a file	Reads data, writes only local files	No change
Create a presentation	Adds a new deck to your Google account	Changes Google Slides
Add, duplicate or move slides; create shapes, images, tables	Adds or rearranges deck content	Changes a deck
Set or style text, replace an image, transform an element, edit speaker notes or table structure	Overwrites existing content	Changes a deck
Find & replace across the deck	Changes every match at once	Changes a deck broadly
Delete a slide, element or comment thread	Removes content with no undo through the API	Destructive
Raw `batchUpdate` or raw API request	Can call API methods without a dedicated tool	Potentially destructive

The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.

Getting access

Google Slides requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.

Connect from the chat (recommended)

Say "connect Google Slides" and the assistant runs the flow with you:

setup_instructions prints the checklist: create or select a Google Cloud project, enable Google Slides API, configure the consent screen and create a Desktop app OAuth client.
Download that client's JSON ("Download JSON") and give the assistant its path — set_client stores it owner-only. The secret never goes through the conversation.
start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.
finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-slides/credentials.json (mode 0600).

The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.

Environment variables (CI, unattended installs)

Create or select a Google Cloud project and enable Google Slides API. Enable Google Drive API too if you want comments, export or local-image upload.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account that owns or can edit the presentations. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request the scopes:
```
https://www.googleapis.com/auth/presentations
https://www.googleapis.com/auth/drive.file
```
presentations covers all Slides reads and writes. drive.file covers local-image upload plus comments and export on decks created through this app; request the broader https://www.googleapis.com/auth/drive instead when you need comments or export on arbitrary presentations.

Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.

Configuration

Every variable is optional — with none of them the server connects from the chat.

Variable	Required	Description
`GOOGLE_SLIDES_CLIENT_ID`	No*	OAuth client ID.
`GOOGLE_SLIDES_CLIENT_SECRET`	No*	OAuth client secret.
`GOOGLE_SLIDES_REFRESH_TOKEN`	No*	OAuth refresh token.
`GOOGLE_SLIDES_ACCESS_TOKEN`	No*	Short-lived (~1 h) alternative to the OAuth trio.
`GOOGLE_SLIDES_OAUTH_PORT`	No	Fixed loopback port for the in-chat login; useful over SSH port forwarding.
`GOOGLE_SLIDES_API_BASE`	No	Google Slides API base URL override.
`GOOGLE_SLIDES_DRIVE_API_BASE`	No	Google Drive API base URL override (internal dependency: comments, export, image upload).
`GOOGLE_SLIDES_TIMEOUT_MS`	No	Per-request timeout; default `60000` ms.
`GOOGLE_SLIDES_MAX_RETRIES`	No	Temporary-error retries; default `3`.

* Provide either the OAuth trio or an access token.

Data, limits and background work

Requests go to Google Slides. The local server refreshes Google OAuth tokens and calls the Slides API; comments, export and local-image upload ride the Drive API, scoped to the one presentation file. Its anonymous telemetry contains an installation ID, package version, AI client and platform versions, and tool names — never OAuth tokens, presentation content, tool arguments or prompts. Set ASKADS_TELEMETRY=0 to opt out.
Google applies rate limits. On 429, the server uses backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure. Thumbnails count against a more expensive read quota.
There is no background polling. The server runs only when called. Nothing watches a deck between calls; if your AI app supports scheduled tasks, it can check a presentation periodically.

Technical documentation

MCP capability catalog — task-oriented pages for every tool.
All tools and inputs
Development documentation
Publishing documentation
Google Slides API reference

Support

Found a bug or need a scenario? Create an issue or write in Telegram.

Google Slides MCP

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Google Slides MCP?

Does Google Slides MCP need an API key?

What transport does Google Slides MCP use?

When was Google Slides MCP last checked?

Documentation

Google Slides MCP

See it work in a minute

Contents

Quick start

What you can ask it to do

Inspect a deck

Build and rearrange slides

Write and polish text

Review and hand off

How a presentation changes

What can change

Getting access

Connect from the chat (recommended)

Environment variables (CI, unattended installs)

Configuration

Data, limits and background work

Technical documentation

Support