io.github.aringad/google-workspace-mcp
io.github.aringad/google-workspace-mcp
Is the io.github.aringad/google-workspace-mcp MCP server down? Yes. It has given no valid answer since 2026-10-20: install failed.
Google Workspace Admin via MCP. Manage users, groups, aliases, org units.
install failed down since 2026-10-20 · probed 2026-11-14 · unchanged since 2026-10-27
error: Failed to install entrypoints for `google-workspace-admin-mcp`
- Run it
- uvx google-workspace-admin-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/aringad/google-workspace-mcp
- Registry
- active, updated 2026-02-13 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.arikanatakan/revmng-mcp · needs mcp<2
- pyslang-mcp io.github.ariklapid/pyslang-mcp · alive
- agentl io.github.arimayuji/agentl · alive
- io.github.aringad/fattureincloud-mcp · needs env
- Zmanim MCP Server io.github.ariroffe72/zmanim-mcp-server · alive
- Flight Search io.github.arjunprabhulal/mcp-flight-search · alive
- io.github.ark-forge/prove-it · alive
- memory-boost io.github.arnaugonzalez/memory-boost · alive
Servers that mention workspace.
- AutEng Docs — Agent Document Workspace & Publishing ai.auteng/docs · alive
- Bindry ai.bindry/bindry · needs auth
- ai.bridgeapp/bridgeapp · needs auth
- Calaf Seed Tools ai.calaf/seeds · alive
- Dryos Workspace ai.dryos/dryos-workspace · needs auth
- ai.enginy/mcp · needs auth
- Filepad ai.filepad/filepad · server error
- Kive ai.kive/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-20, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.