MCP server

Layero Official

ru.layero/layero

Checked 25 Oct 2026, 20:29 UTC · Connected to it and listed its tools

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

Website Source

At a glance

Type

MCP server

Publisher

layero.ru (verified by the MCP Registry)

Status

Working at last check

Tools

36

Token cost

About 16,406 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

25 Oct 2026, 20:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.layero]
url = "https://mcp.layero.ru/mcp"

Gemini CLI

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

Cursor

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

VS Code

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

Antigravity

agy mcp add layero https://mcp.layero.ru/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"layero","server_url":"https://mcp.layero.ru/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"layero","server_url":"https://mcp.layero.ru/mcp"}

Tools

• cancel_deploy ~206 tokens
  Stop a build that is still running. The live address does not change — the previous version stays on it.
• check_copy ~396 tokens
  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
• check_domain ~231 tokens
  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.
• check_performance ~349 tokens
  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; a
• check_rules ~294 tokens
  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 at
• connect_analytics Changes accounts · ~308 tokens
  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. C
• connect_domain ~318 tokens
  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
• data_api_grant Changes accounts · ~961 tokens
  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 them t
• data_api_keys ~670 tokens
  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 platform
• data_api_methods ~243 tokens
  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 the g
• data_api_origins ~506 tokens
  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 remov
• data_api_probe ~697 tokens
  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, calls
• data_api_status ~263 tokens
  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. Enabling the API is safe (everything stays closed until access is granted) and goes t
• deploy_logs ~572 tokens
  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 th
• diagnose_deploy ~774 tokens
  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 has
• env_vars ~538 tokens
  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 settl
• import_repo ~1163 tokens
  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
• list_deploys ~338 tokens
  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 pu
• list_domains ~133 tokens
  The project's own domains and their state.
• list_environments ~260 tokens
  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 p
• list_sources ~213 tokens
  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
• my_projects ~344 tokens
  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 p
• project_create ~241 tokens
  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.
• project_settings ~1208 tokens
  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
• publish_landing Sends messages · ~370 tokens
  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`.
• publish_site Sends messages · ~913 tokens
  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 files
• read_site ~392 tokens
  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, an
• refactor_site ~457 tokens
  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
• retry_deploy ~665 tokens
  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 protec
• rollback ~368 tokens
  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 bac
• search_docs ~350 tokens
  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) an
• site_analytics ~231 tokens
  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.
• site_issues ~315 tokens
  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, r
• site_screenshot Browses the web · ~301 tokens
  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
• site_status ~728 tokens
  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 r
• whoami ~90 tokens
  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.

Browse

• GitHub tools
• Domains and DNS
• GitHub and code hosting
• Databases
• Docker and Kubernetes

Related MCP servers

• VibeKit
  Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
• VibeDeploy
  Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.
• The Deployer
  Check if a repo will deploy, plan a deploy to your own cloud, and see status, logs and redeploys.
• Kleap
  Build, edit, publish, and manage websites and web apps with Kleap hosting, domains, and analytics.
• Novence
  Hosted MCP for creating, checking, deploying, and hosting static sites for AI agents.
• Robtex
  DNS, IP, AS, domain reputation, and Lightning Network intelligence (44 tools)
• BorealHost
  Agent-native web hosting — deploy sites, manage DNS, register domains, scale infrastructure
• TaskLite
  tasklite.net: hosted backend, REST API and admin for apps built by AI agents

Badge for your README

[![AptLynx](https://aptlynx.net/badge/ru.layero/layero.svg)](https://aptlynx.net/servers/ru.layero/layero)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents