ArtifactDeploy

com.artifactdeployPublished by artifactdeploy.comOfficial publisherv1.7.0Updated Oct 27, 2026

Deploy what Claude builds to a live link: previews, who-opened-it links, stats, forms, domains.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCloud & Infrastructure

Overview

AI-generated overview

ArtifactDeploy publishes what an assistant builds to a live link, with previews, tracked who-opened-it links, stats, forms and domains.

What you can do
  • Publish built artifacts to a live hosted link
  • Create preview links and shareable links that record who opened them
  • View access statistics for published links
  • Collect responses through forms on published pages
  • Manage custom domains for deployments
When to use it
Useful when you want an assistant's generated pages or artifacts to be reachable on the web rather than staying local, and when you need to know who opened a shared link or gather responses through a form.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared, and no local package is installed.
Before you install
Publishing puts content on a public live link, and link tracking records who opens it, so avoid sharing sensitive material. Deployments, domains and forms change state on an external service; review what is published and who can access it.

Installation

In SourceWeft

  1. Open ArtifactDeploy 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.artifactdeploy%2Fartifactdeploy/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": {
    "artifactdeploy": {
      "type": "http",
      "url": "https://mcp.artifactdeploy.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.7.0LatestOct 15, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.