Layero

Instalación

Elige la app de IA que usas y copia la configuración.

Pasó 3/4 revisiones · Lo que preguntas pasa por el servidor del autor (mcp.layero.ru) · ✓ Comandos revisados el 13 nov 2026

claude mcp add --transport http --scope user layero https://mcp.layero.ru/mcp

{
  "mcpServers": {
    "layero": {
      "url": "https://mcp.layero.ru/mcp"
    }
  }
}

{
  "servers": {
    "layero": {
      "type": "http",
      "url": "https://mcp.layero.ru/mcp"
    }
  }
}

Qué apps pueden usarlo

Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.

Se conectan por internet en

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Todas las apps, con ventajas y desventajas →

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 14 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• 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 the page title, a direct URL (with anchor)

• 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.

• 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` and `root_directory` say where the pro

• 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 done by the person in the dashboard — nev

• 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 the first build; `setup` in the result sa

• 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 address (its host ends with `- `); the produ

• 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 after the first publish.

• 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 where the project is built from — a connecte

• check_rules

  Check 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 prize lures that send visitors to another domain. Checks what a visitor sees

• 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 limit: anything that reaches your answer se

• 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 platform decides), `resolved` (what the n

• 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 loop: the person may walk away for an hour

• 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.

• 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 difference of 3 points or more is meaningful

• 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 minutes to an hour, the platform re-che

• 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.

• 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 sure the expected version arrived. Without it you edit blind: what lies on the user's disk and what visitors are served are different things,

• 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. ⚠️ The screenshot is taken at BUILD time, n

• 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 location and a clear action: blocked indexing

• 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. Transformations are idempotent: a repeate

• 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, dashes, straight quotes, a dot instead

• 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 build: `branch`, `source` (`git` — built on

• download_source Parece una instrucción para la IA

  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; for a site published with `publish_site` — the published files. `.env*` files are left out. Needs a member who can deploy (editor role). Th

• 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 spent on the wrong version cannot be taken

• 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 platform refuses — that is not an error but pro

• cancel_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 and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the cause is vague, or you are interested in how

• 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 neighbourhood of the fatal line: the platform h

• 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, 8 MB in total, 2 MB per file. Binary fil

• 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`.

• data_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 also comes with its value (it is not a secret: it ships in the site bundle). Secret keys are never returned or stored. Enabling the API goes

• 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 force in the database itself — exactly as th

• 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 — a visitor will get every row"). Show the

• 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 an issued key is returned once: the platf

• 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 decided by access levels. Adding and re

• data_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 nothing by itself: reading and uploading are decided by storage policies (the dashboard → Files → Policies, or SQL on storage.objects). Creating n

• data_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 or Sber ID needs a secret — that is done by the person in the dashboard or with `layero data auth provider set` in a terminal, not through th

• 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 rollback does not undo sequence numbers, ca

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 14 nov 2026

• ✓ Superada

  El creador coincide con el repo

  El nombre en el registro se verificó con el dominio layero.ru (el registro comprueba quién es dueño del dominio)

• ✓ Superada

  Sigue en mantenimiento

  Último cambio de código: hace 6 días

• – No aplica

  Tiene licencia

  No aplica: servidor en la nube del propio dueño de layero.ru; no ejecutas código del repo

• ✓ Superada

  El endpoint responde

  Respondió en 634 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✕ No superada

  Sin instrucciones ocultas en las descripciones de herramientas

  1 descripciones de herramientas contienen texto que parece dar instrucciones a la IA. Léelas abajo antes de instalar

Reseñas de usuarios

Aún no hay reseñas

Inicia sesión con Google para escribir una reseña

Comparado con otros en Herramientas para desarrolladoresi

• Más estrellas que el 0% de los otros 5868 servidores de esta categoría
• Publicado en el registro más recientemente que el 39% de los otros 5868 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 46% de los otros 5868 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Otros de la misma categoría

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

de morluto·Muy usado·↓ 388,7 mil/sem·★ 457,7 mil·Actualizado anteayer

Se ejecuta en tu computadora

Instalar

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

de github·Muy usado·★ 34,4 mil·Actualizado hace 11 días

Computadora o nube

Instalar

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

de oraios·Muy usado·↓ 35,2 mil/sem·★ 31,3 mil·Actualizado hace 6 meses

Se ejecuta en tu computadora

Instalar

README del creador

LAYERO_TOKEN=… npx layero@latest deploy --project <slug> --json --yes

skills/layero/SKILL.md            — КАНОН: единый навык

make build   # перегенерировать адаптеры

LAYERO_TOKEN=… npx layero@latest deploy --project <slug> --json --yes