Layero

This connector has been deprecated

Duplicate listing of the same server under an old namespace. The maintained listing is Layero (ru.layero/layero): same endpoint https://mcp.layero.ru/mcp, current description and tools. The landing-page generator described here was removed in MCP 2.0.

Перезапустить сборку

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
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 changed project settings (`project_settings`) or
environment variables (`env_vars`) get applied. The result goes live the
same way a push to that branch would — on the production branch that is
production, so make sure the person wants that. Projects without a
repository are rebuilt by deploying the folder again
(`npx layero@latest deploy` or `publish_site`).

⚠️ A plain retry makes sense when the cause was external (network,
registry, timeout). If the build failed on the code, a retry gives the
same result: `diagnose_deploy` first, then the fix, and only then a retry.

Input Schema

TableJSON Schema

Name	Required	Description
`branch`	No	Only with `redeploy=true`: the branch to build. Defaults to the production branch.
`deploy`	No	Build id (a UUID from `list_deploys`). Without it the latest build is used. Ignored with `redeploy=true`.
`project`	Yes	The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug.
`redeploy`	No	`true` — build the latest commit of the branch again as a NEW build, whatever state the previous one is in (also `ready`). Same as the «Пересобрать» button in the dashboard. Use it after changing project settings or environment variables, when there is nothing to push. Repository projects only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`project`	Yes
`deploy_id`	Yes
`next_action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 19, 2026

addedInput schema / properties / branch

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only with `redeploy=true`: the branch to build. Defaults to the production branch.",
+  "title": "Branch"
+}

changedInput schema / properties / deploy / description

Previous value: -"Build id (a UUID from `list_deploys`). Without it the latest build is used."New value: +"Build id (a UUID from `list_deploys`). Without it the latest build is used. Ignored with `redeploy=true`."

addedInput schema / properties / redeploy

Added value: +{
+  "default": false,
+  "description": "`true` — build the latest commit of the branch again as a NEW build, whatever state the previous one is in (also `ready`). Same as the «Пересобрать» button in the dashboard. Use it after changing project settings or environment variables, when there is nothing to push. Repository projects only.",
+  "title": "Redeploy",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / deploy / description

Previous value: -"id сборки. Без него берётся самая свежая."New value: +"Build id (a UUID from `list_deploys`). Without it the latest build is used."

changedInput schema / properties / project / description

Previous value: -"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."New value: +"The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug."

AddedAug 3, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes far beyond the single `openWorldHint` annotation. It discloses that refusal on running builds is protection rather than an error, that `redeploy=true` can push resulting changes live on the production branch, that changed `project_settings`/`env_vars` are applied, and that repository-less projects are redeployed via CLI or `publish_site`. This is thorough behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a one-line summary, dedicated paragraphs for the default and redeploy modes, and a warning paragraph. Although it is long, every sentence carries operational information and the key distinction is front-loaded. It is dense but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition covers state constraints, parameter interactions, the non-repository fallback, production impact, and when to use `diagnose_deploy` instead. Since an output schema exists, explaining return values is unnecessary. There are no significant gaps an agent needs for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 4 parameters already have complete descriptions in the schema (100% coverage), so the baseline is 3. The description adds value by explaining how `redeploy` switches between the two execution modes, how `deploy` is ignored when `redeploy=true`, and how `branch` defaults to the production branch. This extra interaction context justifies a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence 'Run a build again — a failed one as is, or the latest commit afresh' clearly states the operation and its two core modes. It is highly specific about the resource (build) and the state conditions, and it distinguishes itself from sibling tools like `diagnose_deploy` by naming them when relevant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when the default mode is allowed (`failed`/`cancelled`) and when it is refused (`queued`/`building`/`ready`) with a pointer to use `redeploy=true`. It also gives clear guidance to run `diagnose_deploy` first for code-related failures and only then retry, providing an explicit when-to-use vs alternative decision path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Layero tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?