Overto for Cursor

Share what Cursor builds, beyond your Cursor team

Cursor’s agent writes reports, dashboards and prototypes. Connect Overto over MCP and Cursor publishes them to one link that reviewers open with Google sign-in, comment on and draw on. Cursor reads the feedback and ships v2.

Free plan: 250 MB, up to 3 members, public share links. No credit card.

Short answerCursor’s shared canvases give your Cursor teammates a read-only snapshot. When the page needs reviewers outside that team, comments on the page or a public link, add Overto to ~/.cursor/mcp.json and ask Cursor to publish the work as HTML or a static site.

What Cursor’s shared canvases do today

Cursor calls canvases “interactive artifacts created by agents, like reports, dashboards, and custom interfaces”. According to Cursor’s docs:

  • a shared canvas is a live snapshot that opens in the browser with read-only access;
  • only members of your Cursor team can open the link, so you need to be on a team;
  • sharing needs a paid plan; free accounts can’t create shares, and team admins can turn sharing off.

That works well inside one Cursor team. It doesn’t cover a client, a designer on another tool, or a stakeholder who wants to point at a chart and say what’s wrong.

What Overto adds

  • Reviewers beyond Cursor. Anyone you invite signs in to your workspace with Google; Markdown docs and websites can also get a public link.
  • Comments and drawings on the page. Reviewers comment on a sentence or an element and draw on HTML pages. Cursor reads both over MCP.
  • Versions. Every publish is a new version; the link opens the latest, and older ones stay in history with rollback.
  • One place for every agent. Claude Code, Codex and OpenCode publish to the same projects, and overto_search finds any of it later.

Overto publishes files: HTML pages, static websites, Markdown docs, other files and audio. To move a canvas over, ask Cursor to build the same view as an HTML page and publish that.

Connect Cursor to Overto

  1. Add the Overto MCP server

    Add Overto to ~/.cursor/mcp.json (create the file if it doesn’t exist):

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "overto": {
          "url": "https://mcp.overto.work/mcp"
        }
      }
    }

    Use .cursor/mcp.json in a project root instead to add Overto to that project only. Keep the URL unchanged; you choose the workspace when you sign in.

  2. Sign in and choose your workspace

    Cursor handles OAuth for remote MCP servers: complete the browser sign-in when it opens. Customize in the sidebar lists the server and lets you turn it on or off.

    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.

  3. Check access

    Ask Cursor 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 with overto_design.

  4. Install the Overto skills (recommended)

    Three small instruction files teach Cursor the Overto workflows: overto works on one artifact, overto-share publishes and revises, and overto-find searches and reviews discussions. They contain no credentials.

    Terminal
    for s in overto overto-share overto-find; do mkdir -p ~/.cursor/skills/$s && curl -fsSL https://overto.work/skills/$s/SKILL.md -o ~/.cursor/skills/$s/SKILL.md; done

    Restart Cursor. In the Overto viewer, Copy for agent copies /overto <artifact-id>. Paste it into Cursor’s Agent chat, or type / and pick overto.

Publish, review and revise from Cursor

Ask Cursor’s agent, for example: “Build the weekly metrics dashboard as a static HTML page and publish it to Overto in the Ops project.” It calls overto_publish and returns the link and the version. Each file can be up to 25 MiB on Free, and larger on Enterprise.

When the comments are in, choose Copy for agent in the viewer and paste it into Cursor’s Agent chat. Cursor reads the threads with overto_comment_list, publishes the next version on top of the one you reviewed and replies in each thread. See publishing and comments and review.

For a wider view, see how each AI tool shares what it makes.

Sources: Cursor, Canvas, Shared canvases changelog, MCP and Agent Skills.

Frequently asked questions

Can I share a Cursor canvas outside my team?

Not with Cursor’s own sharing. Cursor documents shared canvases as a read-only link that only members of your Cursor team can open, on paid plans. To share with people outside it, ask Cursor to build the page as HTML and publish it to Overto, where you invite them to your workspace or turn on a public link.

Do reviewers need a Cursor 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.

Can reviewers comment on what Cursor made?

Yes. In Overto, reviewers comment on a sentence or on any element of an HTML page, and can draw on it. Cursor reads those comments and drawings over MCP when you hand it the discussion.

Does it work with Cursor’s CLI and Cloud Agents?

Overto is a standard remote MCP server, so it works wherever Cursor loads your MCP configuration. Cursor notes that Cloud Agents keep their own MCP sign-ins, separate from the ones on your machine.

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 Cursor?

No. A comment or a mention never starts an agent. When you want a revision, you hand the discussion to Cursor yourself with the viewer’s Copy for agent command.

Third-party product facts on this page were last checked on 24 October 2026, against each vendor’s own documentation. Cursor is a trademark of Anysphere, Inc. Overto is an independent product and is not affiliated with or endorsed by Anysphere.