Artifact Share

Official registry Productivity

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http artifact-share 'https://artifactshare.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "artifact-share": {
            "type": "http",
            "url": "https://artifactshare.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Artifact Share
  2. Source-available, not open source
  3. Repository layout
  4. Local development and validation
  5. Development process
  6. License

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.

pnpm install --frozen-lockfile
pnpm --filter @artifactshare/web exec playwright install --with-deps chrome
pnpm fixtures:build
pnpm db:apply:local
pnpm validate
pnpm 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.

Frequently asked questions

What is Artifact Share?

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

How do I install Artifact Share?

It runs as a remote server. In Claude Code: claude mcp add --transport http artifact-share 'https://artifactshare.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Artifact Share need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Artifact Share open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Artifact Share?

It is published by artifactshare. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.