com.mcparmory/google-gmail
Google Gmail
Send, read, organize emails, manage labels, drafts, and filters
alive probed 2026-10-19
63tools
≈ 13ktokens, estimate
≈ 6.5 %of Claude's 200k window
9.2×the median server
9.0 sto initialize
460 msto list tools
- Run it
- uvx mcparmory-google-gmail==1.0.4 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- Google Gmail 4.1.1
- Capabilities
- logging, prompts, resources, tools
- Instructions
- none
- Of a 1M window
- ≈ 1.3 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/mcparmory/registry
- Registry
- active, updated 2026-05-12 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| import_message | 742 | 6 % |
| insert_message | 689 | 5 % |
| update_draft | 634 | 5 % |
| send_draft | 621 | 5 % |
| send_message | 610 | 5 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.