Is this an official Google Workspace MCP server?

No. It is Memtro's MCP server with Memtro's Google Workspace connector behind it: the connector reads Google Workspace through its API with the credentials you connect on Dashboard → Connections, and Google Workspace publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Google Workspace?

Not yet. Today every Google Workspace tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · People and HR

Google Workspace MCP server

Google Workspace in any MCP client, through Memtro: Google Workspace does not publish this server. Memtro's Google Workspace connector reads Google Workspace through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Google Workspace directory: people with titles, departments, managers and org units, groups and members, the org-unit tree, and admin / login audit activity (uses the same Google OAuth client as Gmail and Calendar; the connecting user must be a Workspace admin).

Reads

gworkspace_peopleFind people in the Google Workspace directory by name or email (prefix), department, job title, org unit or manager (their email, for direct reports).
gworkspace_personOne person by email or id with their manager, direct reports and group memberships.
gworkspace_groupsGroups by name or email prefix with member counts, or one group (by email or id) with its members and their roles.
gworkspace_orgunitsThe organizational unit tree (paths, names, parents, descriptions).
gworkspace_auditAudit activity from the Reports API, newest first: application "admin" (console changes: users created or suspended…

Connect it

First connect Google Workspace on Dashboard → Connections, then add Memtro to your client once. The Google Workspace tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Google Workspace connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who is in the Sales org unit and who do they report to?
› Which groups is dana@acme.com a member of?
› List everyone whose title mentions Designer
› Who created or suspended users in the admin console this month?
› Were there failed logins for the finance team yesterday?

Questions

Is this an official Google Workspace MCP server?: No. It is Memtro's MCP server with Memtro's Google Workspace connector behind it: the connector reads Google Workspace through its API with the credentials you connect on Dashboard → Connections, and Google Workspace publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Google Workspace?: Not yet. Today every Google Workspace tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.