How to Enable Google Sheets & Slides MCP Server in Manus AI (Step-by-Step)
Manus AI can already write, plan, and reason through complex tasks. What it can't do out of the box is open your actual Google Sheet or edit a real Google Slides deck. That gap closes with an MCP server, and setting one up takes less time than reading this sentence twice would suggest.
This guide walks through enabling the Google Sheets and Google Slides MCP servers inside Manus AI, covers both the official Google route and a faster no-code alternative, and points out where each option actually makes sense.
What an MCP Server Does for Manus AI
MCP stands for Model Context Protocol, an open standard that lets AI agents talk to external tools through one consistent interface instead of a custom integration for every app. Once Manus is connected to an MCP server for Google Sheets or Slides, it can read live data and take real actions instead of working off a description you typed in.
For Sheets, that means Manus can pull cell values, update ranges, insert rows, or set formulas. For Slides, it can read the layout of a presentation, duplicate slides, or restructure content across a deck. Nothing gets copy-pasted. Manus works directly against the file, respecting whatever permissions your Google account already has.
Before You Start
A few things need to be in place first:
A Google account with access to the Sheets or Slides files you want Manus to touch
A Manus AI account with access to the MCP or Integrations settings
Either a Google Cloud project (for the official Google-hosted route) or a Mushrooms account (for the no-code route)
Both routes end at the same place: an MCP server URL or config pasted into Manus. The difference is how much setup happens before you get there.
Option 1: Using Google's Official Sheets and Slides MCP Servers
Google now offers remote MCP servers directly for Sheets and Slides, built to work with MCP-compatible clients. This is the most "official" path, but it involves cloud project setup.
Create or select a Google Cloud project. If you don't already have one, create it from the Google Cloud console.
Enable the required APIs. You'll need to turn on the Sheets API and Slides API for the project separately, since each product runs its own dedicated MCP server and has to be enabled on its own.
Set up the gcloud CLI, either locally or through Cloud Shell, to run the commands Google's setup docs require.
Configure your MCP client. In Manus, go to Settings, find the MCP or Integrations section, and add the server URL Google generates for Sheets and again for Slides.
Test the connection. Ask Manus something simple, like pulling values from a known sheet or duplicating a slide, and confirm it responds correctly. If the tool call goes through and you get a sensible answer back, the server is wired up correctly.
This route is solid if you're already comfortable with Google Cloud and want everything under Google's own infrastructure. It's overkill if you just want Manus reading and writing a spreadsheet by this afternoon.
Option 2: The Faster No-Code Route with Mushrooms
If gcloud projects and API enablement sound like more setup than the task deserves, Mushrooms (viaSocket's MCP server platform) gets you to the same result without touching a console. It exposes both Sheets and Slides, along with thousands of other apps, as ready-to-use MCP tools.
Create a free Mushrooms account at mushroom.viasocket.com. No card required.
Connect Google Sheets and Google Slides from your dashboard, authorizing access the same way you would for any Google sign-in.
Copy your cluster URL, or grab the ready-made JSON config from the dashboard if your Manus setup expects that format instead.
Open Manus AI settings and go to the MCP Servers section.
Paste the URL or config and save.
Run a test prompt, such as asking Manus to list the tabs in a specific sheet or summarize the slides in a deck, to confirm the connection is live.
The whole flow usually finishes in under two minutes, which matters if you're setting this up between other tasks rather than dedicating an afternoon to it.
Sheets vs Slides MCP: What Manus Can Actually Do
Capability | Google Sheets MCP | Google Slides MCP |
|---|---|---|
Read data | Cell values, sheet names, grid properties | Slide layouts, text content, styles |
Take action | Update cells, set formulas, insert rows/columns | Duplicate slides, edit elements, batch layout updates |
Common use case | Pulling live metrics into a report Manus is writing | Rebuilding a deck outline based on new content |
Setup complexity (Google route) | Requires Cloud project + API enablement | Requires Cloud project + API enablement |
Setup complexity (Mushrooms route) | Account + one-click connect | Account + one-click connect |
Choosing Between the Two Routes
Go with Google's own MCP servers if your organization already manages Cloud projects centrally and IT prefers everything routed through Google's infrastructure and OAuth logging. It's the more "enterprise" shaped option, and troubleshooting usually means an administrator checking OAuth logs rather than you retracing your own steps.
Go with Mushrooms if you want Manus working with your files today, without a Cloud project to babysit. It's built specifically to hand AI agents live, read-write access to apps like Sheets and Slides through one dashboard, alongside the full library of supported integrations, and it stays free under a fair usage policy with no rate limits attached. You can see current pricing details here if you're weighing it against other options.
If you're just starting to experiment with MCP in Manus at all, connecting one simple app like Sheets first, getting comfortable with how it behaves, and expanding from there tends to work better than trying to wire up five tools on day one.
Common Setup Mistakes to Avoid
A few things trip people up on both routes:
Enabling only one API when a task needs both Sheets and Slides access
Pasting a URL into the wrong settings section (some Manus plans separate "Connectors" from "MCP Servers")
Forgetting to grant the connected Google account access to the specific file, not just the account itself
Skipping the test prompt step, then assuming the connection failed when it was actually a permissions issue
FAQ
Do I need a paid Manus plan to use MCP servers?
Manus includes several prebuilt MCP servers across its plans, but custom server connections may depend on which plan you're on. Check your account's Integrations section to confirm what's available to you.
Can I connect both Sheets and Slides at the same time?
Yes. They're separate MCP servers, so you'll add each one individually, whether through Google's own setup or through a platform like Mushrooms that exposes both.
Is my data safe when Manus connects to Google Sheets or Slides through MCP?
Both routes are built to inherit the same permissions your Google account already has, meaning Manus can't see or edit anything you haven't already granted access to.
What happens if the connection stops working?
Start with the basics: confirm the URL or config hasn't changed, recheck that the file is shared with the connected account, and rerun a simple test prompt before assuming the whole integration is broken.
Once Sheets and Slides are connected, Manus stops being a tool you feed information into and starts being one that can go get it. That's the actual point of an MCP server setup, not the novelty of the connection itself but what Manus can do once it's live.
