Деплой фронтенд- и фуллстек-приложений за одну команду — npx layero@latest deploy. Серверы и трафик в России, сеть доставки в 27 городах, без VPN и замедлений. Поддержка Vite, Next.js, Astro, SvelteKit, Nuxt, CRA, Gatsby, Streamlit. Работает с Cursor, Claude Code и другими AI-агентами. Есть бесплатный тариф.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.layero.ru
35tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.layero.ru/mcp
Skill page: https://www.mcpbundles.com/skills/layero-mcp-8922f629e1
Explore capabilities (35)
read 16
other 9
Showing 25 of 35
Showing 25 of 35 tools from the public preview. Connect the server to inspect the full live tool list.
List4
Site4
Check3
Connect2
Project2
Other capabilities10
Поиск по документации
read
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) and a snippet; open the URL with your
own fetch tool when the snippet is not enough. `score` is relative
within one answer: a rare query word found in a page title weighs most,
and a page ma
Description may be truncated on the public preview.
Поиск по документации — 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) and a snippet; open the URL with your
own fetch tool when the snippet is not enough. `score` is relative
within one answer: a rare query word found in a page title weighs most,
and a page ma
Кто подключён к Layero — 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.
Мои сайты — 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 project is built from: all three are
null for a project without a repository (CLI or `publish_site`);
`root_directory` is the app folder inside a monorepo, null for the
repository root.
Провайдеры и подключения репозиториев — 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 — never ask them to paste the token into the chat.
Проект из репозитория — 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 says whether that happened. Detected
values are NOT written into the project settings: the builder detects
the framework, build command and output folder from the repository on
every build, so
Окружения проекта
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Деплой фронтенд- и фуллстек-приложений за одну команду — npx layero@latest deploy. Серверы и трафик в России, сеть доставки в 27 городах, без VPN и замедлений. Поддержка Vite, Next.js, Astro, SvelteKit, Nuxt, CRA, Gatsby, Streamlit. Работает с Cursor, Claude Code и другими AI-агентами. Есть бесплатный тариф.
How do I connect Layero to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want Layero listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Layero?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in hosting
Other MCP servers in this category from the directory index
— 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
`-<branch>`); the production branch is ALSO served at the project's
canonical address from `site_status` / `my_projects`. Take addresses
from here, never assemble them.
Новый пустой проект — 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.
Как дела у сайта — 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 connected repository means deploys go through git.
`serving` is true when the SITE ITSELF answered — any response that is
not a Layero platform screen and not a 5xx. An API server that has no
`/` ro
Переменные окружения проекта — 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
settles into the conversation history, and a secret that lands there
cannot be taken back. If the user asks "what is my key", say plainly
that you cannot show it and offer to set a new one.
`s
Настройки сборки проекта — 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 next build will actually use,
per field: `value`, `source`, `policy`) and `last_build` (what the latest
ready build was really built with). Precedence is `layero.json` in the
repository > proj
Подключить Яндекс.Метрику — 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. Check later through this same tool
without the `branch` argument, or through `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.
Замерить скорость сайта — 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;
anything smaller is measurement noise, and calling that a regression is
inventing a problem.
A run takes tens of seconds. With `wait=true` the tool waits for you; do
not start a second mea
Подключить свой домен — 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-checks on its own, and you check later via
`check_domain`. Spinning here burns time and context for nothing.
The address can be passed as-is: the platform reduces
`https://shop.example.com/page
Проверить, заработал ли домен — 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.
Домены проекта — The project's own domains and their state.
Прочитать страницу сайта — 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, and they drift apart silently.
The result is a STRUCTURE, not raw HTML: a page with inline styles would
eat half your context, while what you need from it is headings, copy,
forms and meta.
Показать снимок сайта — 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, not now. Right after a publish
a fresh one does not appear instantly — do not present the previous one
as the result of your change.
An image costs far more context than text. Do not call it
Что чинить на сайте — 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,
resources from foreign hosts, raster images without webp, missing meta
and alt, forms with no recipient.
Findings are sorted by importance. Do not dump the list — name the two
or three mai
Применить правку к разметке сайта — 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 repeated call changes nothing and
honestly answers `changed=false`. An empty list of changes is not an
error, it means "there was nothing to apply".
⚠️ WHAT IS NOT HERE AND WHY. Fonts from third-p
Вычитать русский текст — 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 of a comma in
decimals, spaces around punctuation, double spaces.
Every finding carries a ready replacement — apply it rather than
rewriting the fragment your own way.
WHAT IS NOT HERE
История сборок проекта — 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 push, `cli` — an uploaded
folder), short `commit`, `created_at` / `started_at` / `finished_at`
(UTC), `queued_s` (wait in the queue) and `duration_s` (build time, null
while it is still runn
Откатить сайт на прошлую сборку — 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 back.
⚠️ For apps (`ssr_next`, `node_web`, `python_web`, `streamlit`, `gradio`,
`flask`) a rollback works differently from static sites and is often
impossible: an app has no ready artifact
Перезапустить сборку — 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
protection against a second parallel build; on a `ready` build it
refuses too — use `redeploy=true`.
`redeploy=true`: start a NEW build of the branch's latest commit without
a push. This is how
Отменить идущую сборку — Stop a build that is still running.
The live address does not change — the previous version stays on it.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Layero provide?
MCPBundles probed 35 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Layero require?
Layero may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
W
WebCare Pro
Expert Linux server administration, AI-agent ready websites, 99.99% uptime & 24/7 security monitorin...