A
licenseNot graded
qualityA
maintenanceEnables AI assistants to control Google Workspace services (Slides, Sheets, Drive) through natural language.
101 npm
ISC
A1 Google Slides MCP
by A1-x-Tech
Related Servers
Alternatives to A1 Google Slides MCP
No user-submitted related servers found.
Related Servers
- 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,277 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.21 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-
- AlicenseAqualityDmaintenanceEnables 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
A4.3/5.0
Scored across 32 tools
Disambiguation4/5
Most tools target a clearly distinct resource+action, and descriptions carefully delineate boundaries (e.g. insert_text vs set_text vs replace_text, list_slides vs get_page vs get_presentation). The main friction points are the two escape hatches (batch_update vs raw_request) and the graded read tools, which could still occasionally be mis-selected despite explanatory prose.
Naming Consistency4/5
The dominant convention is a predictable verb_noun pattern (create_presentation, list_slides, get_page, update_text_style, delete_object, etc.). A few outliers deviate slightly (logout as verb-only, auth_status as noun-first, batch_update/raw_request), but the set remains readable and largely consistent.
Tool Count3/5
At 32 tools the surface is heavy and sits in the range the rubric flags as crowded, though each tool covers a genuinely distinct operation and the domain (Google Slides plus auth, export and comments) is complex. It is borderline over-scoped rather than redundant.
Completeness5/5
The set covers the full lifecycle: auth/setup/login, reads at three granularities, slide and element creation/mutation/deletion, text, shapes, images, tables, speaker notes, comments, export, and a raw API escape hatch. Documented out-of-scope items (deleting the presentation, changing themes) are Drive/UI operations, not gaps in the Slides surface.
Maintenance
ActivityMaintained
ResponsivenessNo issues