Gmail + Google Docs MCP Server (rohinigowdaiah1111/MCP-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Gmail + Google Docs MCP Server

An MCP server that provides tools for drafting and sending Gmail emails, as well as creating and appending to Google Docs, using OAuth 2.0 authentication.

→ rohinigowdaiah1111/MCP-server· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rohinigowdaiah1111

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: GOOGLE_CLIENT_SECRET, MCP_AUTH_TOKEN, TOKEN_ENCRYPTION_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configALLOWED_GOOGLE_ACCOUNTS_(unset, i.e. any account)_ Comma-separated email allowlist. Not yet enforced — see the NOTE comment in src/auth.ts for what's needed to wire it up (requires the openid/userinfo.email scopes).
configENABLE_DOCS_APPENDtrue If false, the docs_append_text tool is not registered at all
configENABLE_HTML_EMAILtrue If false, gmail_create_draft/gmail_send_email reject isHtml: true with an INVALID_INPUT error
configGOOGLE_APPLICATION_CREDENTIALS_(unset)_ Path to a service-account key file. Not yet used — reserved for a future service-account auth mode; see the NOTE comment in src/auth.ts.
configGOOGLE_CLIENT_ID5. Copy .env.example to .env and fill in and GOOGLE_CLIENT_SECRET from that OAuth client (adjust GOOGLE_REDIRECT_URI too if you want a different local port/path).
🔐 secretGOOGLE_CLIENT_SECRET5. Copy .env.example to .env and fill in GOOGLE_CLIENT_ID and from that OAuth client (adjust GOOGLE_REDIRECT_URI too if you want a different local port/path).
configGOOGLE_REDIRECT_URIApplication type: Desktop app (accepts any loopback redirect URI, so below doesn't need to be pre-registered).
configGOOGLE_TOKEN_STORAGE_PATH./tokens.json Where the access/refresh token is stored (encrypted at rest); relative paths resolve from the project root
configLOG_LEVELinfo Structured (JSON) log verbosity written to stderr: trace\debug\info\warn\error\fatal
configMAX_ATTACHMENT_BYTES20971520 (20MB) Max size per email attachment
configMAX_CONFLICT_RETRIES3 Retry attempts for docs_append_text when a concurrent edit is detected
🔐 secretMCP_AUTH_TOKENPOST/GET/DELETE /mcp — the actual MCP endpoint (Streamable HTTP transport), gated by Authorization: Bearer <>.
configMCP_SERVER_NAMEgoogle-workspace-mcp-server Name this server reports over MCP
configMCP_TRANSPORTstdio "stdio" for local Cursor usage, or "http" to bind an HTTP server instead (for remote hosting)
configRATE_LIMIT_PER_MINUTE60 Max calls allowed per tool per rolling 60s window before returning a RATE_LIMITED error
🔐 secretTOKEN_ENCRYPTION_KEY_(auto-generated)_ Base64, 32-byte key used to encrypt the token storage file at rest; if unset, a random key is generated once into .token.key
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — gmail_create_draft (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gmail_send_email (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gmail_send_draft (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/rohinigowdaiah1111/mcp-server)](https://m8ven.ai/mcp/rohinigowdaiah1111/mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b2a7602ad5e855865910e9482b50afa3ee00b495
code hash: 72a326bfe2522ce4b92bb132630cdab4f5ec19f1ee6b74a20c2b5c0b91a965ba
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client