Google Slides MCP
Related Servers
Alternatives to Google Slides MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to build and edit Google Slides presentations through natural language, including managing slides, text, shapes, images, tables, speaker notes, comments, thumbnails, and exporting to PDF or PPTX.3237 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and edit presentation decks—manipulating documents, slides, shapes, text, animations, transitions, and exports—while reading tabular data and generating 18 types of business charts.1MIT
- AlicenseAqualityCmaintenanceEnables low-level interaction with Google Slides API, including template reuse, element bounding box editing, slide rendering, and batch updates for automated slide deck creation.23MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to control Google Workspace services (Slides, Sheets, Drive) through natural language.72 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create and manipulate PowerPoint presentations programmatically, including adding slides, exporting to PDF, and reading metadata.6 npm5MIT
- 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-
TDQS
Scored across 23 tools
Almost every tool pairs a distinct resource with a distinct action, and descriptions disambiguate well (e.g. delete_element explicitly points to delete_slide for whole slides). A few overlaps remain: move_slide vs reorder_slides both change ordering, add_bullets is a wrapper around add_text_box, and get_presentation/list_slides/get_slide cover similar read territory at different granularities.
All 23 tools use consistent snake_case verb_noun form (get_slide, add_table, set_speaker_notes, delete_element, export_deck). Even the compound names like create_deck_from_outline and replace_all_text follow the same predictable convention.
23 tools is at the heavy end, but a Slides editor is a genuinely broad domain and most tools map to a real capability. There is some redundancy (add_bullets as a thin wrapper, move_slide alongside reorder_slides, plus a batch_update escape hatch) that could be trimmed.
The surface covers the full lifecycle: create/read/update/delete slides and elements, ordering, text and character-range formatting, find-and-replace, images, shapes, tables, backgrounds, speaker notes, and PDF/PPTX export. batch_update closes any remaining gaps for advanced API operations.