Layero is a remote MCP server that gives an AI agent 35 tools, among them cancel_deploy, check_copy, check_domain. It answers at https://mcp.layero.ru/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
cancel_deploy | Stop a build that is still running. The live address does not change — the previous version stays on it. Inputs: project, deploy |
check_copy | Mechanical 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 reader feels: non-breaking spaces Inputs: text, project, path |
check_domain | Check 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 suggest coming back later. Inputs: project, domain |
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 the same deploy vary by at most one point, while LCP and TTFB on identical code swing by 37-40%. A diff Inputs: project, wait |
connect_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 user. The tool returns a link — show it and ask them to open it and grant access. Do not poll in a lo Inputs: project, branch |
connect_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 the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in Inputs: project, domain |
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 `apply` first: the platform returns the commands and warnings (for example "row-level security is off — Inputs: object, get, post, patch, delete, call |
data_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 client with forms asks by itself; without forms ask in the chat and pass confirmed=true. The value of a Inputs: action, kind, label, expires_in_days, key, confirmed |
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 visitor), user (signed-in people), server (the server only). It is read from the role grants in forc Inputs: database, organization |
data_api_origins | Sites 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: what can be read and written is Inputs: action, url, note, confirmed, database, organization |
data_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 (POST, PATCH, DELETE, a function call) are rolled back: rows in the database do not change, but the rol Inputs: method, path, role, query, body, user_id |
data_api_status | Whether the database has the Data API enabled, its address, keys and the sites allowed to call it. Keys are shown as prefixes only: the platform never returns values and does not store secret ones. The API cannot be enabled with a tool: ena Inputs: database, organization |
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 and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the caus Inputs: project, kind, deploy, tail, include_noise |
diagnose_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 current state. To examine a specific older one, pass its id. The response is not a log tail but the neighbo Inputs: project, deploy |
env_vars | Project 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 rather than an implementation lim Inputs: project, action, values, keys |
import_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 production branch is production. After the link the tool finishes the setup wizard itself and starts t Inputs: provider, repo, branch, name, organization, deploy |
list_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 `diagnose_deploy`. For "what is up with the site right now" `site_status` is enough and cheaper. Per buil Inputs: project, limit |
list_domains | The project's own domains and their state. Inputs: project |
list_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 "where is the preview of my branch" and "what is on production now". `url` is the environment's own addr Inputs: project |
list_sources | Which 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. Connecting a provider token is d Inputs: organization |
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: an active user has dozens of projects. `url` is the canonical (production) address. `repo`, `branch Inputs: limit, repo |
project_create | Create 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 served yet: the address answers only a Inputs: name, organization |
project_settings | Build 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 the project; null — not set, the p Inputs: project, action, root_directory, project_type, force_type, framework |
publish_landing | DEPRECATED — 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 `publish_site`. Inputs: files, project_name, project |
publish_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 the project has no connected repository. Requirements — `index.html` at the root, at most 200 files, Inputs: files, project_name, project |
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 sure the expected version arrived. Without it you edit blind: what lies on the user's disk and what v Inputs: project, path |
refactor_site | One 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 rewrite someone's site silently. T Inputs: html, fix |
retry_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 for builds in the `failed` or `cancelled` state. On a running build (`queued`, `building`) the platfor Inputs: project, deploy, redeploy, branch |
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 rollback explicitly. The action is reversible (you can roll forward again), but the time visitors spe Inputs: project, deploy |
search_docs | Search 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 flags and JSON events. Returns th Inputs: query, limit |
site_analytics | Site 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 draw anyway. Inputs: project, period |
site_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 score gives nothing to fix: "73 out of 100" does not say what to change. Here is only what has a locat Inputs: project, path |
site_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 is wrong with it) with the third question: how it looks. Useful before and after a visual change. ⚠️ Inputs: project |
site_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 (project, deploys, live check of the address). `source` / `repo` / `branch` / `root_directory` say wher Inputs: project, path, wait_s |
whoami | 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 is cheaper than one halfway through a deploy. |
Every block below points at https://mcp.layero.ru/mcp. Pick your client and copy.
claude mcp add --transport http layero https://mcp.layero.ru/mcp
{
"mcpServers": {
"layero": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.layero.ru/mcp"]
}
}
}{
"mcpServers": {
"layero": {
"url": "https://mcp.layero.ru/mcp"
}
}
}{
"servers": {
"layero": {
"type": "http",
"url": "https://mcp.layero.ru/mcp"
}
}
}{
"context_servers": {
"layero": {
"url": "https://mcp.layero.ru/mcp"
}
}
}{
"mcpServers": {
"layero": {
"serverUrl": "https://mcp.layero.ru/mcp"
}
}
}{
"mcpServers": {
"layero": {
"url": "https://mcp.layero.ru/mcp"
}
}
}name: Layero
version: 0.0.1
schema: v1
mcpServers:
- name: Layero
type: streamable-http
url: https://mcp.layero.ru/mcp{
"mcpServers": {
"layero": {
"httpUrl": "https://mcp.layero.ru/mcp"
}
}
}{
"mcpServers": {
"layero": {
"type": "http",
"url": "https://mcp.layero.ru/mcp"
}
}
}{
"mcpServers": {
"layero": {
"url": "https://mcp.layero.ru/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.layero.ru%2Fmcp&type=streamable_http&id=layero&name=Layero
It answered our last check on 24 October 2026 in 533 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by layero.ru and served from mcp.layero.ru, the vendor's own domain: https://mcp.layero.ru/mcp.
35, as returned by the server's own tools/list on 23 September 2026: cancel_deploy, check_copy, check_domain, check_performance, connect_analytics, connect_domain, data_api_grant, data_api_keys, and 27 more.
It answered our last check on 24 October 2026 in 533 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.layero.ru/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ru.layero. Endpoint host: mcp.layero.ru. ARD identifier: urn:air:ru.layero:mcp:layero.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.