Short answerAdd Overto to Claude Code with one claude mcp add command and sign in. Then ask Claude Code to publish: it gets back a private link your team opens with Google sign-in, comments on and draws on. Paste the viewer’s Copy for agent command back into Claude Code and it publishes the next version.
Claude Code artifacts or Overto?
Claude Code has its own artifacts, and for many teams they’re the right tool. Here’s an honest split.
Use Claude Code artifacts when
- everyone who needs to see the page is in your Claude organization, or a public link is enough;
- one self-contained page fits the job (Anthropic’s limit is 16 MiB rendered, and relative links don’t resolve);
- you want what’s built in: live updates while the session runs, connector calls per viewer, and comments that Claude can answer from your session.
Use Overto when
- reviewers aren’t all on a Claude plan, or your team mixes Claude Code with Codex, Cursor or OpenCode;
- you need a multi-page static site, a Markdown doc, files or audio, not only a single page;
- you want reviewers to draw on the page, and the agent to read those drawings;
- you want a free workspace for a small team: 250 MB, up to 3 members and public share links.
Anthropic’s docs also list when artifacts are unavailable: they need Pro, Max, Team or Enterprise and a session signed in with a claude.ai account on the Anthropic API. Sessions that use an API key, a gateway token or cloud-provider credentials (Amazon Bedrock, Google Cloud, Microsoft Foundry) can’t publish them, and they are off by default with -p and in the Agent SDK. Overto is an ordinary remote MCP server with its own OAuth, so it doesn’t depend on how the session reaches the model.
For the full side-by-side, see Overto vs Claude Code artifacts.
Set up Overto in Claude Code
Add the Overto MCP server
Run this once in your terminal:
Terminal claude mcp add --transport http overto https://mcp.overto.work/mcpAdd
--scope userto make Overto available in every project, not just this one. Keep the URL unchanged; you choose the workspace when you sign in.Sign in and choose your workspace
In Claude Code, run
/mcp, choose overto and authenticate. Your browser opens Overto’s sign-in.Sign in with Google, choose a workspace, review the requested read, write or administration access and select Authorize. A connection stays signed in for up to seven days.
Check access
Ask Claude Code to call
overto_whoami. It reports the workspace you’re connected to, your upload limits and your usage. Before it makes anything visual, it reads your house style withoverto_design.Install the Overto skills (recommended)
Three small instruction files teach Claude Code the Overto workflows:
overtoworks on one artifact,overto-sharepublishes and revises, andoverto-findsearches and reviews discussions. They contain no credentials.Terminal for s in overto overto-share overto-find; do mkdir -p ~/.claude/skills/$s && curl -fsSL https://overto.work/skills/$s/SKILL.md -o ~/.claude/skills/$s/SKILL.md; doneRestart Claude Code. In the Overto viewer, Copy for agent copies
/overto <artifact-id>. Paste it into Claude Code.
Publish, review, revise
Publish
Ask in plain words, for example: “Publish the onboarding research in ./research as a site in the Launch project.” Claude Code calls overto_publish and returns the link and the version. Each file can be up to 25 MiB on Free, and larger on Enterprise. See publishing and versions.
Review
Teammates sign in with Google and comment on a sentence, a chart or any element of the page. With Annotate they can circle, highlight or draw arrows. Mentions bring others into the thread. See comments and review.
Revise
Choose Copy for agent in the viewer and paste /overto <artifact-id> into Claude Code. It reads the threads with overto_comment_list, drawings included as short text descriptions, publishes the next version on top of the one you reviewed, and replies in each thread. If someone published in the meantime, the update is refused instead of overwriting their work.
Keep your house style with design.md
Your workspace’s design guide, design.md, holds your colours, type, layout rules and voice. Claude Code reads it with overto_design before it makes anything visual, and so does every other connected agent, so a report from Claude Code and a prototype from Codex look like one team made them. See design.md and templates, or read the Overto skill itself.
Frequently asked questions
How is Overto different from Claude Code artifacts?
Claude Code artifacts are built into Claude Code and publish one self-contained page to claude.ai for people in your Claude organization or a public link. Overto is a separate workspace that any MCP agent publishes to: multi-page static sites, Markdown docs, files and audio, with comments, drawings and versions, and teammates who sign in with Google.
Do reviewers need a Claude account?
No. Reviewers sign in to your Overto workspace with Google. For Markdown documents and websites you can also turn on a public link that anyone can open without signing in.
Does Overto need my claude.ai login?
No. Overto is a remote MCP server with its own OAuth sign-in, so the connection doesn’t depend on how your Claude Code session reaches the model.
Can Claude Code publish a whole site, not just one page?
Yes. Claude Code can publish a static website with several pages and its assets in one call, and links between the pages work inside the Overto viewer.
Is Overto free?
The Free plan includes 250 MB of storage, up to 3 members and public share links, with no credit card. Pricing.
Does a comment start Claude Code?
No. A comment or a mention never starts an agent. When you want a revision, paste the viewer’s Copy for agent command into Claude Code yourself.
Third-party product facts on this page were last checked on 24 October 2026, against each vendor’s own documentation. Claude and Claude Code are trademarks of Anthropic. Overto is an independent product and is not affiliated with or endorsed by Anthropic.