Share Artifacts MCP server
online · 100% uptimeio.github.arunai30/share-artifacts·v0.3.0Publish and update safe static HTML reports, presentations, and explainers with controlled sharing.
0 stars
Reviews
Write oneNobody has reviewed Share Artifacts yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Share Artifacts tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 134ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Share Artifacts compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 324 ms
- faster than 45% of 30,031 servers
Install Share Artifacts in Claude Code, Cursor or VS Code
claude mcp add --transport http share-artifacts https://shareartifacts.dev/api/mcp
What the publisher says
From the Share Artifacts repository's README, as published. We do not edit it. Read it on GitHub
share/artifacts MCP server
Publish agent-created HTML artifacts and receive a shareable URL. The npm package remains @aiformasses/mcp-server for compatibility.
Preferred: connect your agent
Give your agent the public setup page. Agents supporting remote MCP, browser authorization, and CIMD or DCR can configure the hosted connection at https://shareartifacts.dev/api/mcp without installing this package or creating a permanent token.
Cursor: hosted OAuth connection
This repository includes a Cursor plugin at .cursor-plugin/plugin.json. Its mcp.json connects directly to the hosted service; no npm install or personal access token is required. Each user signs in to their own share/artifacts account and approves access in the browser.
For manual setup, merge this configuration into your project's .cursor/mcp.json (preserve any other servers):
{
"mcpServers": {
"share-artifacts": {
"url": "https://shareartifacts.dev/api/mcp",
"auth": {
"CLIENT_ID": "53f91130-7752-4e99-9667-7a6dffdab529",
"scopes": [
"pages:read",
"pages:write",
"styles:read",
"styles:write",
"offline_access"
]
}
}
}
}The client ID is public and grants no account access by itself. Do not add a client secret. When connecting, the consent page identifies the pre-registered Cursor configuration and warns that the requesting local app is not verified. Approve only a connection you just started. The desktop callback is exactly http://localhost:8787/callback; the registered web callback is https://www.cursor.com/agents/mcp/oauth/callback.
With Cursor CLI installed, run from the configured project:
agent mcp enable share-artifacts
agent mcp login share-artifacts
agent mcp list-tools share-artifactsComplete browser sign-in and consent when prompted. If you cancel, run login again when ready. Ask the agent to publish an HTML artifact, inspect the returned URL, and specify public sharing explicitly if you want anyone with the link to open it. Publishing defaults to private. A free account includes five successful publishes or updates in total.
Verified on September 17, 2026 with Cursor CLI 2026.09.15-d2fe57e: production OAuth sign-in, consent, and authenticated discovery of all 15 hosted tools. The maintainer also confirmed the local plugin works in Cursor CLI. For a plugin connection that needs authentication, enter /mcp list inside the interactive CLI, select Share Artifacts, and choose Login in its detail view. Complete browser consent, then return to the agent. The desktop editor and Cursor web agent have not been independently verified.
Personal-token fallback
Use this package when your MCP client does not support the hosted OAuth flow. It requires Node.js 20.19 or newer and npx:
node --version
npx --versionUse Connect a background agent in token settings. Create a personal access token and insert it directly into the local configuration. share/artifacts cannot display the token again.
Codex
Add the server to ~/.codex/config.toml, then restart only the share-html MCP entry from Codex settings. The first start downloads the pinned package through npx. The share-html entry name is a stable compatibility identifier; it does not change the share/artifacts product name.
[mcp_servers."share-html"]
command = "npx"
args = ["-y", "@aiformasses/mcp-server@0.2.0"]
[mcp_servers."share-html".env]
SHARE_HTML_API_BASE_URL = "https://shareartifacts.dev/api/v1"
SHARE_HTML_API_TOKEN = "PASTE_TOKEN_HERE"Standard MCP JSON
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Share Artifacts: common questions
- Is Share Artifacts MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Share Artifacts safety report
- How do I install Share Artifacts?
- It runs remotely at shareartifacts.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Share Artifacts need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Share Artifacts maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.3.0.
- Is Share Artifacts up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Share Artifacts compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 324 ms (faster than 45% of 30,031 servers). Full comparison.