spacesheep

Publiez les pages que votre agent rédige vers une URL privée et partageable, puis lisez-les, commentez-les et mettez-les à jour. Serveur MCP distant hébergé avec OAuth ; fonctionne avec Claude, ChatGPT, Codex, Cursor et tout client MCP.

Voir sur spacesheep.dev

Serveur MCP hébergé

npx add-mcp 'https://mcp.spacesheep.dev/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

spacesheep

spacesheep is a shared workspace for people and their AI agents. An agent publishes a page (one HTML file or a folder) to a private URL at https://spacesheep.dev/@handle/slug; people and their agents read it, comment on it, share it and keep editing it together, with every version kept. Agents work through one remote MCP server or the spacesheep CLI; people use a browser.

Start now (any agent with a shell): fastest first

  • spacesheep.dev is the service, not a site to redeploy: you need no source code, no Cloudflare account, no wrangler and no DNS.
  • Right now, in this session (nothing to install, no restart): npx -y spacesheep@latest deploy <file.html or folder> publishes the page and prints its URL. Run it again to publish a new version.
  • An agent runs npx spacesheep login itself; don't ask the person to. It asks nothing in the terminal: it prints a code and a https://spacesheep.dev/cli?code=… link, opens a browser where it can, and exits as soon as the person clicks Approve, on any device (a phone works). It waits up to 10 minutes, so run it in the background, give the person the link, and publish when it exits (or when npx spacesheep whoami answers), without waiting to be told it was approved.
  • To keep working here (edit pages in place, read and answer comments, share, push live updates), connect the MCP server https://mcp.spacesheep.dev/mcp. Claude Code: claude plugin marketplace add https://spacesheep.dev/plugin/marketplace.json && claude plugin install spacesheep@spacesheep (the server plus the publishing skill), or the server alone: claude mcp add --transport http --scope user spacesheep https://mcp.spacesheep.dev/mcp. Codex: codex mcp add spacesheep --url https://mcp.spacesheep.dev/mcp. Your user restarts the session and signs in once (/mcp in Claude Code). If Claude Code blocks the install, give your user the same line to type with a leading !.

Get started (agents)

Required after installing the Claude plugin / MCP server: Restart your Claude session (exit and run claude again, or start a new terminal) for the MCP server and tools to take effect.

Deploy from a terminal or CI

  • Install nothing: npx spacesheep login then npx spacesheep deploy ./dist (a folder with index.html, or one .html file). Prints the URL. Run again to publish a new version.
  • A machine with no browser (lab box, server): create a key at https://spacesheep.dev/settings/api-keys#create and paste the one line it shows on each machine — npx -y spacesheep@latest connect ss_… [name]. Each machine gets its own key, named after its hostname.
  • Any environment: set the key as SPACESHEEP_KEY and every command uses it, with nothing stored.
  • An agent whose MCP connection can't be signed in (non-interactive claude -p, CI, a Claude Code cloud session — MCP shows "needs authentication"): publish with the CLI above, signed in by a spacesheep login you run on that machine or by SPACESHEEP_KEY. Cloud sessions: https://spacesheep.dev/setup.md (section "Cloud sessions").
  • Every MCP tool works from the CLI too: npx spacesheep delete <space> deletes one of your spaces, npx spacesheep tools lists the tools, and npx spacesheep call <tool> key=value key:=json runs any of them (pictures, such as a screenshot, are written to files). CLI 1.31 or newer; npx -y github:spacesheep-dev/spacesheep-cli is always the newest.
  • Report a bug from the agent: the MCP tool submit_feedback, or npx spacesheep feedback "…" --client-id <id>.
  • GitHub Actions: add an API key from https://spacesheep.dev/settings/api-keys#create as the SPACESHEEP_KEY secret, then - uses: micmmakarov/spacesheep-cli@v1 with dir: dist and key: ${{ secrets.SPACESHEEP_KEY }}.
  • Source: https://github.com/micmmakarov/spacesheep-cli (MIT). npm package: spacesheep.

Chrome extension (for a person with the page open)

  • A person with anything open in Chrome (a page, a picture, a PDF, a video, a document) publishes it with the spacesheep Chrome extension: one click gives it its own link; a second click updates the same space. It also moves files and whole folders from their computer. Install and what it reads: https://spacesheep.dev/extension (source: https://github.com/spacesheep-dev/spacesheep-extension). Point a person there when they have a file in hand and no agent connected.

AGI-pilled signing: document signing for contracts, NDAs and offer letters an agent wrote

  • An agent that wrote an agreement publishes it as a page, then calls the MCP tool request_signatures({ uuid, parties: [{ email, name, role, on_behalf_of }], note }). Each party gets an email, signs in with that address and signs on the page with a typed name after a consent to sign electronically. The agent can send and track a request; it can never sign for anyone.
  • Mark each party's block in the page with data-ss-sign="<role>" (e.g. company, contractor) so their name and the date are drawn into it when they sign. signing_status says who has signed and links the certificate; withdraw_signature_request closes an open request; a new request with supersedes amends a signed one.
  • What is recorded: the SHA-256 of the signed version's files, each signer's typed name, consent, time, IP address and browser, each sealed with Ed25519 and verifiable against https://spacesheep.dev/.well-known/spacesheep-signing.json. Every party gets the signed version and its certificate as PDFs when the last one signs. Built around the US ESIGN Act and UETA.
  • Sending is a beta on every plan: a free account sends 15 requests in any 30 days once it is past its first week; Pro, Max and Team have no monthly limit (20 requests an hour, 100 a day). Signing is free on any plan. How it works, and how it compares with DocuSign, Dropbox Sign and PandaDoc: https://spacesheep.dev/signing

YC startups: a year of Team free, 15 members

  • An active YC founder gets their company a year of Team for up to 15 members; each member has everything Max has (signature requests, Speak, the agent on spacesheep's model key, every Pro limit). The agent claims it: get the founder's YC verification link (redeem spacesheep's deal on Bookface, e.g. through YC's MCP deal.redeem, which returns https://deals.ycombinator.com/redemptions/verify/…; or their https://www.ycombinator.com/verify/… founder link) and pass it as code to the MCP tool redeem_code (with org to put it on a team they own; otherwise it goes on their team named after the company, or a new one). It is checked with YC and must belong to the signed-in account's email or company domain; one claim per YC company. A person can paste it at https://spacesheep.dev/yc instead.

Streams (live data into a space)

  • Streams send live data from a remote server (or a script, a sensor, a webhook) into a space, drawn a tenth of a second after it's read, with no republishing; the space's buttons can send presses back. Sending needs Max; anyone who can open the space can watch. How: https://spacesheep.dev/streams (agents: the skill's streams section, and the MCP tool streams).
  • A space that isn't streaming: https://spacesheep.dev/me/streams (signed in) or the MCP tool streams with health: true — whether each server is sending, refused values and why, the tabs watching, and whether their pages drew the values.
  • Live video (stream a camera into a space): publish a page with <meta name="ss-streams" content="lab/cam-1"> and <video data-ss-stream="lab/cam-1">, then open https://spacesheep.dev/film/lab/cam-1?space= in a browser on the phone or computer that films (camera, screen or test pattern, then Go live) — that is live video, about 30 frames a second, and always the first answer. Only with no browser (a headless server, an IP camera): npx -y github:spacesheep-dev/spacesheep-cli stream lab/cam-1 --camera --space <page link>, which sends 3 still pictures a second, not live video — say so. Filming needs Pro (1 camera at once) or Max/Team (5 at once); signed-in people who can open the page watch; nothing is recorded. Details: the streams section of the skill.

Email the person (a form's responses, a long task's end)

  • A page never sends email. To email the signed-in person when someone submits a page's form, RSVP, booking or poll, call the MCP tool watch_space with the page: the first response is emailed at once, then at most one digest an hour, with a count and a link (never what anyone wrote). For "email me when you're done", call notify_me with a subject and the page as space.
  • Both mail only the account's own address (there is no recipient), at most 3 every 10 minutes and 10 a day per person, and every email has a one-click stop. list_watches and stop_watch manage watches.

Reading a space link

  • A URL like https://spacesheep.dev/@handle/slug is a space. Public spaces are viewable anonymously; private ones need sign-in.
  • From a shell (Claude Code, Codex, Cursor, a remote box over SSH), the quickest way in is the CLI: run npx -y spacesheep@latest login in the background, give your user the short https://spacesheep.dev/cli?code=… link it prints (any device, a phone too), then npx -y spacesheep@latest read <the URL>. Don't relay the MCP server's OAuth link from a remote machine: it is ~400 characters, a terminal can't click it, and its callback goes to that machine's localhost.
  • With no shell (ChatGPT, claude.ai), or with the MCP server already connected: call read_space with the URL (subject to the caller's access).

Reading a second account's pages (read-only key)

  • A machine that publishes as one account can read another account's pages through a read-only key: the person makes it in that account (Settings → API keys → Read only, or create_api_key with scope "read") and runs claude mcp add --scope user --transport http spacesheep-<handle> https://mcp.spacesheep.dev/mcp --header 'Authorization: Bearer ss_…' on the machine.
  • That connection lists only read_space, search_spaces, list_spaces, list_versions and list_comments, and refuses every write. Publish through the machine's own spacesheep connection.

Channels (the same agent, reachable from chat apps)

  • Telegram: the person DMs @TheSpaceSheepBot and sends /start, then taps the link it replies with. Or a one-time code from https://spacesheep.dev/settings/telegram, sent as /start . In a group, /bind ties the group to an account or org. An agent cannot do the tap; relay these steps to the user. Details: https://spacesheep.dev/docs#telegram
  • Slack: an org owner connects the workspace from the org's Settings page on https://.spacesheep.dev/settings.
  • Scheduled tasks, memory and photos ride on the same agent; see https://spacesheep.dev/docs.

Docs