How it works

blink artifacts is a remote MCP server plus a web app. Your agent talks to the server with tools; people use the web app to open, edit, comment and share. Both work on the same live artifact.

The MCP server

Every agent connects to https://artifact.blinkbrosai.com/mcp with a token in the Authorization: Bearer header. The server offers tools only: there are no prompts or resources to configure. When the agent connects, the server tells it to read a type's guide with get_skill before creating or editing anything, so it learns the rules for that type.

Artifacts and links

An artifact has a type, a title and a set of files. Its address is https://artifact.blinkbrosai.com/<id>, where the id is 26 characters long. The address never changes: when your agent republishes or edits, people who already have the link see the new content.

Files and revisions

Agents work with files. read_file and get_artifact read them, write_files writes or deletes several files at once, and edit_file applies exact find-and-replace edits that fail if a match is missing or ambiguous. Each change raises the artifact's revision number, rev.

People edit the same artifact in the browser at the same time. An agent can pass baseRev to write_files to make sure nobody changed the files since it last read them, and changes_since lists the paths that changed after a revision, with who changed them and whether it was an agent or a person.

Live editing

The live content of each artifact is kept in one place on the server and synced to every open browser, so cursors, edits and comments appear for everyone as they happen. Saved versions are taken automatically; see Versions.

A separate content origin

Artifact content runs on its own origin, separate from the app, inside a sandboxed frame with strict security headers. A page your agent wrote cannot read your app session or other artifacts. Artifact pages are also kept out of search engines.

Design systems

A design system artifact holds a brand's colors, fonts and text styles. New slides, design and dashboard artifacts get your default system automatically; get_skill tells the agent which one it is, or that it should ask you.