botrun-google-slides

This MCP server provides programmatic access to Google Slides via the Google Slides API using a service account for authentication. After installing the MCP server globally, you can load it into Gemini or Claude-compatible tools as an MCP server named google-slides-mcp. The server enables operations such as creating, reading, updating, and managing Google Slides presentations, and includes a move_presentation capability to relocate or copy presentations within Google Drive. To use it, ensure your service account key is present locally and that the MCP server is accessible via the google-slides-mcp command. When integrating with Gemini CLI, you typically point Gemini at the running Google Slides MCP server, and may supply a Google API key as needed by your workflow, while the server itself relies on the service account key file stored in your working directory.

Key capabilities include:

• Create and fetch Google Slides presentations programmatically
• Modify slides, text, shapes, and layouts within a presentation
• Move or copy presentations to Google Drive folders using move_presentation
• Drive API integration for file management and permissions

To use with your tooling, ensure the MCP server command google-slides-mcp is available in your PATH (installed globally), and configure your MCP client to connect to this server and pass any required authentication details via environment variables or configuration as appropriate for your workflow.

Prerequisites:\n- Node.js (v18 or later) and npm installed on your system\n- A Google Cloud project with the Google Slides API enabled and a service account key downloaded as JSON\n\nStep 1: Install the MCP server globally\nbash\nnpm install -g @bohachu/google-slides-mcp\n``\nStep 2: Prepare authentication keys\n- Create a working directory and a keys subdirectory, then place your Google service account key JSON file there named google_service_account_key.json. For example:\nbash\nmkdir -p ~/coding_projects/working/keys\ncp /path/to/downloaded/google_service_account_key.json /coding_projects/working/keys/google_service_account_key.json\n\n- Set the GOOGLE_APPLICATION_CREDENTIALS environment variable to point to the service account key: \nbash\nexport GOOGLE_APPLICATION_CREDENTIALS=/coding_projects/working/keys/google_service_account_key.json\n``\nStep 3: Prepare MCP configuration for Gemini/Claude clients\n- Create the Gemini settings.json (or edit an existing one) to register the google-slides-mcp server:\njson\n{\n "mcpServers": {\n "google-slides-mcp": {\n "command": "google-slides-mcp"\n }\n }\n}\n\n- Alternatively, ensure this can be loaded by your MCP client as a configured server. Step 4: Verify installation and usage\nbash\ngemini -y # or your CLI equivalent to fetch MCP environment status\n

• The server uses a service account key for authentication. Do not expose the key publicly. Keep google_service_account_key.json securely in your project (e.g., in keys/ under your working directory).\n- If you use Gemini CLI, you may also set a Gemini API key via GEMINI_API_KEY as described in the README. The MCP server relies on the service account for Google API access, while Gemini may use its own API keys for orchestration.\n- The Google Slides and Drive permissions of the service account determine what presentations you can access. Share presentations with the service account email if needed.\n- The Move feature (move_presentation) requires Drive API scope access; ensure your service account has appropriate permissions and that the Drive API is enabled in your Google Cloud project.\n- If you update the server or its dependencies, re-run npm install or npm run build as appropriate for your environment.