Google Admin
Google Admin Console for managing Google Workspace users, groups, and organizational units.
Verdict
Common use cases
- Onboard new hires during standup
- Audit group membership before a launch
- Add email aliases without leaving chat
- Troubleshoot user access in real time
- Offboard departing employees quickly
Integration
- Vendor
- Google Admin
- Category
- other
- Auth
- OAUTH2
- Tools
- 14
- Composio slug
google_admin
Tools
- Add Alias to Google Workspace User
Adds an email alias to a google workspace user.
- Add User to Google Workspace Group
Adds a user to a google workspace group with the specified role.
- Create Google Workspace Group
Creates a new google workspace group with the specified details.
- Create Google Workspace User
Creates a new google workspace user with the specified details.
- Delete Google Workspace Userdestructive
Deletes a google workspace user permanently. this action cannot be undone.
- Get Google Workspace Group Details
Retrieves detailed information about a google workspace group.
- Get Google Workspace User Details
Retrieves detailed information about a google workspace user.
- List Google Workspace Group Members
Lists all members of a google workspace group with optional filtering and pagination.
- List Google Workspace Groups
Lists google workspace groups with optional filtering and pagination.
- List Google Workspace Users
Lists google workspace users with optional filtering and pagination.
- Remove Alias from Google Workspace Userdestructive
Removes an email alias from a google workspace user.
- Remove User from Google Workspace Groupdestructive
Removes a user from a google workspace group, revoking their group access.
- Suspend/Unsuspend Google Workspace User
Suspends or unsuspends a google workspace user account.
- Update Google Workspace Group Settings
Updates settings for a google workspace group.
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to Integrations. 2. Find Google Admin in the catalog and click Connect. 3. You'll be redirected to Google's OAuth consent screen — sign in with a Workspace super admin account. 4. Grant the requested Directory API scopes (read and write access to users, groups, and aliases). 5. Google will redirect you back to Switchy with a success message. 6. Open any Space and type '@Google Admin list members of sales@yourcompany.com' to test the connection. 7. If the MCP returns a member list, you're ready — if it errors, double-check that your admin account has the Directory API enabled in the Google Cloud Console.
What teammates see: by default, memories from Google Admin are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create New User
@Google Admin create a new user with email jane.doe@ourcompany.com, first name Jane, last name Doe, and temporary password Welcome2024!Open in a Space →
Add to Group
@Google Admin add user john.smith@ourcompany.com to the group support@ourcompany.com as a memberOpen in a Space →
Look Up User
@Google Admin get details for user alex.johnson@ourcompany.com including all aliases and group membershipsOpen in a Space →
List Group Members
@Google Admin list all members of the group engineering@ourcompany.com and show their rolesOpen in a Space →
Add Email Alias
@Google Admin add alias j.doe@ourcompany.com to user jane.doe@ourcompany.comOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Google Admin list all members of the engineering@company.com group and show me who has owner vs. member roles
The engineering@company.com group has 23 members total. 3 owners: alice@company.com, bob@company.com, charlie@company.com. 20 members: dana@company.com, evan@company.com, fiona@company.com... (17 more). This snapshot reflects current membership; roles can change between queries. All members have active accounts in your workspace.
This example shows read-only group inspection, useful for auditing access. Requires Google Workspace Admin SDK scope with group read permissions. The MCP returns membership at query time — if someone is added to the group while you're reviewing the list, you won't see them until you query again.
@Google Admin create a new user jordan@company.com with first name Jordan, last name Lee, and add them to the marketing@company.com group as a member
Created user jordan@company.com (Jordan Lee) successfully. Account is active and a temporary password has been generated — you'll need to retrieve it separately or trigger a password reset email. Added jordan@company.com to marketing@company.com as a member. The user can now receive group emails and access shared resources tied to that group.
This example chains two write operations: user provisioning and group membership. Requires Admin SDK user and group write scopes. Be cautious — user creation is immediate and cannot be undone via this MCP (you'd need to delete the user separately). Always verify email addresses before creating accounts to avoid typos.
@Google Admin get details for all users in the sales@company.com group, then draft a summary of who hasn't logged in for 90+ days
The sales@company.com group has 15 members. I retrieved login activity for each: 3 users haven't logged in for 90+ days: mike@company.com (last login 112 days ago), nina@company.com (last login 98 days ago), omar@company.com (last login 140 days ago). The other 12 members logged in within the past month. Consider reaching out to the inactive accounts to confirm they still need access.
This example pairs the MCP's group and user lookup tools with AI reasoning to surface stale accounts. Requires both group read and user read scopes. Login timestamps depend on Google's activity logs — if a user accessed via a mobile app or third-party client, the 'last login' field may not reflect all activity. Use this as a starting point for access reviews, not a definitive audit.
Use-case deep-dives
When Google Admin MCP beats manual provisioning at 10+ hires/quarter
A 15-person startup hiring three engineers this month can script the entire onboarding sequence: create user accounts, assign group memberships for Slack/GitHub sync, add department aliases, all triggered from a Notion hire checklist. The MCP's 14 tools cover the full lifecycle—create user, add to groups, set aliases—so you're not context-switching between Admin Console tabs. This works until you hit complex conditional logic (like role-based access tied to external HR systems), where a dedicated provisioning tool like Okta makes more sense. If your onboarding is still a Google Sheet and manual clicks, and you're adding more than two people a month, this MCP pays for itself in the first sprint.
How this MCP closes the offboarding loop without a HRIS
A 40-person agency with quarterly contractor churn needs to prove every departing user lost access within 24 hours. The compliance lead runs a weekly Switchy prompt: list all users, cross-reference against the active roster in Airtable, flag orphaned accounts, delete them, log the action. The Get User Details and Delete User tools make this a three-minute task instead of a spreadsheet reconciliation nightmare. The trade-off: if you're already paying for BambooHR or Rippling, their native Google Workspace sync is faster and audits itself. But if your source of truth is a spreadsheet or lightweight PM tool, and you need a paper trail for SOC 2, this MCP is the cheapest way to close the loop without buying a full HRIS.
When dynamic Google Groups replace static distribution lists
A 25-person product org runs projects in Linear, but their Google Groups for project-announce@ and project-eng@ are always stale—someone forgets to add the new PM, the contractor never gets removed. A Switchy workflow watches Linear project assignments and syncs group membership daily: Add User to Group when a Linear issue gets assigned, List Group Members to audit who's actually subscribed, remove people when they roll off. This beats manual updates and doesn't require a Zapier seat per sync. The boundary: if your groups are tied to deeper IAM policies (like GCP resource access), you need Terraform or Pulumi, not an MCP. For communication groups that mirror project rosters, this MCP keeps your lists accurate without anyone remembering to do it.
Frequently asked
What does the Google Admin MCP do in Switchy?
It lets your AI agents manage Google Workspace users and groups directly from Switchy. You can create accounts, assign aliases, add people to groups, retrieve user details, and delete accounts. Think of it as giving your AI assistant the keys to your Google Workspace directory—useful for onboarding automation or bulk user management tasks.
Do I need super admin access to connect Google Admin MCP?
Yes. The OAuth flow requires a Google Workspace admin account with permissions to manage users and groups. If you're not a super admin, the connection will fail or the MCP won't be able to execute directory changes. Check with your IT team before attempting to connect it.
Can the Google Admin MCP reset user passwords or manage device policies?
No. It focuses on user and group lifecycle tasks—creating accounts, managing aliases, adding members to groups. Password resets, device management, and security settings aren't exposed through this MCP. For those, you'll need to use the Google Admin console directly or a different integration.
Why use this MCP instead of the Google Admin API directly?
The MCP wraps the Admin API into natural-language tools your AI agents can call without you writing code. If you're already scripting against the API, stick with that. If you want your team to say "create a user for Jane Doe" in Switchy and have it happen, the MCP is faster.
Who on my team should connect the Google Admin MCP?
Whoever has super admin rights in Google Workspace and understands the risk of giving AI agents write access to your directory. This isn't a read-only integration—agents can delete users and modify groups. Limit the connection to one trusted admin, not the whole team.