Gmail marketplace plugin (MCP) as an Automation tool
Scheduled Automation “Second Brain Gmail Ingest” lists Gmail as Connected in the Automations editor Tools UI.
On scheduled cloud runs, the agent reports that the MCP catalog only contains:
Cursor Automation Tools
cursor-cloud
No Gmail tools are available (cannot list labels, search threads, get_thread, or modify labels).
Gmail MCP works correctly in local IDE agent chat on the same account (search/list/get_thread/label tools succeed). Gmail does not appear under Dashboard → Integrations (no Login button there), so there is no cloud “managed connector” path to authorize Gmail the way Slack/Atlassian work.
Request / ask
Treat “Gmail Connected” on an Automation as a bug if the cloud run catalog does not include Gmail tools.
Either:
inject marketplace Gmail auth/tools into Automations/Cloud Agents the same way local IDE gets them, or
add Gmail as a first-party managed Integration (Dashboard → Integrations) with a Login flow that Cloud Automations can use (parity with Slack/Atlassian).
Until fixed, please don’t show Connected when the scheduled run cannot use Gmail.
Steps to Reproduce
In an Automation, install/authorize the Cursor Gmail marketplace plugin (works in local IDE chat).
Hey, thanks for the detailed report and steps. That really helps.
What you described is a known issue. The Automations editor checks the MCP server name case-insensitively and shows Connected, but scheduled cloud runs resolve it case-sensitively, so the server silently fails. In the Gmail plugin, the server name in the manifest is lowercase, but when you install the plugin the server string is created with an uppercase letter. That mismatch is the cause. We’re tracking it.
For now, here’s a workaround:
Open the Automation for editing, remove Gmail from the tool picker, add it again, then save. This rewrites the reference with the live server id and name.
If after that you see a run log entry like requires authentication, log in to Gmail for cloud once at cursor.com/agents + menu > MCP Servers > Login. Cloud MCP auth is separate from your IDE login, so it can work locally but still need a separate cloud login.
About Dashboard > Integrations: it’s expected that Gmail won’t show up there. That page only shows first-party connectors like Slack, GitHub, Linear, and Atlassian. Plugin MCP auth is handled via cursor.com/agents, not there.
Also agree with your point that Connected shouldn’t show if the runner can’t actually use Gmail. I shared this case with the team. Let me know if the workaround helped.
I’m glad it’s a known issue. I’ve tried removing and re-applying Gmail to no effect. I was not able to find anyplace around agents about “MCP Servers > Login”. I’m on vers 3.15.19
My workaround is to fire off a prompt in the Agent chat to do what I want until this gets fixed. Thanks for the quick reply.
Thanks for trying it and sharing the result. The fact that remove and re-add didn’t help matches what we’re tracking. The server link gets saved in a form that scheduled Cloud Run can’t resolve, and re-adding it from the picker doesn’t always overwrite it. So it’s not something you misconfigured.
About MCP Servers > Login, that step won’t help right now. Auth only happens after the run finds the server, but in your case it gets dropped earlier, before the auth stage. So logging in won’t change anything until the resolving issue is fixed.
Your workaround of manually running the prompt in Agent chat is a totally reasonable option for now. Gmail tools get picked up correctly there.
We’re tracking the issue, but I can’t share an exact timeline yet. I’ll reply in the thread when there’s an update.