Some plugins that work in the desktop app can't be used from the CLI agent

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Looks like CLI agent doesn’t send x-cursor-auth to rest-mcp plugin servers, as a result some plugins like Google Docs won’t work in the CLI.

Steps to Reproduce

  1. Install and authenticate the Google Docs plugin in the desktop app.
  2. Start a CLI agent session and try to use it: it shows needsAuth.
  3. Add the rest-mcp URL to mcp.json, run agent mcp login google-docs, then agent mcp list-tools google-docs: 401.

Expected Behavior

Plugins authenticated in the desktop app work in CLI sessions.

Operating System

MacOS

Version Information

3.24.9 (CLI 2026.10.01-14929f9)

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @sagira, thanks for the report.

Desktop and CLI keep separate plugin sign-ins right now, so a plugin that’s connected in the desktop app still needs a one-time sign-in from the CLI. You’re right about the 401: the standalone agent mcp login and agent mcp list-tools commands don’t send the Cursor credential that Cursor-hosted servers like Google Docs need. I’ve flagged that to the team.

Signing in from inside an agent session should work in the meantime:

  1. In your project folder, start agent.
  2. Type /mcp and press Enter.
  3. Pick the Google Docs server and choose Login.
  4. Finish the Google sign-in in the browser, then return to the terminal.
  5. Ask the agent to use a Google Docs tool, for example “create an empty Google Doc called test”.

The same steps work for Sheets, Slides, and Drive. Gmail and Google Calendar plugins currently use Google’s own servers, and the CLI can’t sign in to those yet. That part is flagged too.

Does step 5 work for you? If not, reply with the exact message you see and your CLI version (agent --version).

7

When I try this with the Google Calendar plugin it fails to read or create an event with “Incompatible auth server: does not support dynamic client registration.” even though it appears as authed and enabled. CLI version is 2026.10.01-14929f9.

By the way it ignores when I hit Enter for Logout or Disable under Manage Server tab for some reason, so I can’t confirm if a fresh auth will fix it.

11

Thanks for checking!

For Google Calendar, that’s the part I mentioned that the CLI can’t sign in to yet. Calendar lets the CLI list its tools without signing in, so it shows as connected, but the actual sign-in Google needs isn’t supported in the CLI yet.

To turn it off in the CLI in the meantime, run this from your project folder:

agent mcp disable plugin-google-calendar-google-calendar

On Logout and Disable not responding: when that happens, what does the Tools tab for that server show? Does it say “Loading tools…”, and does Enter start working if you wait a little? Also, does it happen only for Calendar, or for Google Docs too?

12

Ok so just not supported, understood.

It lists the tools, if I wait a while it does say “Logged out of MCP server ‘name’.” However, the state remains the same without a login option after it apparently logs out. Even after I close and start a new CLI session the server still appears enabled in the list view. Happens for any server that is logged in.