Categories › Cloud & DevOps › Hosting & deployment
Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.
Remote server: your requests and data go to mcp.layero.ru. Claude Code: claude mcp add --transport http layero https://mcp.layero.ru/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_docs — Search docs.layero.ru — no token needed. Use it before guessing how the platform works: build settings and `layero.json`, environments and pwhoami — Who is connected to Layero and how many projects they have. Call this first when you are unsure the token is configured: a clear error here my_projects — The user's sites on Layero. Thirty most recent by default. The full list is rarely needed, while flooding half your context with it is easy:list_sources — Which git providers Layero supports and which of them the organization has connected (GitHub App installations and provider tokens). Call beimport_repo — Create a Layero project from a repository — path (a) without the dashboard. From then on a push to the branch is a preview, a push to the prlist_environments — The project's environments — one per branch (or the single `cli` one), each with its address and the state of its latest build. Answers "wheproject_create — Create an empty project with no repository — an address reserved for a later `publish_site` or `npx layero@latest deploy`. For a project FROsite_status — How a site is doing: where it is built from, whether the address is answering, and how the latest build ended. One call instead of three (prcheck_rules — Check the published site against Layero's anti-phishing rules (https://layero.ru/rules): collecting passwords, card details or wallet recoveenv_vars — Project environment variables: list names, set them, remove them. VALUES ARE NEVER READ BACK — not by you, not by the platform in its responproject_settings — Build settings of a project: read them, or change them without the dashboard — the way out when detection guessed wrong (wrong folder, wrongconnect_analytics — Connect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the usite_analytics — Site traffic: totals, direction and top sources. The time series is collapsed into a direction and breakdowns are cut to five: ninety chart check_performance — Measure a site's speed and say whether it got worse after a deploy. The verdict comes FROM THE SCORE, not from timings: repeated runs of theconnect_domain — Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to thecheck_domain — Check whether a connected domain has started working. Runs the DNS check immediately instead of waiting for the background re-check. If the list_domains — The project's own domains and their state.read_site — What is really published: headings, copy, forms, meta, links. Call it BEFORE changing anything on a live site and AFTER a publish, to make ssite_screenshot — A screenshot of the latest built version of the site — how it looks. Complements `read_site` (what is on the page) and `site_issues` (what isite_issues — Concrete problems of a page — each with its location and what to do. This is NOT a score. The score comes from `check_performance`, and a screfactor_site — One named markup transformation — with a predictable result. The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to the perscheck_copy — Mechanical errors of Russian typography — with the exact place and a replacement. This is CODE, not a model's judgement: the same text giveslist_deploys — The project's latest builds: how each one ended, how long it took and which one is live now. Use it to pick a target for `rollback` or `diagdownload_source — A short download link to a ZIP of what a build was made from. For an upload (`npx layero@latest deploy`) the ZIP holds the uploaded sources;rollback — Put the previous working build back on the live address. CHANGES WHAT VISITORS SEE — ask the person before calling unless they asked for a rretry_deploy — Run a build again — a failed one as is, or the latest commit afresh. Default (`redeploy=false`): queue the SAME build again. Allowed only focancel_deploy — Stop a build that is still running. The live address does not change — the previous version stays on it.deploy_logs — Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause andiagnose_deploy — Why a deploy failed — with the cause parsed out, not a raw log. Without `deploy` the latest build is used; that is what reflects the currentpublish_site — Publish a static site to Layero — from here, with no terminal. Takes ANY ready static bundle, so it is the answer to "deploy my site" when tpublish_landing — DEPRECATED — use `publish_site`. Same behaviour, same arguments. Kept for one release (removed in the next) so that configs and prompts writdata_api_status — Whether the database has the Data API enabled, its address, keys and the sites allowed to call it. Keys are shown by prefix; the public key data_api_methods — The database's REST and RPC methods with an access level per HTTP method. The level says who may call the method: closed, visitor (any site data_api_grant — Who may call a method of a table or a function: shows the SQL and applies it after consent. OPENS DATA TO THE INTERNET. Call it without `appdata_api_keys — The database's Data API keys: list, issue, revoke. The list never contains key values. Issuing and revoking need the person's consent: a clidata_api_origins — Sites allowed to call the database from a browser: list, add, remove. Addresses of the connected projects and their branches are allowed autdata_api_buckets — Storage buckets of a database: list and create — without a secret key. Files must be enabled for the database. A private bucket opens nothindata_api_auth — Sign-in of the app's users: what is enabled, and the sender name of its emails. Provider keys are never returned. Connecting Yandex, VK ID odata_api_probe — A real request to a method through the gateway — as a visitor, a user or the server. The platform supplies the key and the token. Writes (PONot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.