MCP INTEGRATION
Upload HTML through MCP.
Configure a separate MCP credential to upload and replace projects from your AI client.
Local file uploads · Recommended
- Create a separate credential in MCP connections. Reading and uploading are enabled by default.
- Download the local adapter, and extract it to a stable directory. Requires Python 3.12+ with no additional dependencies.
- Configure a stdio MCP server in your AI client and specify the directories it may read.
{
"mcpServers": {
"6hl": {
"command": "python3",
"args": ["/absolute/path/6hl-mcp/sixhl_mcp.py"],
"env": {
"SIXHL_URL": "https://6hl.dad",
"SIXHL_TOKEN": "Your separate MCP credential",
"SIXHL_ALLOWED_DIRS": "/absolute/path/to/your/works"
}
}
}
}Configuration varies between clients. Store the credential in private local configuration or a system credential store, never inside a project file.
For uploads, provide the file path, project name and idempotency key. For updates, also provide the project ID and current revision. Files must be within an explicitly allowed directory.
Remote MCP
https://6hl.dad/mcp
For clients that can send Authorization: Bearer <MCP credential> headers. Uses Streamable HTTP with JSON responses and protocol versions 2025-11-25, 2025-06-18 and 2025-03-26. There is no browser OAuth flow for MCP connections. Google tokens and visitor codes cannot be used as MCP credentials.
Remote tools accept HTML strings up to 1 MB. The local adapter supports HTML or ZIP uploads up to 50 MB. The server cannot read paths on your computer.
Available tools
get_spacelist_worksupload_workupdate_workget_upload_statuslist_grantscreate_grantrevoke_grantSharing tools require the separate Manage access grants permission. New uploads are private and are not automatically added to grants. Use the same idempotency key when retrying an operation.