{"id":"ru.layero/layero","slug":"ru-layero-layero","title":"Layero","description":"Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.","version":"2.4.0","publisher":{"kind":"domain","id":"layero.ru","label":"layero.ru","url":"https://layero.ru"},"website":"https://docs.layero.ru/agents/","repository":"https://github.com/LayeroInfra/layero-agents","remotes":[{"type":"streamable-http","url":"https://mcp.layero.ru/mcp","headers":[{"description":"Layero token for CI and headless clients, issued at https://app.layero.ru/settings/cli or with `npx layero@latest token create`. Optional: interactive clients sign in through OAuth.","isSecret":true,"placeholder":"Bearer layero_ci_...","name":"Authorization"}]}],"packages":[],"published":"2026-09-19","updated":"2026-09-19","status":"online","auth":"","latency_ms":1590,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_docs","title":"Поиск по документации","description":"Search docs.layero.ru — no token needed.\n\n    Use it before guessing how the platform works: build settings and\n    `layero.json`, environments and preview URLs, custom domains, env vars,\n    runtime apps, Data API, CLI flags and JSON events. Returns the page\n    title, a direct URL (with anchor) and a snippet; open the URL with your\n    own fetch tool when the snippet is not enough. `score` is re","read_only":true},{"name":"report_docs_issue","title":"Сообщить об ошибке в документации","description":"Send a report about a docs.layero.ru problem to Layero — no sign-in.\n\n    When: a docs page (or `search_docs`) was wrong, outdated, or did NOT have\n    what you needed — including when you then found the answer elsewhere\n    (source code, `--help`, trial and error) — and it cost you a real detour\n    likely to hit the next agent. Not for small hiccups solved at once.\n\n    Ask first: finish the tas","read_only":false},{"name":"whoami","title":"Кто подключён к Layero","description":"Who is connected to Layero and how many projects they have.\n\n    Call this first when you are unsure the token is configured: a clear\n    error here is cheaper than one halfway through a deploy.\n    ","read_only":true},{"name":"my_projects","title":"Мои сайты","description":"The user's sites on Layero.\n\n    Thirty most recent by default. The full list is rarely needed, while\n    flooding half your context with it is easy: an active user has dozens\n    of projects.\n\n    `url` is the canonical (production) address. `repo`, `branch` and\n    `root_directory` say where the project is built from: all three are\n    null for a project without a repository (CLI or `publish_sit","read_only":true},{"name":"list_sources","title":"Провайдеры и подключения репозиториев","description":"Which git providers Layero supports and which of them the organization\n    has connected (GitHub App installations and provider tokens).\n\n    Call before `import_repo` when you are not sure the provider is\n    connected. Connecting a provider token is done by the person in the\n    dashboard — never ask them to paste the token into the chat.\n    ","read_only":true},{"name":"import_repo","title":"Проект из репозитория","description":"Create a Layero project from a repository — path (a) without the\n    dashboard. From then on a push to the branch is a preview, a push to the\n    production branch is production.\n\n    After the link the tool finishes the setup wizard itself and starts the\n    first build; `setup` in the result says whether that happened. Detected\n    values are NOT written into the project settings: the builder de","read_only":false},{"name":"list_environments","title":"Окружения проекта","description":"The project's environments — one per branch (or the single `cli` one),\n    each with its address and the state of its latest build.\n\n    Answers \"where is the preview of my branch\" and \"what is on production\n    now\". `url` is the environment's own address (its host ends with\n    `-<branch>`); the production branch is ALSO served at the project's\n    canonical address from `site_status` / `my_proj","read_only":true},{"name":"project_create","title":"Новый пустой проект","description":"Create an empty project with no repository — an address reserved for a\n    later `publish_site` or `npx layero@latest deploy`.\n\n    For a project FROM a repository use `import_repo` instead. Nothing is\n    built or served yet: the address answers only after the first publish.\n    ","read_only":false},{"name":"site_status","title":"Как дела у сайта","description":"How a site is doing: where it is built from, whether the address is\n    answering, and how the latest build ended.\n\n    One call instead of three (project, deploys, live check of the address).\n    `source` / `repo` / `branch` / `root_directory` say where the project is\n    built from — a connected repository means deploys go through git.\n\n    `serving` is true when the SITE ITSELF answered — any r","read_only":true},{"name":"check_rules","title":"Проверить сайт на правила против фишинга","description":"Check the published site against Layero's anti-phishing rules\n    (https://layero.ru/rules): collecting passwords, card details or wallet\n    recovery phrases of another service, fake security warnings, vote and\n    prize lures that send visitors to another domain.\n\n    Checks what a visitor sees at the project address — the home page and its\n    own scripts. `violations` is empty when nothing mat","read_only":true},{"name":"env_vars","title":"Переменные окружения проекта","description":"Project environment variables: list names, set them, remove them.\n\n    VALUES ARE NEVER READ BACK — not by you, not by the platform in its\n    response. Only names and lengths are returned. This is a deliberate rule\n    rather than an implementation limit: anything that reaches your answer\n    settles into the conversation history, and a secret that lands there\n    cannot be taken back. If the use","read_only":false},{"name":"project_settings","title":"Настройки сборки проекта","description":"Build settings of a project: read them, or change them without the\n    dashboard — the way out when detection guessed wrong (wrong folder,\n    wrong type, wrong command).\n\n    `get` returns `settings` (what is saved on the project; null — not set,\n    the platform decides), `resolved` (what the next build will actually use,\n    per field: `value`, `source`, `policy`) and `last_build` (what the lat","read_only":false},{"name":"connect_analytics","title":"Подключить Яндекс.Метрику","description":"Connect Yandex Metrika to a site.\n\n    IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the\n    platform can do that step for the user. The tool returns a link — show\n    it and ask them to open it and grant access. Do not poll in a loop: the\n    person may walk away for an hour. Check later through this same tool\n    without the `branch` argument, or through `site_analytics`.\n  ","read_only":false},{"name":"site_analytics","title":"Трафик сайта","description":"Site traffic: totals, direction and top sources.\n\n    The time series is collapsed into a direction and breakdowns are cut to\n    five: ninety chart points are useless in your context, and the\n    conclusion is yours to draw anyway.\n    ","read_only":true},{"name":"check_performance","title":"Замерить скорость сайта","description":"Measure a site's speed and say whether it got worse after a deploy.\n\n    The verdict comes FROM THE SCORE, not from timings: repeated runs of the\n    same deploy vary by at most one point, while LCP and TTFB on identical\n    code swing by 37-40%. A difference of 3 points or more is meaningful;\n    anything smaller is measurement noise, and calling that a regression is\n    inventing a problem.\n\n   ","read_only":true},{"name":"connect_domain","title":"Подключить свой домен","description":"Connect a custom domain to a site.\n\n    IMPORTANT: between this call and a working domain stands A PERSON. You\n    get DNS records — show them to the user and explain they go in at their\n    domain registrar. Do not wait for readiness: DNS propagates in minutes\n    to an hour, the platform re-checks on its own, and you check later via\n    `check_domain`. Spinning here burns time and context for no","read_only":false},{"name":"check_domain","title":"Проверить, заработал ли домен","description":"Check whether a connected domain has started working.\n\n    Runs the DNS check immediately instead of waiting for the background\n    re-check. If the records have not propagated yet, that is normal — say\n    so and suggest coming back later.\n    ","read_only":true},{"name":"list_domains","title":"Домены проекта","description":"The project's own domains and their state.","read_only":true},{"name":"read_site","title":"Прочитать страницу сайта","description":"What is really published: headings, copy, forms, meta, links.\n\n    Call it BEFORE changing anything on a live site and AFTER a publish, to\n    make sure the expected version arrived. Without it you edit blind: what\n    lies on the user's disk and what visitors are served are different\n    things, and they drift apart silently.\n\n    The result is a STRUCTURE, not raw HTML: a page with inline styles","read_only":true},{"name":"site_screenshot","title":"Показать снимок сайта","description":"A screenshot of the latest built version of the site — how it looks.\n\n    Complements `read_site` (what is on the page) and `site_issues` (what is\n    wrong with it) with the third question: how it looks. Useful before and\n    after a visual change.\n\n    ⚠️ The screenshot is taken at BUILD time, not now. Right after a publish\n    a fresh one does not appear instantly — do not present the previous ","read_only":true},{"name":"site_issues","title":"Что чинить на сайте","description":"Concrete problems of a page — each with its location and what to do.\n\n    This is NOT a score. The score comes from `check_performance`, and a\n    score gives nothing to fix: \"73 out of 100\" does not say what to change.\n    Here is only what has a location and a clear action: blocked indexing,\n    resources from foreign hosts, raster images without webp, missing meta\n    and alt, forms with no rec","read_only":true},{"name":"refactor_site","title":"Применить правку к разметке сайта","description":"One named markup transformation — with a predictable result.\n\n    The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to\n    the person, getting consent and calling `publish_site` is your job.\n    Never rewrite someone's site silently.\n\n    Transformations are idempotent: a repeated call changes nothing and\n    honestly answers `changed=false`. An empty list of changes is not an\n  ","read_only":true},{"name":"check_copy","title":"Вычитать русский текст","description":"Mechanical errors of Russian typography — with the exact place and a\n    replacement.\n\n    This is CODE, not a model's judgement: the same text gives the same list\n    of findings. It catches what the eye misses and the reader feels:\n    non-breaking spaces, dashes, straight quotes, a dot instead of a comma in\n    decimals, spaces around punctuation, double spaces.\n\n    Every finding carries a rea","read_only":true},{"name":"list_deploys","title":"История сборок проекта","description":"The project's latest builds: how each one ended, how long it took and\n    which one is live now.\n\n    Use it to pick a target for `rollback` or `diagnose_deploy`. For \"what is\n    up with the site right now\" `site_status` is enough and cheaper.\n\n    Per build: `branch`, `source` (`git` — built on push, `cli` — an uploaded\n    folder), short `commit`, `created_at` / `started_at` / `finished_at`\n   ","read_only":true},{"name":"download_source","title":"Скачать исходники деплоя","description":"A short download link to a ZIP of what a build was made from.\n\n    For an upload (`npx layero@latest deploy`) the ZIP holds the uploaded\n    sources; for a site published with `publish_site` — the published files.\n    `.env*` files are left out. Needs a member who can deploy (editor role).\n    The link works for 5 minutes: hand it to the person, do not fetch it\n    yourself unless they asked you t","read_only":true},{"name":"rollback","title":"Откатить сайт на прошлую сборку","description":"Put the previous working build back on the live address.\n\n    CHANGES WHAT VISITORS SEE — ask the person before calling unless they\n    asked for a rollback explicitly. The action is reversible (you can roll\n    forward again), but the time visitors spent on the wrong version cannot\n    be taken back.\n\n    ⚠️ For apps (`ssr_next`, `node_web`, `python_web`, `streamlit`, `gradio`,\n    `flask`) a rol","read_only":false},{"name":"retry_deploy","title":"Перезапустить сборку","description":"Run a build again — a failed one as is, or the latest commit afresh.\n\n    Default (`redeploy=false`): queue the SAME build again. Allowed only for\n    builds in the `failed` or `cancelled` state. On a running build\n    (`queued`, `building`) the platform refuses — that is not an error but\n    protection against a second parallel build; on a `ready` build it\n    refuses too — use `redeploy=true`.\n\n","read_only":false},{"name":"cancel_deploy","title":"Отменить идущую сборку","description":"Stop a build that is still running.\n\n    The live address does not change — the previous version stays on it.\n    ","read_only":false},{"name":"deploy_logs","title":"Логи сборки и приложения","description":"Raw log lines — for when the `diagnose_deploy` analysis was not enough.\n\n    Start with `diagnose_deploy`: it has already pulled out the cause and\n    the neighbourhood of the fatal line. Come here when you need to look\n    with your own eyes — the cause is vague, or you are interested in how\n    the app behaves rather than in a failure.\n\n    You get the TAIL. `truncated` says earlier lines were d","read_only":true},{"name":"diagnose_deploy","title":"Почему упала сборка","description":"Why a deploy failed — with the cause parsed out, not a raw log.\n\n    Without `deploy` the latest build is used; that is what reflects the\n    current state. To examine a specific older one, pass its id.\n\n    The response is not a log tail but the neighbourhood of the fatal line:\n    the platform has already picked out what matters. Read `verdict` and the\n    summary, fix the code, deploy again — y","read_only":true},{"name":"publish_site","title":"Опубликовать сайт","description":"Publish a static site to Layero — from here, with no terminal.\n\n    Takes ANY ready static bundle, so it is the answer to \"deploy my site\" when\n    the project has no connected repository. Requirements — `index.html` at\n    the root, at most 200 files, 8 MB in total, 2 MB per file. Binary files\n    (images, fonts) must come with `encoding=\"base64\"`; sent as text they are\n    silently corrupted.\n\n ","read_only":false},{"name":"publish_landing","title":"Опубликовать сайт (старое имя)","description":"DEPRECATED — use `publish_site`. Same behaviour, same arguments.\n\n    Kept for one release (removed in the next) so that configs and prompts\n    written before 17.09.2026 keep working; new instructions must call\n    `publish_site`.\n    ","read_only":false},{"name":"data_api_status","title":"Data API базы: состояние","description":"Whether the database has the Data API enabled, its address, keys and\n    the sites allowed to call it.\n\n    Keys are shown by prefix; the public key also comes with its value (it is\n    not a secret: it ships in the site bundle). Secret keys are never returned\n    or stored. Enabling the API goes through the CLI; as in\n    Supabase, new tables in `public` are then open to the roles and RLS\n    dec","read_only":true},{"name":"data_api_methods","title":"Data API базы: методы и доступ","description":"The database's REST and RPC methods with an access level per HTTP method.\n\n    The level says who may call the method: closed, visitor (any site\n    visitor), user (signed-in people), server (the server only). It is read\n    from the role grants in force in the database itself — exactly as the\n    gateway sees them. `warnings` names what is unsafe or not working: a\n    table without RLS open to vi","read_only":true},{"name":"data_api_grant","title":"Data API базы: доступ к методу","description":"Who may call a method of a table or a function: shows the SQL and\n    applies it after consent.\n\n    OPENS DATA TO THE INTERNET. Call it without `apply` first: the platform\n    returns the commands and warnings (for example \"row-level security is\n    off — a visitor will get every row\"). Show them to the person. With\n    apply=true a client with forms asks the person itself; without forms get\n    ","read_only":false},{"name":"data_api_keys","title":"Data API базы: ключи","description":"The database's Data API keys: list, issue, revoke.\n\n    The list never contains key values. Issuing and revoking need the\n    person's consent: a client with forms asks by itself; without forms ask\n    in the chat and pass confirmed=true. The value of an issued key is\n    returned once: the platform does not store secret keys. Hand it to the\n    person for their server and do not repeat it afterwa","read_only":false},{"name":"data_api_origins","title":"Data API базы: сайты","description":"Sites allowed to call the database from a browser: list, add, remove.\n\n    Addresses of the connected projects and their branches are allowed\n    automatically — do not add them. An added site opens no data by itself:\n    what can be read and written is decided by access levels. Adding and\n    removing need the person's consent; a removed site is refused on every\n    request. Needs a token with th","read_only":false},{"name":"data_api_buckets","title":"Data API базы: бакеты файлов","description":"Storage buckets of a database: list and create — without a secret key.\n\n    Files must be enabled for the database. A private bucket opens nothing by\n    itself: reading and uploading are decided by storage policies (the\n    dashboard → Files → Policies, or SQL on storage.objects). Creating needs\n    the person's consent. Needs a token with the admin scope — the storage key\n    is issued only to i","read_only":false},{"name":"data_api_auth","title":"Data API базы: вход пользователей","description":"Sign-in of the app's users: what is enabled, and the sender name of its emails.\n\n    Provider keys are never returned. Connecting Yandex, VK ID or Sber ID needs\n    a secret — that is done by the person in the dashboard or with\n    `layero data auth provider set` in a terminal, not through the chat.\n    Setting the sender needs a token with the admin scope.\n    ","read_only":false},{"name":"data_api_probe","title":"Data API базы: проба метода","description":"A real request to a method through the gateway — as a visitor, a user\n    or the server.\n\n    The platform supplies the key and the token. Writes (POST, PATCH, DELETE,\n    a function call) are rolled back: rows in the database do not change,\n    but the rollback does not undo sequence numbers, calls from the database\n    to the outside, session locks or the daily call quota. The answer is\n    real","read_only":false}],"server_info":{"name":"layero","version":"2.7.0"},"category":"cloud","tags":["project","analytics","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":350412,"score":100,"indexable":true,"first_seen":"2026-09-19","stars":0,"badges":["official"],"sponsor":null,"page":"https://agentsindex.org/agents/ru-layero-layero/"}