F
licenseB
qualityD
maintenanceA local MCP server that provides a safe Google Workspace admin console, enabling AI agents to read users, groups, devices, and reports, with optional write operations gated by explicit confirmation.
17
-
gwsadm-mcp
by shigechika
Related Servers
Alternatives to gwsadm-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.1001-
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for narrowly scoped Google Workspace user lookups via the Admin SDK Directory API, providing user status, search, aliases, and summary tools with strict domain and trust-boundary controls.-
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Microsoft Entra ID (Azure AD) that enables querying user sign-in logs, group memberships, and assigned Microsoft 365 licenses via Microsoft Graph API. Provides security and audit visibility without any write operations.-
- AlicenseBqualityDmaintenanceProduction-ready MCP server for Google Workspace providing broad coverage across Gmail, Drive, Calendar, Docs, Sheets, and more, with safe-by-default write operations and markdown-to-Google-Docs support.100MIT
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3422 npm17MIT
TDQS
A4.1/5.0
Scored across 21 tools
Disambiguation4/5
Most tools map to clearly distinct resources/actions, and the descriptions explicitly disambiguate confusing pairs (get_user vs suspended_accounts, login_audit vs suspended_accounts vs user_activity, group_delivery_policy vs gmail_message_trace). The only real overlap is between the composite tools (compromise_sweep, daily_brief) and the primitive tools they bundle, plus the daily_brief / daily_brief_start / daily_brief_result trio, where an agent must choose between a sync call and an async job.
Naming Consistency4/5
All names are snake_case and readable, with a consistent resource-first/report-name style (user_activity, ip_activity, login_audit, drive_external_sharing). Minor deviation: a couple use verb_noun (get_user, list_group_members) while most are noun phrases, but the style never becomes confusing.
Tool Count4/5
21 tools is at the upper edge but justified by the genuinely broad domain: directory, Reports API audits, Drive sharing, Gmail trace/usage, groups, DMARC, status dashboard, plus a sync/async pair. Each tool earns its place; only the daily_brief trio feels like a small inflation.
Completeness4/5
Covers read-side lifecycle well: user state, suspended accounts, tokens, activity, IP pivots, admin audit, Drive sharing and doc history, group membership and posting policy, DMARC, and Gmail delivery trace/usage. Gaps are deliberate (read-only, no remediation) but notable: Gmail forwarding/filter settings are only reachable through compromise_sweep, and there is no standalone per-user Gmail usage or group settings beyond posting policy.
Maintenance
ActivityActive
ResponsivenessOutdated data