Shareout

npx add-mcp 'https://shareout.io/mcp'

Your work.Beyond your workspace.

Publish a proposal, report or interactive prototype for clients and collaborators to open in their browser. Collect feedback and revise at the same link.

Choose your client Instructions for your agent

Connect your agent.

Choose the client you use. These are direct connection options; directory approval is separate.

Codex

Full installation guide

Add this to your Codex configuration, then authorize the connection.

[mcp_servers.shareout]
url = "https://shareout.io/mcp"

Run codex mcp login shareout, then sign in to Shareout and approve access.

1. Connect your account. Sign in to Shareout when your client asks. New accounts use email sign-in.
2. Give it a task. Ask your agent to publish a self-contained HTML file for the audience you choose.
3. Send the recipient link. Grant commenting access separately if you want feedback. Publishing from a hosted connection

Hosted MCP uses Streamable HTTP and OAuth with PKCE. Publishing needs a supported host-provided HTML attachment or direct HTTP file transfer. If your client cannot transfer a file, use the CLI or local MCP to publish; the hosted connection can still read feedback and manage documents.

Terminal and local MCP setup

Install the standalone CLI, then run shareout doctor --json. If credentials are missing, sign in to the console and choose Connect your agent. A connected CLI can serve local files through stdio MCP:

{
  "mcpServers": {
    "shareout": { "command": "shareout", "args": ["mcp"] }
  }
}

Use an absolute executable path if your app does not inherit PATH. Client configuration fields vary. Read the publishing workflow.

See package and marketplace status.

Is Shareout the right tool?

Use it when people outside your AI workspace need to view or review a self-contained HTML deliverable—even if they do not use AI. A private viewing link and commenting access are separate.

Keep local drafts local. Use application hosting for backends, submitted forms or live API integrations. Shareout pages cannot call external APIs, submit forms or embed other sites.

Try a shared page · Rendering rules

A starting point for the job.

If you have content but no design, ask your agent to start from the template library. A change proposal, report or presentation comes with a brief, visual style and working example to adapt. Keep your own facts and voice; example content is fictional.

Make a change proposal from my notes using a Shareout template. Include a working before-and-after prototype. Keep it local for review.

Browse templates · Template instructions for your agent

Free, with clear limits.

The current self-service offering is free and subject to quotas. Read current limits as JSON; authenticated requests return effective workspace limits. Service terms explain availability and future pricing.

Link expiry controls access. Document retention controls deletion. Set each for your task; an expired link does not delete the document.

New account? Start with an inbox.

Use your email or an inbox your agent is authorized to manage, including services such as AgentMail. Shareout sends a sign-in link. Open it in the browser that requested it.

After signing in, choose Connect your agent, or approve your host’s Shareout OAuth connection. A supplied setup link connects an existing account without an agent inbox. Account creation still requires email and browser verification; there is no anonymous signup.

Sign in and connect your agent

Know when the task is done.

Confirm publication and the active version, then return the recipient’s link. Keep that link when revising. If another revision has landed, inspect it before replacing anything. Named links help distinguish audiences; opening activity does not prove who read the page.

Files move directly from disk or through an upload URL. Their contents never belong in MCP arguments. Fetch only the instructions and template needed for the current task.

Agent quickstart · Publishing workflow · Reference index