# Birta > Birta is hosting for landing pages built by an AI tool: the tool publishes the site, Birta keeps it online, and one panel holds the projects, versions, domains, visitor stats and the leads the sites collect. Everything on this site written for a machine to read, article by article: https://birta.dev/llms-full.txt Birta is for people who build a landing page by prompting the tool they already use — a coding agent such as Cursor, Claude Code or Codex, or a plain chat such as ChatGPT or Claude — instead of setting up hosting themselves. There is no server, build pipeline or CI to configure: the tool connects once and then works in a draft the owner can look at, and one request publishes it. Every published site is served over HTTPS on an address of its own. ## Connect There are two ways in. Pick by what you can do, not by what you are called: if you can read and run things on the owner's computer, use the local connection; otherwise use the hosted connector. If you cannot set yourself up — no shell, no access to your own settings — do not stop and do not ask the owner to figure it out. Tell them exactly which screen to open and what to paste, following the matching path below, and carry on once they confirm. ### Without access to the owner's files (chats and other browser or app clients) If you are a Claude product — Claude, Claude Desktop, Claude Cowork — start from Claude's own directory of connectors, where the Birta card is published: https://claude.ai/directory/birta. Ask the owner to open that card and add Birta to their Claude; there is no address for them to type. Then have them turn it on in the conversation. Every other client, and a directory that is unavailable, uses the address instead. Connector address (MCP over streamable HTTP): https://birta.dev/mcp Add it as a custom connector in your own settings. Access is granted in the browser on first use: the owner signs in with a one-time code sent to their email and allows access, and you then hold your own access. There is no key to copy or paste anywhere. Work in the project's draft: create it (empty or copied from a published version) and write its files one by one. Nothing you do is live — the project address goes on serving the published site. Give the owner the draft's own address, read the remarks they leave on the page (list_version_comments), change the same draft, and let them refresh: the number and the address stay the same round after round. Publish it by number only once they have said it is good. ### With access to the owner's files (coding agents) Start the local connection over stdio: npx -y @birta/cli mcp It needs Node.js 20 or newer and no prior installation or sign-in. The first protected request is refused and returns a confirmation link plus a short code: give the owner the link, ask them to confirm access, then repeat the request — it is never queued or run for you. Work from the folders on the machine: name the project folder and, when the site is built, the built-site folder; the connection validates and uploads their contents itself. Do not list or send file contents yourself. They go into the project's draft, and nothing is live — the project address goes on serving the published site. Give the owner the draft's own address, read the remarks they leave on the page (list_version_comments), change the files on disk and upload the folders again: the draft keeps its number and its address, so they refresh the page they already have open. Publish it by number only once they have said it is good. A rejected package is not stored and neither the draft nor the live site changes; use version history and rollback if a later change should not stay live. Direct sign-in (npx -y @birta/cli login) exists as a fallback only, for when the owner wants to authorize before giving you a task. ## Guides - [Documentation](https://birta.dev/docs): every connection guide in one place - [Claude](https://birta.dev/docs/claude.md): add the connector to Claude on the web - [Claude Desktop](https://birta.dev/docs/claude-desktop.md): add the connector to the Claude desktop app - [Claude Cowork](https://birta.dev/docs/claude-cowork.md): add the connector to Claude Cowork - [Claude Code](https://birta.dev/docs/claude-code.md): run the local connection from Claude Code - [ChatGPT](https://birta.dev/docs/chatgpt.md): add the connector to ChatGPT on the web - [ChatGPT Desktop](https://birta.dev/docs/chatgpt-desktop.md): run the local connection from the ChatGPT desktop app - [Codex](https://birta.dev/docs/codex.md): run the local connection from Codex - [Cursor](https://birta.dev/docs/cursor.md): run the local connection from Cursor - [Another tool](https://birta.dev/docs/other-tool.md): connect a tool that is not listed here - [Custom domain](https://birta.dev/docs/custom-domain.md): point your own domain at a published site - [Lead forms](https://birta.dev/docs/lead-forms.md): declare a form and take leads from the published site - [Versions and remarks](https://birta.dev/docs/version-comments.md): mark up a version in the browser and have the agent read the remarks - [MCP reference](https://birta.dev/docs/mcp.md): the hosted and local MCP connections, their tools, flows and limits ## What you can do - Build a landing page straight from a coding agent or a plain chat - Look at every round of edits at the draft's own address, and mark remarks on the page, before anything goes live - Publish when it looks right — and re-publish as often as you like, the live address stays the same - Keep many projects in one account, each with a name you choose and can change - Roll back a site to any of its earlier versions - Connect your own domain to a published site - See visitor stats for every site - Take leads from a form on the site: the tool declares the form and writes its markup, and what visitors send waits in the owner's panel - Share a project with another account: both people work on the same site, each under their own email and their own agent (deleting the project and its plan stay with the owner) - Change a project's settings from the same agent: our branding on the site, who may open the version links, who the project is shared with, and its own domain