Connect arcdoq as a remote MCP connector and Claude can publish and manage your sites straight from a conversation. Claude builds the HTML, arcdoq hosts it at a real URL. You sign in once with your workspace.
Use Claude Code from the terminal, or add it as a custom connector in the Claude apps. The endpoint is the same either way: https://mcp.arcdoq.com/mcp.
Run this in your terminal.
$ claude mcp add --transport http arcdoq \
https://mcp.arcdoq.com/mcp
Settings, then Connectors, then Add custom connector. Paste the URL.
https://mcp.arcdoq.com/mcp
The first time Claude connects, arcdoq opens a sign-in and asks which workspace to publish to. Access is scoped to that workspace and the sites in it, and every tool runs as you, under your plan and permissions. Connect over OAuth, and revoke it any time from your account.
Sixteen tools cover the publish lifecycle and the read side that came after it — Claude can search and quote a site you published as readily as it can ship one. Read tools run without a prompt; tools that change or remove data ask first. In practice you just say what you want: publish this as launch-notes, roll it back a version, or what do our docs say about refunds, and Claude picks the tool.
There is no tool that creates a deploy token, on purpose: minting one would have to hand the secret to Claude, and a credential that lands in a transcript is a credential you have to rotate. You mint tokens yourself in the app, shown once — see Deploy from CI.
An arcdoq workspace. Publishing is on every plan, including Free. If you don't have access yet, request it and we'll get you in.
Questions about the connector? Email support@arcdoq.com.