Listed from the MCP registry; nobody on Odel publishes it.
MCP server for the Google Slides API: presentations, slides, text, shapes, images and tables.
Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @a1-x-tech/mcp-google-slides
MCP client config
{
"mcpServers": {
"google-slides-mcp": {
"command": "npx",
"args": [
"-y",
"@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.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.batchUpdate: one invalid request voids the whole batch, so a deck is never left half-edited.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
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.
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
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
claude mcp add \
--transport stdio --scope user google-slides \
-- npx -y @a1-x-tech/mcp-google-slides@latest
claude mcp list
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.
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"]
}
}
}
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.
create_presentation creates a deck with one title slide; only the title is honored at creation.list_slides is the compact inventory to start from before any edit.batchUpdate: one invalid request voids the whole batch, so nothing is half-applied.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.
| 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.
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.
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.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.
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.
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.
#; a value from your request can appear in it if the error text contains it. Set ASKADS_TELEMETRY=0 to opt out.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.Found a bug or need a scenario? Create an issue or write in Telegram.
You made it to the end!