MCP

Dropkiln exposes a streamable HTTP MCP endpoint at /mcp, bearer-authenticated. The natural loop: an agent generates an HTML or React artifact, publishes it, and replies with one link instead of pasting hundreds of lines into the chat.

Claude Code

claude mcp add --transport http artifacts https://artifacts.example.com/mcp \
  --header "Authorization: Bearer ${ARTIFACTS_API_KEY}" --scope user

Codex CLI

In ~/.codex/config.toml:

[mcp_servers.artifacts]
url = "https://artifacts.example.com/mcp"
bearer_token_env_var = "ARTIFACTS_API_KEY"

Tools

Tool	Args	Returns
`publish_artifact`	`content`, `type`, `slug?`, `title?`, `tags?`, `expiresAt?`, `visibility?`, `password?`	public URL
`update_artifact`	`slug`, `content`, `type`, …	public URL
`rename_artifact`	`slug`, `newSlug`	new URL
`disable_artifact` / `enable_artifact`	`slug`	confirmation
`set_artifact_expiry`	`slug`, `expiresAt` (ISO or `null`)	confirmation
`set_artifact_tags`	`slug`, `tags`	confirmation
`set_artifact_visibility`	`slug`, `visibility`, `password?`	confirmation
`list_artifacts`	`tag?`	JSON list
`delete_artifact`	`slug`	confirmation

Zip sites have no MCP tool (binary payload); use the CLI or the zip endpoint.

Scoping

The key’s scope gates the tools: read allows list_artifacts, publish allows the mutation tools, and delete_artifact needs full. Mint a publish key for a client that should publish but never delete.