Agents Index

Layero

OnlineOfficial

Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.

Visit publisherConnectJSON

What it can do: 40 tools

  • search_docs read-onlySearch docs.layero.ru — no token needed. Use it before guessing how the platform works: build settings and `layero.json`, environments and preview URLs, custom domains, env vars, runtime apps, Data API, CLI
  • report_docs_issueSend a report about a docs.layero.ru problem to Layero — no sign-in. When: a docs page (or `search_docs`) was wrong, outdated, or did NOT have what you needed — including when you then found the answer elsewhere
  • whoami read-onlyWho 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 is cheaper than one halfway through a deploy.
  • my_projects read-onlyThe 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: an active user has dozens of projects. `url` is the canonical
  • list_sources read-onlyWhich git providers Layero supports and which of them the organization has connected (GitHub App installations and provider tokens). Call before `import_repo` when you are not sure the provider is connected.
  • import_repoCreate 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 production branch is production. After the link the tool finishes the
  • list_environments read-onlyThe project's environments — one per branch (or the single `cli` one), each with its address and the state of its latest build. Answers "where is the preview of my branch" and "what is on production now". `u
  • project_createCreate an empty project with no repository — an address reserved for a later `publish_site` or `npx layero@latest deploy`. For a project FROM a repository use `import_repo` instead. Nothing is built or serve
  • site_status read-onlyHow 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 (project, deploys, live check of the address). `source` / `repo` / `br
  • check_rules read-onlyCheck the published site against Layero's anti-phishing rules (https://layero.ru/rules): collecting passwords, card details or wallet recovery phrases of another service, fake security warnings, vote and priz
  • env_varsProject environment variables: list names, set them, remove them. VALUES ARE NEVER READ BACK — not by you, not by the platform in its response. Only names and lengths are returned. This is a deliberate rule
  • project_settingsBuild settings of a project: read them, or change them without the dashboard — the way out when detection guessed wrong (wrong folder, wrong type, wrong command). `get` returns `settings` (what is saved on t
  • connect_analyticsConnect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the user. The tool returns a link — show it and ask them to open it and
  • site_analytics read-onlySite traffic: totals, direction and top sources. The time series is collapsed into a direction and breakdowns are cut to five: ninety chart points are useless in your context, and the conclusion is yours to
  • check_performance read-onlyMeasure 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 the same deploy vary by at most one point, while LCP and TTFB on identical
  • connect_domainConnect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait
  • check_domain read-onlyCheck whether a connected domain has started working. Runs the DNS check immediately instead of waiting for the background re-check. If the records have not propagated yet, that is normal — say so and sugges
  • list_domains read-onlyThe project's own domains and their state.
  • read_site read-onlyWhat is really published: headings, copy, forms, meta, links. Call it BEFORE changing anything on a live site and AFTER a publish, to make sure the expected version arrived. Without it you edit blind: what l
  • site_screenshot read-onlyA screenshot of the latest built version of the site — how it looks. Complements `read_site` (what is on the page) and `site_issues` (what is wrong with it) with the third question: how it looks. Useful before a
  • site_issues read-onlyConcrete 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 score gives nothing to fix: "73 out of 100" does not say what to change.
  • refactor_site read-onlyOne named markup transformation — with a predictable result. The tool PUBLISHES NOTHING. It returns the changed HTML; showing it to the person, getting consent and calling `publish_site` is your job. Never r
  • check_copy read-onlyMechanical errors of Russian typography — with the exact place and a replacement. This is CODE, not a model's judgement: the same text gives the same list of findings. It catches what the eye misses and the
  • list_deploys read-onlyThe 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 `diagnose_deploy`. For "what is up with the site right now" `site_status
  • download_source read-onlyA 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; for a site published with `publish_site` — the published files. `.
  • rollbackPut the previous working build back on the live address. CHANGES WHAT VISITORS SEE — ask the person before calling unless they asked for a rollback explicitly. The action is reversible (you can roll forward
  • retry_deployRun a build again — a failed one as is, or the latest commit afresh. Default (`redeploy=false`): queue the SAME build again. Allowed only for builds in the `failed` or `cancelled` state. On a running build (
  • cancel_deployStop a build that is still running. The live address does not change — the previous version stays on it.
  • deploy_logs read-onlyRaw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighbourhood of the fatal line. Come here when you need to look
  • diagnose_deploy read-onlyWhy a deploy failed — with the cause parsed out, not a raw log. Without `deploy` the latest build is used; that is what reflects the current state. To examine a specific older one, pass its id. The response
  • publish_sitePublish 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 the project has no connected repository. Requirements — `index.html` at
  • publish_landingDEPRECATED — use `publish_site`. Same behaviour, same arguments. Kept for one release (removed in the next) so that configs and prompts written before 17.09.2026 keep working; new instructions must call `pub
  • data_api_status read-onlyWhether 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 also comes with its value (it is not a secret: it ships in the site
  • data_api_methods read-onlyThe 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 visitor), user (signed-in people), server (the server only). It is read
  • data_api_grantWho 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 `apply` first: the platform returns the commands and warnings (for exam
  • data_api_keysThe database's Data API keys: list, issue, revoke. The list never contains key values. Issuing and revoking need the person's consent: a client with forms asks by itself; without forms ask in the chat and pa
  • data_api_originsSites allowed to call the database from a browser: list, add, remove. Addresses of the connected projects and their branches are allowed automatically — do not add them. An added site opens no data by itself:
  • data_api_bucketsStorage buckets of a database: list and create — without a secret key. Files must be enabled for the database. A private bucket opens nothing by itself: reading and uploading are decided by storage policies (the
  • data_api_authSign-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 or Sber ID needs a secret — that is done by the person in the dashboard
  • data_api_probeA 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 (POST, PATCH, DELETE, a function call) are rolled back: rows in the da

Connect it

Claude Code
claude mcp add --transport http layero https://mcp.layero.ru/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.layero.ru/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "layero": {
      "url": "https://mcp.layero.ru/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "layero": {
      "type": "http",
      "url": "https://mcp.layero.ru/mcp"
    }
  }
}

Questions

What does Layero do?

Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API. It exposes 40 tools to AI assistants.

What tools does Layero provide?

40 tools, including search_docs, report_docs_issue, whoami, my_projects, list_sources, import_repo, list_environments, project_create, site_status, check_rules, env_vars, project_settings….

How do I connect Layero to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.layero.ru/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Layero require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Layero online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Layero?

layero.ru. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps