Labsco
MCP SERVER

Work Gmail and Google Calendar across several accounts at once — query mail with real search syntax, draft and reply, save attachments, and plan around existing events.

Office Suites & Cloud File Storage
Summary
Multi-account is the design, not an afterthought.

Most Google servers assume one mailbox. Here accounts are first-class and each carries a free-text note the model reads, which is what makes the difference between naming an address every time and just saying my work account. The setup cost is real — you are creating your own OAuth client and consent screen — but the payoff is that the credentials stay yours and the mail scope granted is one you chose.

What it is

An MCP server for Gmail and Google Calendar that is built around multiple Google accounts rather than one. Each account is declared with a note about what it is for, so a request can say check my private account's family calendar and land on the right one.

What you get
  • Gmail querying with flexible search — unread, from a given sender, date ranges, has-attachment — rather than only the newest messages
  • Full message retrieval by id, including fetching several messages at once by their ids
  • Draft creation with recipients, subject, body and CC; draft deletion; and replies that can either send immediately or be saved as a draft
  • Saving multiple attachments from emails to your local filesystem
  • Calendar across several calendars: read events in a time range, create events with title, start and end, optional location, description, attendees, custom timezone and notification preferences, and delete events
  • Per-account context through the `extra_info` field, which is where you tell the model what a given account holds
Requirements

Google OAuth2 credentials you create yourself: a Cloud project with the Gmail API and Google Calendar API enabled, an OAuth client id, and `http://localhost:4100/code` added as an authorized redirect URI. The scopes needed are `openid`, `https://mail.google.com/`, calendar and userinfo.email. Put the client id and secret in `.gauth.json` and list your accounts in `.accounts.json`; the first tool call per account opens a browser for consent and then stores credentials in `.oauth.{email}.json`, after which the refresh token is used. Paths are overridable with `--gauth-file`, `--accounts-file` and `--credentials-dir`. The package is `mcp-gsuite` (0.3.0 in pyproject), run with `uvx mcp-gsuite`; Smithery can install it for Claude Desktop automatically.

Setup effort

One command plus a key — npx -y @smithery/cli install @alBERT-launcher/mcp-gsuite --client claude, then supply credentials