A1 Google Slides MCP
This MCP server lets an AI app connect to Google Slides and inspect, build, and edit presentations through Google Slides API tools.
Connect to Google via OAuth: check auth status, get setup instructions, save an OAuth client, start/finish login, and log out.
Create new Google Slides presentations.
Inspect decks: list slides compactly, get full presentation/page JSON, and list layouts and masters.
Add, duplicate, move, and delete slides or page elements.
Insert, replace, and find-and-replace text across a deck or selected pages.
Style text with bold, italic, underline, strikethrough, fonts, sizes, colors, and links.
Create shapes and insert or replace images from public URLs or local files.
Move and scale page elements.
Create tables, edit table structure, and fill table cells.
Read and write speaker notes.
List, get, create, reply to, resolve, and delete presentation comments.
Render slide/page thumbnails as PNGs.
Export presentations as PDF, PPTX, ODP, or TXT.
Use raw
batchUpdateor raw Slides API requests for operations not covered by typed tools.
Uses the Google Drive API to support presentation comments, export, and local-image upload, strictly limited to the presentation file and without exposing general Drive file management.
Provides tools for creating and editing Google Slides presentations, including managing slides, text, shapes, images, tables, speaker notes, and comments, as well as exporting presentations as PDF or PPTX.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@A1 Google Slides MCP List the slides in my Q3 review deck and what's on each one."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.1with 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.
Related MCP server: Google Workspace MCP Server
Contents
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@latestcodex mcp listclaude mcp add \
--transport stdio --scope user google-slides \
-- npx -y @a1-x-tech/mcp-google-slides@latestclaude mcp listThe 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"]
}
}
}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.
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_presentationcreates 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_slidesis 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 | 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_instructionsprints 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_clientstores it owner-only. The secret never goes through the conversation.start_loginreturns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on127.0.0.1(PKCE), never through the chat.finish_loginexchanges 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.filepresentationscovers all Slides reads and writes.drive.filecovers local-image upload plus comments and export on decks created through this app; request the broaderhttps://www.googleapis.com/auth/driveinstead 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 |
| No* | OAuth client ID. |
| No* | OAuth client secret. |
| No* | OAuth refresh token. |
| No* | Short-lived (~1 h) alternative to the OAuth trio. |
| No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
| No | Google Slides API base URL override. |
| No | Google Drive API base URL override (internal dependency: comments, export, image upload). |
| No | Per-request timeout; default |
| No | Temporary-error retries; default |
* 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. For each tool call it also sends the outcome and, on failure, an excerpt of the error text with e-mails, addresses, tokens, numbers of 4+ digits and quoted text replaced by
#; a value from your request can appear in it if the error text contains it. SetASKADS_TELEMETRY=0to opt out.Google applies rate limits. On
429, the server uses backoff; reads also retry after network and5xxerrors, 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.
Support
Found a bug or need a scenario? Create an issue or write in Telegram.
Available Tools
32 toolsadd_slideAdd a slideA
Adds a slide (batchUpdate createSlide) and returns the new slide's objectId in the reply. Pick the look with either predefined_layout (BLANK, TITLE, TITLE_AND_BODY, SECTION_HEADER, ...) or layout_object_id from list_layouts — not both; with neither the slide copies the layout of the current last slide. insertion_index is the 0-based position (omitted = append at the end). Placeholders inherited from the layout arrive empty — find their object ids via list_slides, then fill them with set_text.
Inputs: presentation_id (required), object_id, insertion_index, layout_object_id, +1 more.
auth_statusGoogle connection statusARead-onlyIdempotent
Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected.
Inputs: no named parameters.
batch_updateRaw batchUpdateADestructive
Sends raw Slides API batchUpdate requests for anything the typed tools don't cover: updateShapeProperties (fill, outline, shadow), updatePageProperties (slide background), updateParagraphStyle, createParagraphBullets, updateTableCellProperties, mergeTableCells, createVideo, createLine, groupObjects, updateSlideProperties and the rest of the request union. requests is the API's requests[] array verbatim, e.g. [{"updateShapeProperties":{"objectId":"...","shapeProperties":{...},"fields":"shapeFill"}}]. The batch is atomic: one invalid request rejects the whole batch and nothing is applied. Lengths/coordinates take {"magnitude":N,"unit":"PT"}; wire enums are UPPER_CASE.
Inputs: requests (required), presentation_id (required).
create_imageInsert an imageA
Inserts an image on a slide (batchUpdate createImage) from EITHER image_url — a public https URL Google's servers can fetch (validated: https-only, no private/local hosts, ≤2 kB; the image itself must be PNG/JPEG/GIF, ≤50 MB, ≤25 megapixels) — OR image_path, a local file that is checked by magic bytes, uploaded to Drive, shared by link for the fetch and DELETED from Drive right after (Slides stores its own copy, so the temp file is disposable; the result reports the cleanup). Omitted size keeps the image's native proportions fitted to the page; position/size are in points. Returns the image objectId in the reply.
Inputs: page_object_id (required), presentation_id (required), x_pt, y_pt, +5 more.
create_presentationCreate a presentationA
Creates a new Google Slides presentation and returns it (presentationId, revisionId, pageSize, the initial title slide with its object ids, layouts and masters). The API honors only the title at creation — add slides with add_slide, content with the text/shape/table/image tools. The new deck starts with one title slide and belongs to the authorized user's Drive. Note: this server cannot delete a presentation; removing the file is a Drive operation outside its scope.
Inputs: title (required).
create_shapeCreate a shapeA
Creates a shape on a slide (batchUpdate createShape), optionally with its initial text in the same atomic batch. Types: text_box, rectangle, round_rectangle, ellipse, diamond, triangle, right_arrow, left_arrow, up_arrow, down_arrow, star, heart, cloud, callout — the API's other ~130 ShapeTypes go through batch_update. Position/size are in points ((0,0) is top-left; a default 16:9 slide is 720x405 pt); omitted geometry defaults to 300x80 pt at (50,50). Returns the shape's objectId in the reply. Fill/outline/shadow are not parameters here — style via batch_update updateShapeProperties; text styling via update_text_style.
Inputs: shape_type (required), page_object_id (required), presentation_id (required), text, +5 more.
create_tableCreate a tableA
Creates an empty rows x columns table on a slide (batchUpdate createTable) and returns its objectId in the reply. Fill cells with set_text / insert_text using row_index + column_index (0-based); restructure later with edit_table. Position/size are in points; omitted geometry lets the API pick a centered default. Cell styling (borders, background) goes through batch_update updateTableCellProperties.
Inputs: rows (required), columns (required), page_object_id (required), presentation_id (required), +5 more.
delete_objectDelete a slide or elementADestructive
Deletes a slide or a page element (shape, image, table, video, line, group) by object id — batchUpdate deleteObject. Deleting a slide removes all its elements and speaker notes; deleting a group removes its children. There is no undo through the API (version history lives in the Slides UI). It cannot delete the whole presentation — that is a Drive file operation outside this server.
Inputs: object_id (required), presentation_id (required).
duplicate_slideDuplicate a slideA
Duplicates a slide (batchUpdate duplicateObject) — the copy, with all its elements and speaker notes, lands immediately after the original and its new objectId comes back in the reply. Works on any page element id too (the copy lands on the same slide, slightly offset). Move the copy with move_slides afterwards if needed.
Inputs: presentation_id (required), slide_object_id (required).
edit_tableEdit table structureADestructive
Restructures an existing table in one call. action=insert_rows needs row_index (+optional below, default true, and count 1-20); insert_columns needs column_index (+optional right, default true, and count); delete_row needs row_index and delete_column needs column_index — deletion permanently discards the cells' content, and the remaining rows/columns shift so indexes change between successive edits (re-check with list_slides). Cell TEXT is written with set_text/insert_text (row_index + column_index), not here.
Inputs: action (required), presentation_id (required), table_object_id (required), below, +4 more.
export_presentationExport the presentationARead-onlyIdempotent
Downloads the whole presentation as pdf, pptx, odp or txt (txt = all text incl. speaker notes) and saves it to output_path, overwriting an existing file. Served by the Drive export endpoint internally, which caps exports at 10 MB — a bigger deck fails with an export-size error (split it or use the Slides UI). Requires a Drive scope on the OAuth token (drive.readonly is enough; presentations-only gets a 403). Returns saved_to, bytes and mime_type; nothing in the presentation changes.
Inputs: format (required), output_path (required), presentation_id (required).
finish_loginFinish the Google loginAIdempotent
Second step: waits up to 20 s for the browser consent to finish, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed.
Inputs: no named parameters.
get_pageGet one pageARead-onlyIdempotent
Returns one page in full by its object id — works for slides, layouts, masters and notes pages alike. For a slide the response includes slideProperties.notesPage (the speaker-notes page) and every pageElement with its size, transform (EMU: 1 pt = 12700 EMU) and complete text. Use it when list_slides' summary is not enough for one page but the whole deck via get_presentation would be too much.
Inputs: page_object_id (required), presentation_id (required).
get_presentationGet a presentationARead-onlyIdempotent
Returns the raw presentation JSON: slides[] with every page element (shapes, text runs, tables, images), layouts[], masters[], notesMaster, pageSize (EMU: 1 pt = 12700 EMU) and revisionId. WARNING: a full deck is often hundreds of kilobytes — prefer list_slides for an inventory, and pass fields (a Google fields mask, e.g. "slides(objectId,pageElements(objectId,shape(text)))") to trim this response when you need raw detail.
Inputs: presentation_id (required), fields.
get_speaker_notesGet speaker notesARead-onlyIdempotent
Returns a slide's speaker notes as plain text, plus the speakerNotesObjectId (the text shape on the slide's hidden notes page). The lookup fetches the slide's notes page internally, so you only need the slide's object id from list_slides. An empty string means the slide has no notes yet. Notes text is also searched by replace_text.
Inputs: presentation_id (required), slide_object_id (required).
get_thumbnailGet a slide thumbnailARead-onlyIdempotent
Renders one page (slide, layout or master) as a PNG. Without output_path it returns contentUrl + width/height — the URL is short-lived (~30 minutes) and served from googleusercontent.com. With output_path the PNG is downloaded and saved to that local file instead (the download is restricted to Google's image hosts). size: large (1600px, default), medium (800px) or small (200px). This is the way to SEE what a slide actually looks like — the JSON never shows rendering. Counts as an expensive read in the API quota.
Inputs: page_object_id (required), presentation_id (required), size, output_path.
insert_textInsert textA
Inserts text into a shape or a table cell (batchUpdate insertText) at a 0-based character index (default 0 = the beginning). For a table cell pass row_index + column_index together. Text carries \n for new paragraphs; the target must be a shape that can hold text or a table — images and lines cannot. To REPLACE what's already there use set_text instead; to fill an empty layout placeholder this works directly (find its object id via list_slides).
Inputs: text (required), object_id (required), presentation_id (required), row_index, +2 more.
list_layoutsList layouts and mastersARead-onlyIdempotent
Lists the presentation's theme building blocks: layouts[] (objectId, name like TITLE_AND_BODY, displayName, masterObjectId), masters[] and the notesMasterObjectId. Layout object ids feed add_slide's layout_object_id; the Slides API cannot import a new theme or change the master set — themes are chosen in the UI, this tool only reads what the deck already has.
Inputs: presentation_id (required).
list_slidesList slides (compact inventory)ARead-onlyIdempotent
Compact inventory of the deck — the read to start from: presentationId, title, revisionId, pageSizePt, slideCount and per slide its 0-based index, objectId, layoutObjectId, speakerNotesObjectId and elements[] with each element's objectId, type (shape type / table RxC / image / video / line / group), placeholder role and visible text (truncated to 160 chars). All mutation tools address these object ids, so call this before editing; per-element geometry and full text need get_presentation or get_page.
Inputs: presentation_id (required).
logoutDisconnect from GoogleADestructive
Revokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect.
Inputs: no named parameters.
manage_commentsManage commentsADestructive
Comment threads on the presentation file (served by the Drive API internally — scoped to this one file, no generic Drive access). action=list returns comments with replies and resolved status (pageSize/page_token to paginate, include_deleted for tombstones); get needs comment_id; create needs content and starts a new unanchored thread (the API cannot anchor a new comment to a specific slide or shape); reply needs comment_id + content and/or resolve=true (resolve closes the thread); delete needs comment_id and permanently removes the thread with all replies. Requires a Drive scope on the OAuth token (https://www.googleapis.com/auth/drive) — a presentations-only token gets a 403 here.
Inputs: action (required), presentation_id (required), content, resolve, +4 more.
move_slidesMove slidesA
Moves one or more slides to a new position (batchUpdate updateSlidesPosition). slide_object_ids must appear in their current deck order with no duplicates; insertion_index is the 0-based position BEFORE the move is applied (moving a slide down: index counts with the slide still in its old place). Use list_slides to see the current order first.
Inputs: insertion_index (required), presentation_id (required), slide_object_ids (required).
raw_requestRaw Google Slides API callADestructive
Escape hatch to call any Google Slides API v1 path directly, for requests even batch_update doesn't cover — e.g. GET "v1/presentations//pages/" with a custom fields mask in the query string, or a POST with a body shaped differently from the typed tools. The Slides API only has GET and POST endpoints; the path is relative to https://slides.googleapis.com and may carry a query string. The Bearer token is added automatically; a path resolving to a foreign origin is rejected. Drive endpoints (comments, export) are NOT reachable here — use manage_comments / export_presentation.
Inputs: path (required), body, method.
replace_imageReplace an imageADestructiveIdempotent
Swaps the bitmap of an existing image element while keeping its frame, position and effects (batchUpdate replaceImage). The new picture comes from image_url or image_path with exactly the same validation/upload/cleanup rules as create_image. replace_method: center_inside (default — scales to fit inside the frame, keeping aspect) or center_crop (fills the frame, cropping the overflow).
Inputs: image_object_id (required), presentation_id (required), image_url, image_path, +1 more.
replace_textFind & replace textADestructiveIdempotent
Finds and replaces every occurrence of a string across the whole deck — shapes and table cells on slides, and their speaker notes (batchUpdate replaceAllText). Scope it with page_object_ids to touch only specific slides. Matching is literal (no regex), case-sensitive by default (match_case=false to ignore case). Returns occurrencesChanged in the reply — 0 means nothing matched, check the exact wording with list_slides. The classic template flow: duplicate a template deck, then replace {{placeholders}}.
Inputs: find (required), replace (required), presentation_id (required), match_case, +1 more.
set_clientSave the OAuth clientAIdempotent
Saves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login.
Inputs: path (required).
set_speaker_notesSet speaker notesADestructiveIdempotent
Replaces a slide's speaker notes with the given text (empty string clears them). The tool resolves the slide's speakerNotesObjectId internally and rewrites that shape atomically — you pass the slide's object id, not the notes shape id. Notes are visible in the presenter view and exported by format txt; use \n for paragraphs.
Inputs: text (required), presentation_id (required), slide_object_id (required).
set_textSet (replace) textADestructiveIdempotent
Replaces the ENTIRE text of a shape or table cell: one atomic batch of deleteText(ALL) + insertText. If the target has no text yet the delete is skipped automatically, so it works on empty placeholders too. An empty text just clears the object. Replacing text drops per-character styling — restyle with update_text_style afterwards if needed. For a table cell pass row_index + column_index together.
Inputs: text (required), object_id (required), presentation_id (required), row_index, +1 more.
setup_instructionsSetup instructionsARead-onlyIdempotent
Step-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat.
Inputs: no named parameters.
start_loginStart the Google loginAIdempotent
First step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login.
Inputs: no named parameters.
update_text_styleStyle textADestructiveIdempotent
Styles the text of a shape or table cell (batchUpdate updateTextStyle): bold, italic, underline, strikethrough, font_family (e.g. "Roboto"), font_size_pt, foreground_color (#RRGGBB) and link_url. Only the provided fields change (the field mask is computed automatically); at least one is required. By default the whole text is styled; pass start_index + end_index (0-based character offsets, end exclusive) to style a range — get the offsets from get_page's textElements. For a table cell add row_index + column_index.
Inputs: object_id (required), presentation_id (required), bold, italic, +10 more.
update_transformMove / scale an elementADestructiveIdempotent
Moves and/or scales a page element (batchUpdate updatePageElementTransform). mode=absolute REPLACES the element's whole transform: translate_x_pt/translate_y_pt become the new top-left-ish origin and omitted scales default to 1 — NOT to the current values, so an absolute move of a scaled element also resets its scale unless you resend it. mode=relative multiplies onto the existing transform: translate shifts by the given points, scale 2 doubles the current size (scaling happens around the origin, which also shifts the element — for a simple move prefer relative translate only). Element geometry to reason from is in get_page.
Inputs: mode (required), object_id (required), presentation_id (required), scale_x, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Most tools target clearly distinct resources or actions, and descriptions explicitly separate insert_text vs set_text vs replace_text and get_presentation vs list_slides vs get_page. However batch_update and raw_request are overlapping generic escape hatches, and create_shape with initial text partially overlaps the text insertion tools.
Names are consistently snake_case and mostly follow an action_noun pattern such as create_presentation, list_slides, and update_text_style. Minor deviations like auth_status, setup_instructions, batch_update, and raw_request are not verb-first but remain clear and predictable.
At 32 tools the surface is above the 25+ threshold and feels heavy for a Slides MCP, especially with six auth/setup tools plus multiple specialized mutation tools and two generic escape hatches. The capabilities are rich, but selection cost is high and some tools could be consolidated.
The set covers presentation creation, slide/page reads, element and text editing, tables, images, speaker notes, comments, thumbnails, export, auth, and raw API escape hatches. Notable gaps remain around presentation-level Drive operations: renaming, deleting, or duplicating a whole deck is not supported, so the mentioned template duplication flow cannot be completed with the provided tools.
Maintenance
Related MCP Connectors
Generate AI slide decks and export native PowerPoint (.pptx) and PDF presentations from chat.
Generate, edit, and export AI presentations to PDF, PPTX, or a shareable link.
Create, edit, export and manage presentations. Requires a paid PPT.AI API merchant account.
Create designed slide decks from a prompt, notes, or an outline, then export them or share a link.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to create, edit, and manipulate PowerPoint presentations programmatically with support for text styling, shapes, slide rearrangement, and direct Office XML access.81-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Google Workspace services (Slides, Sheets, Drive) through natural language.113 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create and manipulate PowerPoint presentations programmatically, including adding slides, exporting to PDF, and reading metadata.16 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, read, and modify Google Slides, Sheets, Docs, and Drive documents programmatically. Supports file management, content editing, and version history retrieval.528 npmMIT