Html2MP4 MCP
Remote Streamable HTTP MCP for agents. Discover this page from the homepage nav/footer or html2mp4.com/#mcp, then follow the install steps below.
For agents (read this first)
- Open https://html2mp4.com/mcp (linked from the homepage as MCP).
- If not signed in, open https://html2mp4.com/sign-in?next=%2Fmcp and complete login, then return to https://html2mp4.com/mcp.
- With the session cookie, POST https://html2mp4.com/api/account/api-keys with JSON {"name":"MCP key"} (or {}). Save response.secret.
- Configure the MCP client with url=https://html2mp4.com/api/mcp and Authorization: Bearer <secret>.
- Call html2mp4_get_credits to verify the connection.
Machine-readable install metadata: GET /api/mcp/install · GET /mcp/server-card · homepage index /llms.txt.
Endpoint
https://html2mp4.com/api/mcpAuth header: Authorization: Bearer <api_key> (keys start with h2m_).
Install for your agent
- Sign in so the agent can mint an API key with your session cookie (avoids manual key copy when the agent drives the browser).
- Return here, then create a key (button or
POST /api/account/api-keyswith session cookies). - Connect MCP:
https://html2mp4.com/api/mcp+Authorization: Bearer <key>.
Agent tip: after login, POST /api/account/api-keys {} with credentials included; read secret from the JSON response.
Client configs
Replace YOUR_API_KEY after creating a key. Workbuddy: use type "http" if streamableHttp is rejected.
Codex CLI
export HTML2MP4_API_KEY="YOUR_API_KEY"
codex mcp add html2mp4 --url https://html2mp4.com/api/mcp --bearer-token-env-var HTML2MP4_API_KEYCodex config.toml
# export HTML2MP4_API_KEY="YOUR_API_KEY"
[mcp_servers.html2mp4]
url = "https://html2mp4.com/api/mcp"
bearer_token_env_var = "HTML2MP4_API_KEY"Workbuddy
{
"mcpServers": {
"html2mp4": {
"type": "streamableHttp",
"url": "https://html2mp4.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Cursor mcp.json
{
"mcpServers": {
"html2mp4": {
"url": "https://html2mp4.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Session API (browser / logged-in agent)
After the user signs in, call these with the session cookie (credentials: "include"). Do not use these for MCP tool calls — MCP uses Bearer keys only.
POST /api/account/api-keys— JSON body{}or{"name":"MCP key"}; returnssecretonceGET /api/account/api-keys— list keys (no secrets)DELETE /api/account/api-keys/:id— revoke
MCP tools
html2mp4_create_job— same scenarios as web Createhtml2mp4_get_job— status for one jobhtml2mp4_list_jobs— paginated listhtml2mp4_download— signed URL for finished MP4html2mp4_get_credits— credit balance
Verify
- Call
html2mp4_get_credits html2mp4_create_job→ pollhtml2mp4_get_jobhtml2mp4_downloadwhen status is succeeded