Labsco
MCP SERVER

GAM MCP Server

by dbarks

Administer Google Workspace users, groups and org units through GAM, from the assistant instead of the command line.

Identity, Access, Secrets & Encryption
Summary
GAM's admin surface, without the syntax.

GAM already does this work; the friction is remembering its command shapes. Here the intent is stated in words, the parameters are validated, and only a known set of commands can be built from them.

What it is

A wrapper around GAM, the Google Workspace command-line admin tool, exposing its user, group, org-unit and domain operations as tools. It shells out to the GAM binary you have already authenticated, and only whitelisted commands are allowed through.

What you get
  • Users listed and filtered by domain or query, and one user's full record fetched
  • Users created, updated and suspended
  • A user moved between organisational units, and the org units themselves listed
  • Groups listed and created, one group's detail read, and members added with a role
  • Domain information read back
  • Inputs validated before a command is built, with only whitelisted GAM commands allowed to run
Requirements

GAM installed and already authenticated against your Workspace — that one-time authorisation happens outside this server. Node.js, a local build, and the path to the GAM binary if it is not already on your PATH. Whatever the authenticated GAM account can do in Workspace, these tools can do.