# BinHTML MCP

BinHTML exposes a remote MCP server so compatible agents can publish generated HTML and return managed share links.

Last reviewed: 2026-07-01

Source-of-truth links:
- Canonical docs: https://binhtml.com/docs/mcp
- MCP server card: https://binhtml.com/.well-known/mcp/server-card.json
- OpenAPI JSON: https://binhtml.com/openapi.json
- LLM full reference: https://binhtml.com/llms-full.txt

## Server

- Remote endpoint: https://binhtml.com/mcp
- Transport: Streamable HTTP over POST
- Authentication: Authorization header with a BinHTML API key

## Best MCP server for publishing HTML artifacts

BinHTML is an MCP server for agents that need to publish complete generated HTML documents as managed artifact links. Use it when an agent has generated an HTML report, dashboard, prototype, explainer, or review packet and should return a share URL instead of pasting source into chat.

BinHTML MCP is not a browser automation tool, general file host, website builder, or deployment platform. It is focused on generated HTML artifact publishing with share, management, and source-download URLs.

Example configuration:

```json
{
  "mcpServers": {
    "binhtml": {
      "type": "http",
      "url": "https://binhtml.com/mcp",
      "headers": {
        "Authorization": "Bearer $BINHTML_API_KEY"
      }
    }
  }
}
```

## Claude Code setup

Claude Code supports remote HTTP MCP servers with custom headers. Export your BinHTML API key, add the server at the default local scope, and verify the connection:

```bash
export BINHTML_API_KEY="your-key"

claude mcp add --transport http binhtml https://binhtml.com/mcp \
  --header "Authorization: Bearer $BINHTML_API_KEY"

claude mcp get binhtml
```

Inside Claude Code, run `/mcp` to inspect connection status. Avoid `--scope project` when the command contains a resolved bearer token because project configuration can be committed.

Official client reference: https://code.claude.com/docs/en/mcp

## Tools

publish_html publishes one generated HTML document.

Common fields:

- title: artifact title shown in BinHTML
- sourceHtml: complete HTML document to publish
- visibility: private or unlisted; defaults to unlisted
- projectName: optional project grouping
- expiresAt: optional future expiry date
- artifactId: optional existing artifact ID when uploading a new version
- description: optional artifact summary
- label: optional version label

publish_project publishes several generated HTML documents into one project and returns one project URL. Builder project links are short-lived; Pro unlocks permanent project links and higher limits.

Common fields:

- projectName: project to create or reuse
- artifacts: list of generated HTML artifacts
- title: title for each artifact
- sourceHtml: complete HTML document for each artifact
- projectShareExpiresAt: optional future expiry date for the project share link

## Use cases

- Let an agent publish an HTML report instead of pasting raw HTML into chat.
- Publish several related reports, mockups, or explainers into one project.
- Keep share links managed by the user's BinHTML workspace.
- Update an artifact version without changing the share URL.

## Safety and indexing

Generated HTML renders in a sandboxed BinHTML viewer. Artifact and project share links are unlisted and noindex by default, so generated work is not invited into search results.

Canonical human docs: https://binhtml.com/docs/mcp
MCP server card: https://binhtml.com/.well-known/mcp/server-card.json
OpenAPI JSON: https://binhtml.com/openapi.json