Skip to main content
gbrain
Sign in

Gmail · MCP

Gmail in any assistant.

Search, read, file and draft mail from a terminal or an assistant.

Reading is one grant and changing is another, so a client can search a mailbox for months without ever being able to touch it. Sending is a third, and most setups never turn it on: a draft lands in Drafts and waits for a person to press send. 

claude mcp add gbrain https://gbrain.io/mcp --header "Authorization: Bearer <token>"

One endpoint for everything on the plane, not one per service. What this client can call is decided by its permission, not by the address.

The tools it gets

Read from the tool plane, so this is what an assistant is handed today, minus anything its permission does not allow.

gmail_search
Search your email
gmail_read
Read a message
gmail_send
Send email
gmail_labels
See your labels
gmail_draft
Write a draft
gmail_drafts
See your drafts
gmail_label
File a message
gmail_move
Move a message
gmail_mark
Mark a message

Or from a terminal

The same Gmail, four commands from a shell prompt, on the same permission and the same record.

Gmail from the command line

How the whole thing fits

One permission, one daily ceiling, one record, across every client that asks.

Tools

Also on the plane