Publish a site from Claude Code with MCP

AI assistants now make pages, reports and small apps. Sharing what they made usually still needs you: copy the file, upload it somewhere, paste the link back. Taslak’s MCP server leaves that step to the agent.

The local MCP server

In Claude Code, one line is enough:

claude mcp add taslak -- npx -y https://taslak.dev/cli/taslak.tgz mcp

For other clients, the CLI writes the setup file:

npx -y https://taslak.dev/cli/taslak.tgz setup cursor

The options are claude, cursor, codex and agents.

The hosted MCP server

If you would rather not install anything, or your client supports remote servers, add https://api.taslak.dev/mcp. On the first connection you sign in to Taslak in the browser (OAuth); after that the client works on your behalf. Disconnect it any time under Connected apps on the API keys page.

What the agent can do

The server’s tools cover what an agent needs:

• publish_files: publish files as a new version.
• list_spaces, list_versions, rollback: see sites and versions, roll back.
• set_access, create_share_link, preview: change access, hand out share and preview links.
• add_domain, check_domain: connect a domain.
• db_create, db_query, db_rules: set up the site’s database and manage its tables.

Asked to “publish this folder and give me the link”, the agent creates the site and updates the same site on later requests.

Keep the important decisions

For steps such as making a site public or putting a new version live, you want the agent to ask. That is what request_approval is for: the agent opens a request, you get an e-mail, and you approve or deny it on the Approvals page. The agent reads your answer with get_approval and goes on accordingly.

Limit it with a key

If the agent runs with an API key instead of OAuth, give the key the publish scope only, limit it to one site and set an expiry date. Such a key cannot change access, domains or the team, and cannot create new sites.