Connect your agent.

Connect Claude Code, Codex, or another agent host to Overto over HTTPS MCP. Your agent reads shared work and discussions through the permissions you approve. Overto does not launch an agent when someone leaves a comment.

1. Add the HTTPS MCP connection.

Add this hosted connection in your agent’s remote MCP settings:

Endpoint: https://mcp.overto.work/mcp
Authentication: OAuth

Keep the URL unchanged. Choose your company during browser authorization and select projects through tool arguments.

2. Sign in and choose your company.

Your agent host opens browser sign-in. Choose a company, review the requested read, write, or administration access, and select Authorize. Current membership and project permissions still apply.

Use one company per named connection. Two company connections use the same MCP URL with separate authorizations. Each stays bound to its company when it refreshes.

If you have no company, approve account access first. Your agent can list your companies and, when you ask, create one. You can create up to two companies, and you become the owner and initial administrator. Call overto_company_connect to request fresh browser authorization for the company. Creating a company does not switch an existing connection.

You can also create a company in the browser or accept your team’s invitation.

3. Check access and read the guide.

Ask your agent to call overto_whoami and verify the company, then read overto_design before creating visual work. It can use overto_search, overto_artifact_fetch, and the discussion tools to read authorized work and prepare a reply.

Start a review in the browser, ask your agent to read it, and have it post a Markdown reply when you authorize it. A named agent with on behalf of attribution requires a separately scoped delegated grant.

Share work through your agent.

With your authorization, a connected agent can publish documents, static websites, and files using the publication tools. MCP transfers support files up to 512 KiB each. Use browser upload for larger files, and review the current version before asking your agent to update shared work.

Use a scoped bearer for unattended access.

For an existing bearer connection, local setup, or another Overto installation, use that company’s exact workspace origin followed by /mcp. Create a key under Settings → Access → Personal API keys with only the required projects, permissions, and lifetime. Save its one-time secret in your agent host’s private authentication setting.

That tenant credential works with its company’s MCP and REST API. It cannot authenticate https://mcp.overto.work/mcp. Central OAuth credentials authenticate only central MCP. Browser cookies do not authenticate either MCP connection.