Skip to main content
Glama
Sign In
gws-admin-mcp

gws-admin-mcp

by antct11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gws-admin-mcp

No user-submitted related servers found.

    Related Servers

    • jb_gateway_mcp

      jitheshb83
      A
      license
      B
      quality
      C
      maintenance
      A local MCP server that acts as a secure credential-holding gateway to Google APIs (Gmail, Calendar, Drive), with deny-by-default policy enforcement so agents never see OAuth tokens.
      13
      MIT

    • fabrica-webex-mcp

      kctrey
      A
      license
      Not graded
      quality
      B
      maintenance
      This local MCP server enables AI assistants to query, report on, and, with explicit confirmation, change Webex organizations they administer. It supports multi-org reads, license and workspace inventories, and optional live SIP registration checks while keeping tokens local and writes gated.
      2
      MIT

    • multi-gmail-mcp

      dkaleganov
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that gives an AI client read, search, triage, drafting, attachment/export and label-management access to several Gmail or Google Workspace accounts at once, with each call naming an explicit account. Sending is disabled unless armed twice, mail deletion is impossible, and tokens, exports and audit data stay local.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (get vs list, different resource types like users, groups, devices, reports, etc.). Even similar tools like reports_activities and reports_usage are clearly separated by audit vs usage, and device lists distinguish mobile vs ChromeOS.

    Naming Consistency5/5

    All tool names follow a consistent resource_operation pattern (e.g., users_list, groups_get, orgunits_list). Some names include a subresource (devices_list_mobile, groups_list_members), but the convention remains uniform and predictable.

    Tool Count4/5

    17 tools is a reasonable number for a Google Workspace admin server covering users, groups, devices, reports, org units, roles, and domains. It is slightly on the heavier side but each tool focuses on a distinct administrative area.

    Completeness2/5

    The tool set is almost entirely read-only (get/list/query). There are no create, update, or delete operations for users, groups, devices, org units, roles, or domains, which is a significant gap for an 'admin' server. Management tasks like creating users or updating group settings are impossible.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources