artifacts.boo

boo.artifactsPublished by artifacts.booOfficial publisherv1.0.0Updated Nov 2, 2026

Agents publish interactive pages people comment on, approve and fill in; agents read the answers.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant publish small interactive pages in a team workspace, where invited people comment, approve and fill in answers the agent can read back.

What you can do
  • Publish interactive artifacts such as reports, dashboards, polls, checklists and mini apps into a workspace
  • Edit existing artifacts through patches rather than full rewrites
  • Read viewer responses, approvals and anchored comments left on an artifact
  • Use per-viewer browser storage and live shared state inside the published pages
  • Fetch guidance on how the workspace and artifacts work before creating content
When to use it
Useful when an assistant needs to hand a result to people rather than just print it: a decision to approve, a poll or checklist to fill in, or a small dashboard that specific colleagues open after verifying their email.
Requirements
A hosted workspace at its own subdomain, with its own MCP address taken from the workspace settings. Connection uses OAuth or a personal agent token from those settings, and the agent acts as that member. No local install or deployment is needed.
Before you install
The agent acts as a workspace member, so anything it publishes or edits is attributed to that member; treat the agent token as a credential. Published artifacts are shared with people on the artifact's share list, so check who can see them before publishing. Free workspaces are limited in artifact and member counts and cannot enable public links during their first day.

Installation

In SourceWeft

  1. Open artifacts.boo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

artifacts.boo

Agents publish small interactive pages (reports, dashboards, polls, checklists, mini apps) that specific people can open after verifying their email. Artifacts get per-viewer browser storage, live shared state and anchored comments. Each team gets a workspace at its own subdomain with its own Durable Object database, all on one Cloudflare Worker.

Try the hosted service

  1. Create a Free workspace with no card required. Free includes 20 artifacts and 3 members; guests are free. See pricing for all limits and the Team plan.
  2. Open your workspace's Settings for the connection steps for your MCP-capable agent. Each workspace has its own MCP address.
  3. Ask your agent to call artifact_guide, then create a private project update with a decision to review.

You do not need to deploy the app to use the hosted service. Help covers setup and feedback. New Free workspaces cannot turn on public links during their first day; start with a private artifact.

  • Agents connect to a workspace's MCP server at https://<slug>.<domain>/mcp, with OAuth or a personal agent token from the workspace's settings, and act as that member. Call artifact_guide first. Edits are patches (artifact_edit, artifact_patch_data), never full rewrites.
  • Viewers open /a/<id> in the workspace. They sign in once on the apex with an emailed code; the workspace then checks the artifact's share list.
  • Isolation: artifacts render in a sandboxed, opaque-origin frame with no network access. Storage and sync reach the frame only through the shell's postMessage bridge.

See docs/DESIGN.md for what it's for and the decisions behind it, and docs/DEPLOY.md to deploy and operate it.

Develop

sh
bun installbun run test        # unit testsbun run typecheckbun run build       # kit + workerbun run deploy      # alchemy deploy (reads .env)bun run e2e         # live end-to-end check in a throwaway workspacebun scripts/seed-demo.ts   # publish demo/ to the public demo workspacebun scripts/icons.ts       # re-render the PNG icons from their SVGs

The splash page's examples live in demo/: each folder is an artifact, and demo/examples.ts lists them with the votes and comments they start with.

License

FSL-1.1-ALv2: the source is available, and you may run, change and self-host it for your own team or organization, including for clients you do professional work for. You may not offer it to others as a competing hosted product. Each release becomes Apache 2.0 two years after it's published.

Source: README.md at commit 86445a6

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Artifacts integrations