A1 Google Slides MCP
Related Servers
Alternatives to A1 Google Slides MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to control Google Workspace services (Slides, Sheets, Drive) through natural language.100 npmISC
- 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.1,084 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
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create and manipulate PowerPoint presentations programmatically, including adding slides, exporting to PDF, and reading metadata.17 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-
- 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
TDQS
Scored across 26 tools
Most tools map cleanly to a distinct resource and action, and the descriptions are thorough enough to resolve most ambiguity. The text-related tools (insert_text, set_text, replace_text) and the two escape hatches (batch_update, raw_request) have partially overlapping purposes, so an agent could occasionally select the wrong one.
The naming is consistently snake_case and mostly follows a verb_noun pattern such as create_presentation, list_slides, set_text, and update_transform. The main deviation is raw_request, which is an adjective_noun form rather than verb-first.
At 26 tools, the surface is heavy and above the ideal MCP range, but the server covers a genuinely broad Google Slides API domain including slide management, elements, text, tables, notes, comments, export, and raw requests. The count is justified by the scope, though it still feels large.
The tool surface covers virtually the full presentation lifecycle: creating, reading, listing, editing, duplicating, moving, deleting, text manipulation, image/table operations, speaker notes, comments, thumbnails, and export. Missing operations like deleting the presentation file are explicitly outside the server's stated Drive scope, so there are no meaningful dead ends.