Gmail & Google Calendar MCP

MCP日程管理

提供方 未标注

日程管理 SSE · 服务端推送 OAuth 授权 社区 / 第三方
查看接入方式

全面解析Gmail & Google CalendarMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Gmail & Google Calendar能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Gmail & Google Calendar MCP 属于日程管理类 MCP 服务器,SSE · 服务端推送,OAuth 授权,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类日程管理 传输方式SSE · 服务端推送 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

日程管理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

SSE · 服务端推送 OAuth 授权
早期远程传输方式,正在被 HTTP 取代
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程安排

按空闲时间自动排日程。

提醒与待办

设提醒、管待办清单。

时间协调

在多人之间找共同空档。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在日程管理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gmail & Google Calendar MCP当前 未标注 SSE · 服务端推送 远程部署 有 2026-05-17
Todoist MCP Server 79e800d2 35 stdio · 本地进程 支持远程部署 有 2026-05-17
Outlook Calendar MCP 7 stdio · 本地进程 本地部署 有 2026-05-18
MCP Server Apple Events 5 stdio · 本地进程 本地部署 有 2026-05-17
y-cli 未标注 stdio · 本地进程 本地部署 无 2026-10-05
Google Calendar 未标注 HTTP · 远程 支持远程部署 有 2026-05-17

服务器档案

日程管理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类日程管理本站按上游分类展示
连接方式SSE · 服务端推送早期远程传输方式,正在被 HTTP 取代
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

6.5 KB
来自项目仓库与上游目录的原文,未做删改

mcp-gsuite MCP server

MCP server to interact with Google produts.

Example prompts

Right now, this MCP server supports Gmail and Calendar integration with the following capabilities:

  1. General
    * Multiple google accounts

  2. Gmail
    * Get your Gmail user information
    * Query emails with flexible search (e.g., unread, from specific senders, date ranges, with attachments)
    * Retrieve complete email content by ID
    * Create new draft emails with recipients, subject, body and CC options
    * Delete draft emails
    * Reply to existing emails (can either send immediately or save as draft)
    * Retrieve multiple emails at once by their IDs.
    * Save multiple attachments from emails to your local system.

  3. Calendar
    * Manage multiple calendars
    * Get calendar events within specified time ranges
    * Create calendar events with:
    + Title, start/end times
    + Optional location and description
    + Optional attendees
    + Custom timezone support
    + Notification preferences
    * Delete calendar events

Example prompts you can try:

  • Retrieve my latest unread messages
  • Search my emails from the Scrum Master
  • Retrieve all emails from accounting
  • Take the email about ABC and summarize it
  • Write a nice response to Alice's last email and upload a draft.
  • Reply to Bob's email with a Thank you note. Store it as draft

  • What do I have on my agenda tomorrow?

  • Check my private account's Family agenda for next week
  • I need to plan an event with Tim for 2hrs next week. Suggest some time slots.

Quickstart

Install

Installing via Smithery

To install G Suite Integration for Claude Desktop automatically via Smithery:```bash
npx -y @smithery/cli install @alBERT-launcher/mcp-gsuite --client claude


#### Oauth 2

Google Workspace (G Suite) APIs require OAuth2 authorization. Follow these steps to set up authentication:

1. Create OAuth2 Credentials:
   - Go to the Google Cloud Console
   - Create a new project or select an existing one
   - Enable the Gmail API and Google Calendar API for your project
   - Go to "Credentials" → "Create Credentials" → "OAuth client ID"
   - Select "Desktop app" or "Web application" as the application type
   - Configure the OAuth consent screen with required information
   - Add authorized redirect URIs (include `http://localhost:4100/code` for local development)

2. Required OAuth2 Scopes:```json
   [
     "openid",
     "https://mail.google.com/",
     "https://www.googleapis.com/auth/calendar",
     "https://www.googleapis.com/auth/userinfo.email"
   ]
  1. Then create a .gauth.json in your working directory with client```json
    {
    "web": {
    "client_id": "$your_client_id",
    "client_secret": "$your_client_secret",
    "redirect_uris": ["http://localhost:4100/code"],
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token"
    }
    }

4. Create a `.accounts.json` file with account information```json
{
    "accounts": [
        {
            "email": "alice@bob.com",
            "account_type": "personal",
            "extra_info": "Additional info that you want to tell Claude: E.g. 'Contains Family Calendar'"
        }
    ]
}

You can specifiy multiple accounts. Make sure they have access in your Google Auth app. The extra_info field is especially interesting as you can add info here that you want to tell the AI about the account (e.g. whether it has a specific agenda)

Note: When you first execute one of the tools for a specific account, a browser will open, redirect you to Google and ask for your credentials, scope, etc. After a successful login, it stores the credentials in a local file called .oauth.{email}.json . Once you are authorized, the refresh token will be used.

Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows: %APPDATA%/Claude/claude_desktop_config.json

Development/Unpublished Servers Configuration```json
{
"mcpServers": {
"mcp-gsuite": {
"command": "uv",
"args": [
"--directory",
"<dir_to>/mcp-gsuite",
"run",
"mcp-gsuite"
]
}
}
}


  Published Servers Configuration```json
{
  &quot;mcpServers&quot;: {
    &quot;mcp-gsuite&quot;: {
      &quot;command&quot;: &quot;uvx&quot;,
      &quot;args&quot;: [
        &quot;mcp-gsuite&quot;
      ]
    }
  }
}

Configuration Options

The MCP server can be configured with several command-line options to specify custom paths for authentication and account information:

  • --gauth-file: Specifies the path to the .gauth.json file containing OAuth2 client configuration. Default is ./.gauth.json.
  • --accounts-file: Specifies the path to the .accounts.json file containing information about the Google accounts. Default is ./.accounts.json.
  • --credentials-dir: Specifies the directory where OAuth credentials are stored after successful authentication. Default is the current working directory with a subdirectory for each account as .oauth.{email}.json.

These options allow for flexibility in managing different environments or multiple sets of credentials and accounts, especially useful in development and testing scenarios.

Example usage:```bash
uv run mcp-gsuite --gauth-file /path/to/custom/.gauth.json --accounts-file /path/to/custom/.accounts.json --credentials-dir /path/to/custom/credentials


This configuration is particularly useful when you have multiple instances of the server running with different configurations or when deploying to environments where the default paths are not suitable.

## Development

### Building and Publishing

To prepare the package for distribution:

1. Sync dependencies and update lockfile:```bash
uv sync
  1. Build package distributions:```bash
    uv build

This will create source and wheel distributions in the `dist/` directory.

3. Publish to PyPI:```bash
uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:
* Token: --token or UV_PUBLISH_TOKEN
* Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:```bash
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite


Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

You can also watch the server logs with this command:```bash
tail -n 20 -f ~/Library/Logs/Claude/mcp-server-mcp-gsuite.log

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Gmail & Google Calendar MCP 怎么安装?

在客户端按下面的安装命令接入:npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite。装完在客户端配置里引用同一个包或端点。

Gmail & Google Calendar MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Gmail & Google Calendar MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gmail & Google Calendar MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Gmail & Google Calendar MCP 能提供哪些能力?

资料显示能力标签包括 日程管理、JavaScript、Gmail集成、OAuth认证。具体工具清单以官方文档为准。

Gmail & Google Calendar MCP 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

Gmail & Google Calendar MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为SSE · 服务端推送。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。