Artifact Share

com.artifactsharePublished by artifactshare.comOfficial publisherv1.0.0Updated Oct 24, 2026

Share HTML and Markdown files from AI agents within your company, with versions and comments.

VerifiedStreamable HTTPWeb executableFiles & StorageCommunication & Collaboration

Overview

AI-generated overview

Artifact Share is a hosted service that lets an assistant publish HTML, Markdown, folders and static sites at stable URLs with versions and comments.

What you can do
  • Publish HTML, Markdown, folders and static sites at stable shareable URLs
  • Share work created by people, AI agents and automation
  • Apply access scopes such as private, workspace, project, explicit-viewer or link-based
  • Keep versions and collect comments on shared artifacts
When to use it
Useful when an assistant produces HTML or Markdown reports, docs or small static sites that colleagues inside a company need to view at a stable link, with versioning and feedback instead of pasting files into chat.
Requirements
A remote MCP endpoint at artifactshare.com reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared. The README notes the code is source-available and can be self-hosted under its license.
Before you install
Shared artifacts are published to a third-party hosted service, so check what content leaves your environment. Access can be link-based, which may expose material to anyone holding the link. Publishing creates or updates content on the service.

Installation

In SourceWeft

  1. Open Artifact Share in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.artifactshare%2Fartifactshare/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "artifact-share": {
      "type": "http",
      "url": "https://artifactshare.com/mcp"
    }
  }
}

README

Artifact Share

Artifact Share shares HTML, Markdown, folders, and static sites at stable URLs. It supports private, workspace, project, explicit-viewer, and link-based access for work created by people, AI agents, and automation.

Service: https://artifactshare.com

Source-available, not open source

This repository is source-available. You may study, modify, and self-host Artifact Share for your own organization, subject to the repository license. The license restricts offering Artifact Share as a directly competing hosted, managed, SaaS, or cloud service. It is not an OSI-approved open-source license.

The npm package through version 0.9.0 remains licensed under Apache-2.0. The repository and CLI from version 0.10.0 onward are covered by the source-available license. Version 0.10.0 was intentionally not published; version 0.10.1 is the first npm release under the new license.

Repository layout

  • apps/web/ — the React Router application and Cloudflare Workers
  • packages/cli/ — the source-available command-line client
  • docs/reference/ — current technical contracts and repository boundaries
  • docs/brand/ — Artifact Share brand assets and their usage terms
  • proposals/ — public, proposal-only contributions

Local development and validation

The authoritative setup and export boundary are documented in the source-available boundary. A public checkout requires no production credentials or private services.

sh
pnpm install --frozen-lockfilepnpm --filter @artifactshare/web exec playwright install --with-deps chromepnpm fixtures:buildpnpm db:apply:localpnpm validatepnpm test:runtime

Run the commands in that order. Local configuration uses fixtures and local service bindings; it does not provide a production deployment path.

For interactive development, pnpm dev prepares local certificates, variables, and D1 state before starting the application, sandbox, and image worker. See the local development harness. UI review captures are documented in the screen capture harness. Manual product diagnostics are documented in AI-search eligibility and performance trace automation.

The sandbox reporter is maintained in packages/viewer-kit/src/reporter/*.ts. After changing it, run pnpm --filter @artifactshare/viewer-kit generate:reporter. The generated file is deterministic, unformatted output and is excluded from repository formatting. The generator owns reporter.generated.ts, including its exact script body and CSP hash; include that file with source changes. Run node packages/viewer-kit/scripts/build-reporter.mjs --check to check for drift without writing files. This check also runs as part of root pnpm typecheck.

Development process

Artifact Share currently accepts proposal-only pull requests, not code pull requests. Contributors describe a real situation and desired change; maintainers then own the issue, specification, implementation, verification, and release. Read CONTRIBUTING.md before submitting a proposal.

Report vulnerabilities through the private process in SECURITY.md, never through a public issue or proposal.

License

The repository license is a lawyer-review draft with Japanese authoritative text and an English reference translation. See LICENSE. The npm package through version 0.9.0 remains under Apache-2.0; the repository and CLI from version 0.10.0 onward use the source-available license. Version 0.10.0 was intentionally not published; version 0.10.1 is the first npm release under the new license.

Local artifact execution uses versioned a-… and l-… hosts under *.usercontent.localhost on port 5174. pnpm dev:setup includes this certificate wildcard. The app and public link-viewer URLs are unchanged. All .localhost hosts are same-site, so use the cross-site browser release gate to verify cookie partitioning; local viewer checks alone are insufficient.

Source: README.md at commit fe068fe

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 26, 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 listed15 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.