Super Artifacts
Server Details
Super Artifacts lets AI agents create, host and share interactive artifacts: web pages, reports, forms and media galleries. Combine HTML, images, video and audio, collect responses, and collaborate at one link. Artifacts start private. Connect over OAuth; connecting publishes nothing. Home: https://superartifacts.app. Setup: https://superartifacts.app/docs. Pricing: https://superartifacts.app/pricing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 21 tools
The descriptions go to great lengths to distinguish adjacent tools, especially super_data vs super_data_query vs super_data_schema vs super_data_write vs super_entries, and super_templates vs super_template_action vs super_template_save vs super_release_template. A few family groups are inherently easy to mix up at first glance, but each tool has a clearly stated scope.
All tools share the `super_` prefix and snake_case, which keeps the set readable, but the convention mixes plural resource names, singular resource names, and verb-style names such as `super_publish`, `super_share`, and `super_upload`. The pattern is understandable rather than fully consistent.
At 21 tools the surface is large, but the server spans many distinct subdomains: artifacts, publishing, data, collections, templates, projects, sharing, signatures, webhooks, uploads, and identity. Most tools earn their place, though the count is slightly heavy relative to a typical focused MCP server.
The set covers the major lifecycle operations: publish versions, read and update artifacts, manage data and schemas, write entries, handle templates, projects, sharing, signatures, uploads, and webhooks. Minor gaps exist, such as no general way to remove existing shared access or delete templates, though some of these limitations appear intentional.
Publisher details
- Operator
- Super Artifacts · Publisher source
- Operator website
- https://superartifacts.app
- Vendor relationship
- First-party
- Documentation
- https://superartifacts.app/docs
- Privacy policy
- Not provided
- Trust center
- Unknown
- Restrictions
- Requires a Super Artifacts account and OAuth authorization. Usage and storage limits depend on your plan. · Publisher source
Available Tools
21 toolssuper_artifactsYour artifacts, their versions and filesARead-onlyInspect
Without artifact: your artifacts, newest first, with URLs and live. With artifact: its versions, which is published, their paths, and declaration (the published policy). Add path or version to read that file as text (default: published index.html); non-text or over 300,000 bytes: refused. open: true (with artifact, optional version) returns url and expiresAt: load url to see the artifact as a viewer, private included, for 10 minutes; visibility is unchanged, the URL opens only that artifact, 60/key/hour (rate_limited). Changing what an artifact serves, or who can open it, is super_artifact_set.
Inputs: open, path, version, artifact.
super_artifact_setChange what an artifact serves, and to whomADestructiveIdempotentInspect
Change one artifact. version serves an existing version (a pointer move; nothing rebuilt or deleted). live turns its live room on or off; off disconnects every visitor, and Free has one room at a time. triggersEnabled is the owner’s kill switch for declared triggers (default on). notifyOnSubmission emails you for each new data submission (default off; edits send nothing; no answers in the mail). phase sets the live room’s phase. visibility widens or narrows who can open it; narrowing voids every viewer grant already issued, so each viewer is checked again. collection sets its gallery grouping label. delete removes the artifact with every version, share link and response, permanently; it needs confirm: true and goes alone. Fields apply in that order, and a refusal part-way names the ones already applied. Publishing a new version is super_publish.
Inputs: artifact (required), live, phase, delete, +6 more.
super_commentsRead and answer the comments on an artifactBInspect
Threads: messages, anchor, viewed version (default status: "open"); status all includes resolved history. Publish the fix first, then respond with body explaining what changed and which version, plus resolve: true atomically. Reuse messageId on retry. Reports replied/resolved separately. resolve: false reopens. screenshot returns an image. Agents cannot open/delete threads. mentioned: true lists your @mentions, oldest unseen first, marking them seen.
Inputs: page, limit, react, cursor, +6 more.
super_dataRead what visitors submittedARead-onlyInspect
The rows visitors submitted to your artifacts, newest first, with each version's field schema; paged by cursor. Address exactly one: artifact; dataset (a catalog key; one shared by several artifacts is ambiguous_dataset); or collection, the gallery grouping label set at publish, not a content collection (≤20 artifacts over one window, kept per artifact, no filter). Entries of a content collection are super_entries; totals and averages are a query, not a read.
Inputs: sort, limit, since, until, +6 more.
super_data_queryAggregate what was collectedARead-onlyInspect
Numbers over what was collected, never rows (rows are super_data). Aggregate measures across the datasets in scope; datasets combine on the same measure in one base unit, results in the declared unit. Names come from the catalog; an unknown one errors with near misses. The answer has one row per group_by key (or one row) with a column per measure and compute, the datasets used and any skipped, and truncated when limit cut it. Or send distributions for one artifact: counts, per-version rates and per-field distributions (free text: answer rate and length only). A call with neither is invalid_query.
Inputs: agg, limit, scope, since, +6 more.
super_data_schemaWhat data exists, and what it meansADestructiveIdempotentInspect
The data catalog, without rows. Read (the default): datasets your artifacts declared, with fields, units, measures and since/deprecated versions, and this workspace's content collections, with fields, rules and entry counts. compare (alone): two to ten artifacts' newest fields side by side, every type, unit and measure conflict named. define creates a content collection, or replaces the one with that key outright, name, display field and every field; a field left out is gone from the model, and a collection an artifact declared is refused with conflict. Refusals name field, rule and fix. Rows an artifact collected are super_data.
Inputs: tags, since, define, series, +3 more.
super_data_writeWrite rows into your artifactADestructiveInspect
Write rows into an artifact this key may edit, through the validation and stream rules a page write gets; each row is attributed " (agent)". rows creates in stream. ops [{op: create|replace|delete, id, row, stream}] replaces or deletes only rows this agent wrote (writes: upsert); a deleted row cannot be restored by any tool. ≤50 a call; atomic: all or none, otherwise a partial batch answers complete: false. Visitor rows are never changed here; entries of a content collection are super_entries.
Inputs: artifact (required), ops, rows, atomic, +1 more.
super_entriesRead or write a collection's entriesAInspect
Entries of a workspace content collection (a model defined in the catalog), not rows an artifact collected. With values: create one entry (an object) or up to 50 (an array, one outcome per row); values are coerced to declared types, undeclared fields are refused by name, and nothing existing is updated or deleted. Without: read one page, filtered and sorted in the database; references resolve to labels, sensitive fields read as answered-or-not. Rows visitors submitted are super_data.
Inputs: collection (required), page, sort, limit, +6 more.
super_helpHow the tools fit togetherARead-onlyInspect
Plain-text notes for when it is unclear which tool, data store or argument shape does a job. Topics: tools (a line per tool), data (which store a page needs and how the page writes to it), templates (finding, building from, drafting, releasing), collections (content models and field types), projects (creating, ordering, sharing, rules), batch (what each tool takes in one call). Without topic: the full topic list, which names two more reached from results. Answers {topic, text}; not needed when a tool’s own description answers the question.
Inputs: topic.
super_projectCreate, read and edit projectsADestructiveIdempotentInspect
A project is an ordered set of your artifacts shown one at a time at /s/{slug}, with its own audience and share list. No project: title creates one (seeded from artifacts), else list yours. With project: add artifacts, remove one, title renames, set visibility, order/move reorder, a rule adds matches as they are published, or read it. delete with confirm: true removes the project, its order and its share list permanently; its artifacts stay. One change per call, or title with visibility. An artifact's gallery label is not a project: that is collection on super_artifact_set.
Inputs: move, rule, order, title, +9 more.
super_publishPublish an artifactAInspect
Publish a page at a stable URL; the same slug adds a new version, which the URL serves at once. Earlier versions stay and can be served again; nothing that existed before the call is deleted. Always give the person the url from the result, even on updates. Send html, or values for a template that carries a runtime, not both. Without policy a form, input or saved state stores nothing; CMS rows a page edits go in policy.collections. When retained storage is full it refuses with plan_limit and deletes nothing. A template becomes everybody’s through a release, not a publish.
Inputs: slug (required), html, kind, files, +14 more.
super_release_templateMake one version of your template everybody’sAInspect
Release one version of your template so others can build from it, live at once to the reach visibility sets; the result names its trust tier (Official, Verified or Community). Forward only (release_moves_backwards): earlier versions stay, and nothing is deleted. A private demo needs demoConsent: true. A runtime, prompt, parts or data change leaves a Verified badge behind. Public: account 7 days old (publisher_too_new), 10/day, 3/template/hour (rate_limited), 20 templates (too_many_templates), no tier words (reserved_wording), no credential (secret_in_template), paid plan (plan_required). Writing the draft is super_template_save.
Inputs: slug (required), version (required), visibility, demoConsent, +1 more.
super_secret_useCall an API with a stored secret you cannot readAInspect
Make one HTTPS request with a pii: secret value from a content collection entry. The platform puts the value into one header and calls the one host a person approved; you get status, headers and body, scrubbed of it. You never see it, in input or result; a response echoing it is withheld whole (secret_echoed). A first request for a field and host answers approval_required with approvalUrl: give the person that link, then repeat the request once they approve. Grants expire, cap uses and can be revoked; every use is logged. The person types the secret into its dashboard entry; super_entries writes one only if they insist on pasting it.
Inputs: url (required), entry (required), field (required), method (required), +4 more.
super_signaturesAsk people to sign an artifactAInspect
Ask named people to sign one published version of an artifact, and follow the request. request with artifact, signers [{name, email, party?}] (≤10) and an optional message (≤500 characters) emails each signer a private link; the version must be one file of at most 2 MiB, and it is kept while the request is open and for good once it completes. status with request (one) or artifact (all, newest first). withdraw closes an open request. remind emails signer the link again, three times at most, a day apart. Only each signer can sign, in a browser, after a code sent to their address: an agent cannot.
Inputs: action (required), signer, message, request, +3 more.
super_template_actionInstall, rate, report, roll back or verify a templateAInspect
Act on one template; nothing here deletes a template, a version or a built artifact. install/uninstall: this workspace's installed set (uninstall removes only the install; built artifacts keep working); install returns its build prompt as nextStep. rate: the person's 1–5 stars on an installed template not yours (cannot_rate_own, not_installed, rate_limited); counts once this workspace built from it. report: kind and a reason (≤1000 chars) for a moderator; one per account; enough reports hide it. rollback: restore version as a new version, unless the runtime changed. request_verification: a moderator checks your released version; 3 per 30 days. Finding and reading templates is super_templates.
Inputs: slug (required), action (required), kind, stars, +3 more.
super_templatesFind, list and read templatesARead-onlyInspect
With request: rank installed templates by content similarity; matches carry band (high: build from it; possible: judge it), why and unscored stats. scope: marketplace: released public templates, ranked by request or else the top by sort; sort, limit and the facets apply only here. Neither: the installed list. slug: one template in full, with its installPrompt; history: its changelog; feedback: its artifacts' comments as themes. mine: your published templates, with counts. Reading only: installing, rating and rolling back are super_template_action.
Inputs: cost, jobs, kind, mine, +13 more.
super_template_saveCreate or revise a template draftAInspect
Write a template draft only you can publish from. Without expectedVersion it creates (refused if the slug exists); with it, it revises the head (refused if the head moved past it), and a revision that changes nothing cuts no version. A json slot needs schema. Runtime files (≤512 KiB decoded) need a json slot and an index.html with one <script id="sa-template-values" type="application/json">. Others build from it only once super_release_template releases it; a revision never changes a released version.
Inputs: slug (required), spec (required), title (required), description (required), +16 more.
super_uploadStage files for a publishAInspect
Stage images, video or big files for a publish without sending their bytes in a call. Declare each file’s path and exact bytes; the result carries an uploadId and one url per file. PUT each file to its URL (curl -T, no credentials), then super_publish with uploads. Not index.html: that is html; small assets can ride inline as the publish’s files. Same limits as files; a staged set expires after 30 minutes, and at most 5 wait unpublished at once.
Inputs: files (required).
super_webhooksManage webhook endpointsADestructiveInspect
Manage this account’s webhook endpoints. create and rotate return the signing secret once; delete permanently removes an endpoint and its delivery history. Mutations require write scope. agent: "me" selects the calling key’s agent (no_agent if absent); a handle must be owned. messages returns the newest 100, optionally filtered by endpoint id and sinceMinutes (1–43200). Declare artifact triggers through super_publish.
Inputs: action (required), id, url, agent, +3 more.
super_whoamiWho am I publishing asARead-onlyInspect
Who this key publishes as: the workspace handle, email, agent name and scope (the artifacts it may change: its own, and those it is named Editor on), plus liveRooms where live rooms run (the limit and who holds one). Useful to confirm where a publish lands, or why an artifact answers not_found; no other tool needs it.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Save, version & share AI-generated HTML artifacts (canvases, dashboards, apps) as links.
Give your AI agent a “publish” button. Droply turns HTML pages, Markdown, PDFs, CSVs, images or a whole multi-file site into a live link like name.droply.page, in one tool call. Update a project later and the link stays the same, so anything already shared shows the new version. Agents can also list projects with view counts, set a password, or limit access to specific emails. OAuth sign-in, free plan that never expires; works in Claude, Cursor, Claude Code and any client that supports remote MCP.
Shared workspace for AI artifacts: your agents publish, search and cite each other's work.
Instant web publishing for AI agents. POST HTML, get a live URL. No account needed.
Related MCP Servers
- AlicenseAqualityBmaintenanceOne place for every AI agent's pages and docs. Publish HTML, build folders, ZIPs, PDFs and Office documents as sandboxed, versioned share links, then search, read and update them later from any MCP client. Sign in with Google or GitHub via OAuth. Open source and self-hostable: https://github.com/lexmount/artifact-site2628Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables sharing artifacts (HTML, files, sites) with password protection and custom branding on your own domain, directly from any AI agent.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to publish, retrieve, update, and delete hosted HTML, Markdown, Mermaid, and SVG artifacts and to create, list, or revoke shareable links through authenticated, scope-enforced tools. It exposes artifact hosting over Streamable HTTP so any MCP client can manage content on a self-hosted instance using a Bearer agent API key.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to publish HTML artifacts for human review, receive anchored feedback, and iterate until approval.2-
Glama MCP Gateway
Add one secure layer between your agents and this server.