google-slides-mcp
google-slides-mcp is an MCP (Model Context Protocol) server that provides tool functions to interact with the Google Slides API, enabling an agent to create presentations, fetch presentation/slide data, perform batch updates to modify slides, and summarize slide text content.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security posture is largely inherited from Google OAuth/Google APIs. The README recommends providing a Google Refresh Token and client secret via environment variables injected into the MCP process, which reduces accidental logging risk but still places highly sensitive long-lived credentials in the runtime environment. No explicit guidance is provided on secret lifecycle/rotation, logging redaction, or minimizing scope/least privilege beyond listing scopes. README also does not mention rate limits or explicit retry/backoff behavior, which can lead to throttling-related failures.
⚡ Reliability
Best When
You want an LLM/agent to operate Google Slides via a local MCP stdio transport, using OAuth credentials configured in the MCP runner.
Avoid When
You cannot safely handle Google OAuth refresh tokens (long-lived credentials) or you need strict guarantees of repeatable, idempotent updates across retries.
Use Cases
- • Generating new Google Slides presentations from structured instructions
- • Reading and extracting slide text (including optional speaker notes)
- • Programmatically updating slide content using batchUpdate requests
- • Agent-driven slide generation workflows (e.g., drafts then refinements)
Not For
- • High-throughput or latency-sensitive production systems (tool calls over stdio; no evidence of performance tuning)
- • Use cases requiring fine-grained access controls beyond Google OAuth scopes
- • Applications needing a public hosted API/webhooks (this is an MCP stdio server)
- • Workflows that require deterministic idempotent writes without tracking request/slide state
Interface
Authentication
Authentication is handled via environment variables injected into the MCP process: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_REFRESH_TOKEN. README indicates scopes like https://www.googleapis.com/auth/presentations (and optional Drive scopes).
Pricing
No pricing information provided; cost likely comes from Google API usage rather than this package.
Agent Metadata
Known Gotchas
- ⚠ Writes via batch_update_presentation may not be idempotent; retries could duplicate or further mutate slides
- ⚠ OAuth credentials are long-lived (refresh token); misconfiguration can cause auth failures across all tools
- ⚠ fields/page retrieval may require correct identifiers (presentationId, pageObjectId); wrong IDs will fail
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for google-slides-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.