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
`rules_warnings`	No
`created_project`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedOutput schema / $defs

Added value: +{
+  "RulesWarning": {
+    "properties": {
+      "explanation": {
+        "title": "Explanation",
+        "type": "string"
+      },
+      "rule": {
+        "title": "Rule",
+        "type": "string"
+      },
+      "title": {
+        "title": "Title",
+        "type": "string"
+      },
+      "url": {
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "required": [
+      "rule",
+      "title",
+      "explanation",
+      "url"
+    ],
+    "title": "RulesWarning",
+    "type": "object"
+  }
+}

addedOutput schema / properties / rules_warnings

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/RulesWarning"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Rules Warnings"
+}

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/5.0

Behavior3/5

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

With only openWorldHint declared, the description carries the behavioral burden, and it discloses the deprecation lifecycle and removal timeline, which is genuinely useful context. However, it punts on what the operation actually does ('same behaviour') rather than stating that it deploys/publishes files, so side effects and auth expectations remain undocumented.

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?

Three short sentences, front-loaded with the DEPRECATED marker and the replacement name, followed by the reason and deadline. Every sentence earns its place with no filler.

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?

An output schema exists so return values need no explanation, and the description fully covers the deprecation contract an agent needs. The only shortfall is that it does not independently describe the publishing behaviour, relying on the agent to consult `publish_site` instead.

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?

Schema description coverage is 100% and every parameter (files, project, project_name) already carries its own description, so the baseline is 3. The description adds nothing parameter-specific beyond asserting the arguments match `publish_site`.

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

Purpose4/5

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

The description immediately identifies the tool as a deprecated alias that behaves identically to `publish_site`, which lets an agent distinguish it from every sibling. It never states the actual function (publishing a site) directly, delegating that to the sibling reference and the title, so it is clear but one step removed from a self-contained verb+resource statement.

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?

It gives explicit when-to-use ('kept for one release so that configs and prompts written before 17.09.2026 keep working'), when-not-to-use ('new instructions must call publish_site'), and names the replacement. Nothing about tool selection is left to inference.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?