blink artifact

com.blinkbrosaiPublished by blinkbrosai.comOfficial publisherv1.0.0Updated Oct 29, 2026

Publish HTML, docs, slides and dashboards from your AI CLI; edit them live with people.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an AI assistant publish HTML pages, docs, slides and dashboards, then edit them live with other people.

What you can do
  • Publish HTML, documents, slide decks and dashboards from an AI CLI session.
  • Share the published artifacts and edit them live alongside collaborators.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when you want an assistant to turn its output into a shareable web artifact — a page, doc, deck or dashboard — and keep working on it with other people, rather than leaving results in the chat.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An OAuth-based API token is required, sent in the Authorization header and created in the provider's web app.
Before you install
The server holds an API token in the Authorization header, so treat it as a secret. Publishing and live collaborative editing push content to a third-party hosted service, so anything you publish leaves your machine and may be visible to collaborators.

Installation

In SourceWeft

  1. Open blink artifact in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.blinkbrosai%2Fartifact/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "blink-artifact": {
      "type": "http",
      "url": "https://artifact.blinkbrosai.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Blinkbrosai integrations

blink artifact (no account)

com.blinkbrosaiOfficial publisher

blink artifact (no account)'s hosted MCP server, published by blinkbrosai.com; no sign-in required; Streamable HTTP; 2 tools.

Streamable HTTPWeb executable
2 toolsOct 29, 2026