Skip to content

Google Workspace

Artific Connect · Google Workspace gives a key Google's own tools across six products: Gmail, Drive, Docs, Sheets, Calendar and Chat. It installs from the Marketplace like any other bundle.

What you get

One toolset, google, holding six of Google's own remote MCP servers — one per product — plus a skill that tells the model which server answers which question. Attach the toolset to a key and the tools are there.

Signing in

The tools act as the person the turn is for, through that person's own Google account — so a turn sees exactly what that person may see. Two things follow:

  • a request must name a user; one that names nobody is told so instead of calling a tool;
  • each person signs in once, from the bundle's page in the console or through the link the model is given the first time it tries.

The consent screen says Artific: the application is this deployment's, registered once by its operator, and no organisation registers one of its own.

Before it works

Your administrator has to allow every host the bundle dials in the key's own egress policy:

  • gmailmcp.googleapis.com, drivemcp.googleapis.com, docsmcp.googleapis.com, sheetsmcp.googleapis.com, calendarmcp.googleapis.com, chatmcp.googleapis.com — the six product servers;
  • accounts.google.com and oauth2.googleapis.com — where a person signs in and where the code is exchanged for a token.

These servers are part of Google's Workspace Developer Preview Program: reaching any of them needs the operator's Google Cloud project to be enrolled in it, on top of registering the OAuth client, and some scopes need Google's own app-verification review before Google allows them to be granted at all, whatever this deployment's key policy allows.

If the operator has not registered and enrolled the Artific application at Google yet, the install waits: the bundle sits at needs configuration and names what it is waiting for.

Good to know

  • Verified 2026-09-24 on developers.google.com/workspace: the six servers are https://{gmail,drive,docs,sheets,calendar,chat}mcp.googleapis.com/mcp/v1, all part of the Developer Preview Program, global, no stated region.
  • A refusal naming a missing or unverified scope is Google's own review holding a permission back from this deployment's application, not a bug — say so rather than retrying.
  • "not found" on a file or event the person named usually means the signed-in account cannot see it, not that it does not exist.
  • The mark: this bundle's card still uses Artific's own placeholder. Google's partner guidance permits a product icon only in context, such as "a grid of products that are compatible with your services", and never by itself; this deployment did not confirm a catalogue card counts as that context, so it has not applied for use (checked 2026-09-24).