Skip to main content
Glama
johnnyclem

hypervault-mcp

by johnnyclem

create_artifact_group

Bundle multiple web files into one runnable project, save it to HyperVault, and receive a URL that opens an integrated editor/preview with all files working together.

Instructions

Save a multi-file "artifact group" — several .html/.css/.js/.jsx files that run together as one project — to the user's HyperVault.

Unlike save_to_hypervault (a single file), a group bundles a whole little project: markup, styles, and script(s) as separate files that reference each other normally (e.g. <link href="style.css">, <script src="app.js">). It is always run/previewed as a container, similar to a JSFiddle: the returned URL opens a minimal editor/preview UI where the files render together, routed through the required root index.html.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags for organizing the vault (also power auto-connections between items sharing a tag).
filesYesThe group's files, e.g. [{"path": "index.html", "content": "<html>...</html>"}, {"path": "style.css", "content": "body { ... }"}, {"path": "app.js", "content": "console.log('hi')"}]. Rules (validated locally before any network call): - Must include exactly one root file at path "index.html" — the entry point the container routes through. A nested one like "public/index.html" does not count. - Paths must be relative, use '/' separators, contain no '..' segments, and only [A-Za-z0-9._/-] characters. - Extensions are limited to .html, .css, .js, .jsx. - At most 50 files; 256 KB per file; 1 MB total. - Paths must be unique (case-insensitively).
titleNoHuman-friendly title shown in the user's vault.Untitled
connect_toNoTitles or slugs of related artifacts/groups to link.
visibilityNo"private" (default) or "public".private
source_promptNoThe prompt that produced this group, if any — baked in the same way save_to_hypervault embeds it, so a later agent can read it back and iterate.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the multi-file bundle, always-run-as-container behavior, required root index.html, and the returned URL opening an editor/preview UI. It doesn't cover authentication or error/overwrite behavior, but the core behavioral contract for a create tool is well stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences that are front-loaded with the core action, then differentiate from a sibling, then clarify preview behavior. Every clause earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 6-parameter tool with no annotations, the description plus the detailed schema cover purpose, validation rules, file constraints, and returned URL behavior comprehensively. The presence of an output schema means return-value details need not be in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds semantic value by explaining how files reference each other and why index.html is required as the entry point, which goes beyond the raw schema. It doesn't enumerate each parameter, but the schema already does so thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Save a multi-file artifact group', clearly naming the verb and resource. It explicitly distinguishes this from save_to_hypervault (single file), making the tool's unique scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly contrasts with save_to_hypervault as the single-file alternative, and explains that a group is for a whole project bundle of files run together. This gives clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnnyclem/hypervault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server