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.

Опубликовать сайт (старое имя)

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

Input Schema

TableJSON Schema

Name	Required	Description
`files`	Yes	Same as in `publish_site`: the site files with `index.html` in the root.
`project`	No	Same as in `publish_site`: id of an existing project.
`project_name`	Yes	Same as in `publish_site`: the project slug.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`bytes`	Yes
`error`	No
`files`	Yes
`status`	Yes
`deploy_id`	Yes
`project_id`	Yes
`next_action`	Yes
`project_slug`	Yes
`created_project`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 18, 2026

changedInput schema / properties / files / description

Previous value: -"То же, что у `publish_site`: файлы сайта с `index.html` в корне."New value: +"Same as in `publish_site`: the site files with `index.html` in the root."

changedInput schema / properties / project / description

Previous value: -"То же, что у `publish_site`: id существующего проекта."New value: +"Same as in `publish_site`: id of an existing project."

changedInput schema / properties / project_name / description

Previous value: -"То же, что у `publish_site`: слаг проекта."New value: +"Same as in `publish_site`: the project slug."

Changed3 schema fields changedSep 17, 2026

changedInput schema / properties / files / description

Previous value: -"Файлы сайта целиком, с `index.html` в корне. Пути относительные (`assets/app.css`). Двоичные файлы — с `encoding=\"base64\"`. Не более 200 файлов, 8 МБ всего, 2 МБ на файл."New value: +"То же, что у `publish_site`: файлы сайта с `index.html` в корне."

changedInput schema / properties / project / description

Previous value: -"id существующего проекта — для повторной публикации того же сайта. Без него платформа ищет проект по имени или создаёт новый."New value: +"То же, что у `publish_site`: id существующего проекта."

changedInput schema / properties / project_name / description

Previous value: -"Слаг проекта — строчные латинские буквы, цифры и дефис. Он станет частью адреса сайта. Если проект уже существует, передавай ещё и `project`, иначе платформа заведёт новый."New value: +"То же, что у `publish_site`: слаг проекта."

Changed3 schema fields changedAug 3, 2026

addedInput schema / properties / files / description

Added value: +"Файлы сайта целиком, с `index.html` в корне. Пути относительные (`assets/app.css`). Двоичные файлы — с `encoding=\"base64\"`. Не более 200 файлов, 8 МБ всего, 2 МБ на файл."

addedInput schema / properties / project / description

Added value: +"id существующего проекта — для повторной публикации того же сайта. Без него платформа ищет проект по имени или создаёт новый."

addedInput schema / properties / project_name / description

Added value: +"Слаг проекта — строчные латинские буквы, цифры и дефис. Он станет частью адреса сайта. Если проект уже существует, передавай ещё и `project`, иначе платформа заведёт новый."

Changed1 schema field changedAug 2, 2026

addedInput schema / $defs / FilePayload / properties / encoding

Added value: +{
+  "default": "text",
+  "description": "Use `base64` for binary files — images, fonts, favicons. Text files (html/css/js/svg) stay `text`. A binary sent as text is silently corrupted.",
+  "enum": [
+    "text",
+    "base64"
+  ],
+  "title": "Encoding",
+  "type": "string"
+}

AddedJul 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description discloses deprecation status, compatibility window, and eventual removal — useful context beyond the minimal `openWorldHint` annotation. However, the actual behavior is only conveyed via 'same behaviour' as `publish_site`, without detailing what the operation does, side effects, or failure modes. For a deprecated compatibility alias this is acceptable but not fully transparent.

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 compact, front-loads the critical deprecation directive, and has no filler. Every sentence contributes to the deprecation message and usage guidance. The structure is ideal for a tool that exists only as a compatibility shim.

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

Completeness4/5

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

For a deprecated alias, the description is nearly complete: it identifies the replacement, explains why it still exists, and gives a removal timeline. The only gap is that it does not describe the underlying publish behavior, but that is intentionally delegated to `publish_site`, and the provided schema plus output schema cover invocation details.

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

Parameters3/5

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

The schema already provides descriptions for all parameters, so the baseline is 3. The top-level description adds no parameter information itself; the schema descriptions reference `publish_site` and give brief explanations like 'the project slug', but they rely on the sibling tool for full meaning. This is adequate but not exceptional.

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 description immediately identifies the tool as deprecated and points to `publish_site` as the replacement, which clearly distinguishes it from the sibling list. It states the intended action ('use publish_site') and the resource it refers to, so an agent can correctly decide not to invoke this tool.

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 to use this tool (legacy configs/prompts written before 17.09.2026) and when not to use it (new instructions must call `publish_site`). It also tells that the tool will be removed in the next release, providing complete routing guidance.

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?