Connect with OAuth

Connect Artifact Publisher from Claude’s directory or from a coding agent. Prefer OAuth (browser consent) whenever the client supports it. A scoped publisher API key is for advanced, headless, or always-on setups.

Endpoint: https://app.artifactpublisher.com/mcp (streamable HTTP, POST)

Artifact Publisher is listed as a Community connector in the Claude Connectors Directory:

claude.ai/directory/artifact-publisher

1. Open the listing (or find Artifact Publisher under Customize → Connectors → Discover / Suggested).
2. Choose Connect.
3. Complete consent on Artifact Publisher (sign in with GitHub or Google if asked).
4. In a chat, turn the connector on and approve the tool call when Claude asks.
5. Try one of the prompts below — Claude publishes HTML and returns a stable, unlisted link.

You do not need a publisher API key for the directory path. OAuth tokens stay in the client; never paste an access token into chat.

If Connect shows Request instead of Connect (on some organisation plans), an admin must approve the connector first — that is Claude’s side, not Artifact Publisher.

When the client supports browser consent, use OAuth first.

1. Register the same endpoint: https://app.artifactpublisher.com/mcp.
2. Start the client’s MCP / connector add flow for remote HTTP (or streamable HTTP).
3. Complete consent in the browser when prompted.
4. Confirm a tool call works (e.g. list_artifacts or the publish prompt below).

Exact UI labels differ by client. Same endpoint; same OAuth preference.

Use a scoped publisher key when the client cannot do browser consent — for example Hermes, OpenClaw, CI, or always-on agents.

1. Sign in at Your dashboard and mint a key (only a hash is stored).
2. Put the key in an environment variable (e.g. ARTIFACT_PUBLISHER_KEY). Never put it in a prompt, repo, or artifact.
3. Send Authorization: Bearer <key> on MCP requests.

Example shape (Claude Code with a key — prefer OAuth when your client offers consent):

claude mcp add --transport http artifact-publisher \
  https://app.artifactpublisher.com/mcp \
  --header "Authorization: Bearer <your-key>"

Rotate the key if it is ever exposed. Full tool list, scopes, and limits: MCP integration.

These match the Claude Directory listing. They work after Connect (OAuth) or with a keyed coding-agent setup.

1. Publish
   Make a one-page HTML summary of this conversation and publish it with Artifact Publisher. Give me the link.

2. List + feedback status
   List my Artifact Publisher artifacts and show which have unresolved comments.

3. Feedback → update → reply
   Read the feedback on my latest artifact, fix what reviewers asked for, publish the update to the same link and reply to each comment.

After a successful publish, Claude (or your agent) should give you an https://app.artifactpublisher.com/artifact/… link. Anyone with the link can open the page without an Artifact Publisher account. Links are not listed, searched, or indexed.

Most MCP “publish HTML” tools stop at a link. Artifact Publisher also lets the agent read comments back and reply:

Reviewers comment anonymously on the page or on a selected passage — no Artifact Publisher account required to leave feedback.

Demo (optional): see what a published page looks like:
https://app.artifactpublisher.com/artifact/LBBqGHv8r34LCUDJc0SnknXm

Works with any MCP client that can reach the endpoint with OAuth or a Bearer credential. Claude Code, Codex CLI, and Cursor are common examples — not an exclusive list.

• MCP integration — tools, scopes, access modes, limits
• Agent Skill — share-URL-first behaviour for agents
• FAQ
• Claude Directory listing: claude.ai/directory/artifact-publisher