Connect Google Slides to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Google Slides, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Google Slides + Microsoft Copilot

Let your AI work with Google Slides: read a presentation as text slide by slide with speaker notes, see slides as images, create presentations, add, copy and reorder slides, fill templates, insert text, text boxes and images. Personal Google accounts and Google Workspace.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET

Step 1 — Get credentials

1. Open console.cloud.google.com, pick or create a project, then go to APIs & Services → Library and enable the Google Slides API.
2. Open APIs & Services → OAuth consent screen. Choose Internal if you are on Google Workspace (the simplest option), otherwise External. For External, set the publishing status to In production: while the app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own account you can click through the "unverified app" warning.
3. Open APIs & Services → Credentials → Create credentials → OAuth client ID, choose the application type Web application and add the authorized redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback. If you host AnythingMCP yourself, enter https://your-anythingmcp-host/api/mcp-oauth/callback instead.
4. Paste the client ID into GOOGLE_CLIENT_ID and the client secret into GOOGLE_CLIENT_SECRET, then install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account whose presentations the AI should use. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector: Gmail, Google Calendar, Google Drive, Google Sheets, Google Docs, Google Slides, Google Forms, Google Contacts, Google Meet, Google Tasks, Search Console, Analytics and Ads. Enable each API in that project, reuse the same client ID and secret, and authorize each connector once. Each one asks only for its own permissions.

Finding a presentation: paste the presentation's link into the chat; its id is the long string in https://docs.google.com/presentation/d/<id>/edit. To find presentations by name, add the Google Drive connector as well. The AI reads a deck as text, slide by slide, with the speaker notes, and can render a slide as an image to check the layout. That image link works without signing in for about 30 minutes, so anyone who has it can open it.

Templates and new decks: replacing text everywhere is the reliable way to fill a template with placeholders such as [Customer name], and it keeps the formatting. To build one slide per customer or product, the AI copies a template slide and fills only the copy. A new presentation starts with one title slide in the root of your My Drive. Text boxes and images are placed in points from the top-left corner (a 16:9 slide is 720 x 405 pt), and images must come from a public URL as PNG, JPEG or GIF.

Permissions: the connector asks for https://www.googleapis.com/auth/presentations: read and edit every presentation your account can open. It does not include Google Drive, so the connector cannot list, search, share or delete presentation files.

Read-only setup: change the scope in the connector's OAuth settings to https://www.googleapis.com/auth/presentations.readonly, authorize again and disable google_slides_create_presentation, google_slides_add_slide, google_slides_duplicate_object, google_slides_move_slides, google_slides_insert_text, google_slides_add_text_box, google_slides_replace_all_text and google_slides_create_image.

Switched off at install: google_slides_delete_object and google_slides_batch_update, which can delete slides and content. Turn them on one by one if the AI needs them.

Changes wait for your yes: before every change the AI tells you what it will create, change or delete and in which presentation, and waits for your confirmation. Edits are saved at once, and everyone who has the file open sees them.

Limits: Google allows each user 60 changes and 60 slide images per minute. Above that it answers 429: wait a minute and try again.

Common errors: 401 means the authorization expired or was revoked (always after 7 days while the consent screen is in Testing): click Authorize with Provider again. 403 PERMISSION_DENIED means the account cannot open or edit that presentation, or the scope is read-only; 403 "Slides API has not been used in project" means the Google Slides API is not enabled in the Cloud project. 404 means the id is wrong or belongs to another file type: a PowerPoint file uploaded to Drive is not a Slides presentation until it is converted. A 400 on an image means the URL is not public or the file is not PNG, JPEG or GIF.

The connector does not handle comments, does not share, move, delete or export presentations to PDF or PowerPoint (the Google Drive connector does that) and does not edit PowerPoint files stored in Drive.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Google Slides tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Read the sales deck at this link and summarise every slide together with its speaker notes."
• "Fill in the proposal template: replace [Customer name] with Acme GmbH and [Date] with 1 November 2026."
• "Copy the case study slide three times and fill each copy with one of these customers."
• "Create a presentation called Q4 review with a title slide and one slide each for revenue, pipeline and hiring."
• "Show me slide 4 as an image so I can check the layout."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse