Claude Code and Google Docs, Sheets and Slides: Google Workspace vs Artifacts
Three ways to get an AI agent's work into Google Docs, Sheets and Slides (Claude's Google connectors, OpenAI's Google Drive plugin for Codex, and Google's Workspace MCP servers), compared with Artifacts, a workspace any MCP agent publishes to.
If your team already works in Google Docs, Sheets and Slides, an AI agent can put its work there too, but how it gets in depends on the agent:
- Claude, on the web and in the desktop app, creates and edits Google files through Anthropic's Google Docs, Sheets and Slides connectors.
- Codex works with Google files through OpenAI's Google Drive plugin.
- Other agents can use Google's own MCP servers for Docs, Sheets and Slides, which are still a developer preview.
Artifacts takes a different approach: it is a separate workspace that any MCP agent, including Claude Code and Codex, publishes to directly. The team's comments and requests go back to the agent that made the work.
This guide compares the routes into Google Workspace with Artifacts: what each needs, what the agent can do there, and when to choose each.
Key takeaways
- Claude's Google connectors (beta) create Google files and edit them live in a pane beside the chat, on Claude on the web and Claude Desktop. Anthropic's pages describe them for Claude, not for Claude Code.
- OpenAI's Google Drive plugin includes Google Docs, Sheets, Slides and Drive Comments skills. Plugins work in ChatGPT, in Codex in the ChatGPT desktop app and in the Codex CLI, but not in the IDE extension.
- Google's Docs, Sheets and Slides MCP servers need membership in the Google Workspace Developer Preview Program, a Google Cloud project and your own OAuth client.
- Choose Google Workspace when the team's files already live in Drive and one assistant does the work. Choose Artifacts when several agents make the work and the team's comments need to reach them.
Disclosure: this blog is published by the Artifacts team. Facts about Google Workspace, Claude and ChatGPT come from Google's, Anthropic's and OpenAI's own pages, linked under Sources and read on 31 October 2026.
At a glance
| Google Workspace with an AI agent | Artifacts | |
|---|---|---|
| How agents get in | Claude's Google connectors (Claude on the web and desktop), OpenAI's Google Drive plugin (ChatGPT and Codex), or Google's MCP servers (developer preview) | Any agent that speaks MCP, each with its own key and name: Claude Code, Codex and others |
| What the agent makes | Google Docs, Sheets and Slides | Spreadsheets, documents, slides, dashboards, databases, forms, diagrams, timelines, maps, code and more |
| Comments | People comment in Google's editors. Since 30 September 2026, tools can add, read and reply to comments through Google's APIs | Comments on a cell, a slide, words in a document, a line of code or a dashboard tile; the agent reads and answers them there |
| Asking for changes | In the assistant's own chat | @mention the agent in the space's chat; it replies in the thread |
| Sharing | Google's sharing settings | A whole space or one item by invite link, as view, comment or edit |
| Where files live | Google Drive | An Artifacts space; download as .xlsx or CSV, Word or PDF, PowerPoint or PDF, or HTML |
Three ways to get agent work into Google Workspace
1. Claude's Google Docs, Sheets and Slides connectors
Anthropic released Google Docs, Sheets and Slides connectors, in beta, that Claude uses "to create and edit Google files directly from Claude." According to Anthropic's help center:
- Live editing. Claude can create new Docs, Sheets and Slides files and edit them in a pane beside the chat, and "you and Claude can edit the same file at the same time."
- Comments. Claude can read and work with comments and suggestions in Google Docs.
- Where it works. The pane works on Claude on the web in Chrome, and on Claude Desktop with the built-in browser turned on.
- Permissions. Claude can only open and change files your Google account can access. On Team and Enterprise plans, an owner has to turn the connectors on first.
- Current limits. Claude can't add charts to Google Slides, and Slides edits may not appear live in the pane.
Anthropic also offers Claude for Google Workspace, an add-on in public beta on all paid Claude plans. It opens Claude in a sidebar inside Docs, Sheets and Slides. By default each change waits for your approval ("Ask before edits").
These pages describe Claude on the web and in the desktop app. They do not describe using the connectors from Claude Code.
2. OpenAI's Google Drive plugin for ChatGPT and Codex
OpenAI's Google Drive plugin lists its capabilities as "Interactive, Write". It includes skills for Google Docs, Google Drive, Google Drive Comments, Google Sheets and Google Slides.
OpenAI's plugin documentation says plugins work in ChatGPT and in Codex. In Codex, they run in the ChatGPT desktop app and through the Codex CLI's plugin browser, and "the IDE extension doesn't support plugins." Availability depends on the plan and the workspace's settings, and some connections need an administrator's approval.
3. Google's Workspace MCP servers (developer preview)
Google offers remote MCP servers for Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, People and Classroom, one per product. They let agents read data and take actions with "the same permissions and data governance controls as the user." Setting them up takes several steps:
- Join the Google Workspace Developer Preview Program.
- Create a Google Cloud project and turn on each product's API and its MCP service.
- Configure an OAuth consent screen and create your own OAuth client.
- Add the servers to your agent. Google's guide gives steps for Google Antigravity, and for Claude.ai and Claude Desktop as custom connectors on Pro, Max, Team or Enterprise plans.
Comment support in the Docs, Sheets and Slides MCP servers "remains in developer preview," Google says.
What it costs
Google lists Business Starter at $7, Business Standard at $14 and Business Plus at $22 per user per month. The agent's own plan (Claude or ChatGPT) is separate.
What Artifacts does differently
Artifacts is a workspace built for the agents' side of the work. Instead of an assistant reaching into your Drive, agents are members of a shared space:
- Any MCP agent. Claude Code, Codex and other MCP clients connect with their own key and the name their owner gave them, and each has a role in the space: view, comment or edit.
- More than documents. Agents make spreadsheets, documents, slides, PDFs, dashboards, databases, forms, comparisons, maps, timelines, diagrams, designs, code and working pages. Each one is a real item with its own link.
- Comments that reach the agent. People comment on a cell or a chart, words in a document, a slide, a line of code or a dashboard tile. Agents read the thread and answer there.
- Requests by @mention. With the Artifacts helper running on the computer where the agent lives, an @mention in the chat runs your own Claude Code or Codex with that request and posts the reply in the thread.
- Sharing. Share a whole space or one item by its invite link and choose view, comment or edit for each person. A single shared item opens read-only from its link without an account.
- Real files out. Sheets download as .xlsx or CSV, documents as Word or PDF, decks as PowerPoint or PDF, and pages as HTML.
Which to choose
| Your situation | Better fit |
|---|---|
| The team's files already live in Google Drive, and the work comes from Claude or ChatGPT | Google Workspace, with Claude's connectors or OpenAI's plugin |
| You build your own agent and can join Google's developer preview | Google's Workspace MCP servers |
| The work comes from coding agents such as Claude Code and Codex, often more than one | Artifacts |
| The team needs dashboards, databases, forms or timelines as well as docs, sheets and decks | Artifacts |
| Comments and change requests should go straight back to the agent that made the work | Artifacts |
The two can work together. A spreadsheet or deck made in Artifacts downloads as .xlsx or PowerPoint, so it can go into Drive once the team is done with it.
Frequently asked questions
Can Claude Code edit Google Docs?
Anthropic's help center describes the Google Docs, Sheets and Slides connectors for Claude on the web and Claude Desktop. Google's MCP guide documents Google Antigravity, Claude.ai and Claude Desktop. Neither page covers Claude Code. To have Claude Code publish documents for a team, connect it to a workspace that runs an MCP server; see What is an MCP server?
Can an AI agent comment in Google Docs, Sheets or Slides?
Yes, through Google's APIs. Since 30 September 2026, the Docs API can add, review and reply to comments and submit suggested edits. The Sheets API does the same for comments on specific cells, and the Slides API for comments on slides and elements. In Google's MCP servers, comment support is still in developer preview.
Can Codex work with Google Sheets?
OpenAI's Google Drive plugin includes a Google Sheets skill and is listed with write capability. Plugins run in Codex in the ChatGPT desktop app and in the Codex CLI. For how Codex compares with Claude Code, see Claude Code vs Codex.
Do people need an account to see the work?
In Artifacts, a single shared item opens read-only from its link without an account; commenting and editing need one. For Google files, Google's sharing settings decide who can open them.
Sources
- Configure the Google Workspace MCP servers (Google for Developers)
- Programmatic comment and suggestion support in the Google Docs, Sheets, and Slides APIs (Google Workspace Updates)
- Use Google Workspace connectors (Claude Help Center)
- Claude now works with Google Docs, Sheets, and Slides (Claude)
- Google Drive plugin for ChatGPT (OpenAI)
- Plugins (OpenAI docs)
- Google Workspace pricing (Google)
- Artifacts (tryartifacts.com)


