Cursor IDE and Google Workspace MCP Server Conflict Issue Report

[LenLin83]

Environment Information

• IDE: Cursor

• Node.js Version: v22.14.0

• Operating System: Windows

• Repository: google-workspace-mcp-server

MCP Configuration Structure

json

Apply

{

"mcpServers": {

"google-workspace": {

"command": "C:\\Program Files\\nodejs\\node.exe",

"args": ["path/to/google-workspace-mcp-server/build/index.js"],

"cwd": "path/to/google-workspace-mcp-server",

"env": {

"GOOGLE_CLIENT_ID": "[CLIENT_ID]",

"GOOGLE_CLIENT_SECRET": "[CLIENT_SECRET]",

"GOOGLE_REFRESH_TOKEN": "[REFRESH_TOKEN]"

}

}

}

}

Issue Description

When starting the Google Workspace MCP server from the epaproditus/google-workspace-mcp-server repository, Cursor IDE experiences connection issues:

1. Unable to connect to Anthropic service

2. Error message appears:

text

Apply

We’re having trouble connecting to anthropic.

This might be temporary - please try again in a moment.

(Request ID: 37b0f2e6-557b-44c7-98a5-cf5ed10a161a)

1. The issue resolves immediately after shutting down the MCP server

Steps to Reproduce

1. Clone the repository from GitHub - epaproditus/google-workspace-mcp-server: A Model Context Protocol server for Google Workspace integration (Gmail and Calendar)

2. Follow the setup instructions in the repository’s README

3. Open Cursor IDE

4. Start Google Workspace MCP server

5. Attempt to use Cursor’s AI features

6. Observe connection error

Temporary Solution

Currently, the only effective solution is:

1. Only start the MCP server when Gmail API access is needed

2. Shut down the MCP server immediately after completing Gmail-related operations

3. Avoid using both services simultaneously

Attempted Solutions (Unsuccessful)

1. Modifying proxy settings

2. Changing port configurations

3. Simplifying MCP configuration

4. Reinstalling dependencies

5. Rebuilding the project

I hope this issue report helps other developers who encounter the same problem while working with the google-workspace-mcp-server repository, and I look forward to better solutions from either the Cursor team or the community.