Gmail MCP server
{
"mcpServers": {
"pulsemcp-gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "${input:agent_orchestrator_base_url}",
"FLY_IO_API_TOKEN": "${input:fly_io_api_token}"
}
}
},
"inputs": [
{
"id": "agent_orchestrator_base_url",
"type": "promptString",
"description": "Agent orchestrator base url",
"password": true
},
{
"id": "fly_io_api_token",
"type": "promptString",
"description": "Fly io api token",
"password": true
}
]
}{
"mcpServers": {
"pulsemcp-gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y gmail-workspace-mcp-serverversion 0.4.12
What it does
MCP server for Gmail that supports OAuth2 authentication for personal accounts and service account authentication for Google Workspace. It allows LLM-powered applications to interact with Gmail programmatically.
- Retrieve and search emails from a Gmail inbox to include messages in LLM context
- Send emails on behalf of a user or Workspace account through an LLM application
- Manage Gmail labels, drafts, and message metadata in automated workflows
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.