layero

endpoint

https://mcp.layero.ru/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing

karma

0 · newcomer

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• publish_site auth-required never probed

  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 (images, fonts) must come with `encoding="base64"`; sent as text they are silently corrupted. Do NOT use it for a project with a connected repository (`site_status` shows one): the next git push would overwrite what you published. Publishing without a Layero account is not possible from here — the server requires sign-in. For that case there is the CLI: `npx layero@latest deploy --claim` deploys first and lets the person claim the site later. An empty project for a future publish is created with `project_create`. A project that still needs a build step (Vite, Next, Astro — anything where the answer is `npm run build`) does NOT go here: publish its build output, or tell the user to run `npx layero@latest deploy`, which builds on our side. Send the ACTUAL file contents: the server does not remember the bundle between calls. If the user edited the text after generation, pass the current versions, or what gets published is what used to be there. Pass `project` (the id of an existing project) when republishing the same site; without it the platform finds a project with that name or creates a new one. Returns as soon as the build finishes, or after ~40s with `status` `building` and the `deploy_id` — the build keeps going on its own. Never call this tool a second time to "retry" a build that is still running: that starts a SECOND build. Follow `next_action`.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566

  {
    "type": "object",
    "$defs": {
      "FilePayload": {
        "type": "object",
        "title": "FilePayload",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "title": "Path"
          },
          "content": {
            "type": "string",
            "title": "Content"
          },
          "encoding": {
            "enum": [
              "text",
              "base64"
            ],
            "type": "string",
            "title": "Encoding",
            "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."
          }
        }
      }
    },
    "title": "publish_siteArguments",
    "required": [
      "files",
      "project_name"
    ],
    "properties": {
      "files": {
        "type": "array",
        "items": {
          "$ref": "#/$defs/FilePayload"
        },
        "title": "Files",
        "description": "The whole site, with `index.html` in the root. Paths are relative (`assets/app.css`). Binary files go with `encoding=\"base64\"`. At most 200 files, 8 MB in total, 2 MB per file."
      },
      "project": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project",
        "default": null,
        "description": "id of an existing project — to publish the same site again. Without it the platform looks the project up by name or creates a new one."
      },
      "project_name": {
        "type": "string",
        "title": "Project Name",
        "description": "Project slug — lowercase Latin letters, digits and hyphens. It becomes part of the site address. If the project already exists, pass `project` as well, otherwise the platform creates a new one."
      }
    }
  }

  arguments 66 lines copy
• data_api_grant auth-required never probed

  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 to the person. With apply=true a client with forms asks the person itself; without forms get consent in the chat and pass confirmed=true together with expected_sql from the preview. Methods you do not name keep their current level. Exactly the shown commands are applied: if the grants changed meanwhile, the platform refuses — show the new ones. Needs a token with the admin scope, for the preview too.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163

  {
    "type": "object",
    "title": "data_api_grantArguments",
    "required": [
      "object"
    ],
    "properties": {
      "get": {
        "anyOf": [
          {
            "enum": [
              "closed",
              "visitor",
              "user",
              "server"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Get",
        "default": null,
        "description": "Reading the table. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key."
      },
      "call": {
        "anyOf": [
          {
            "enum": [
              "closed",
              "visitor",
              "user",
              "server"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Call",
        "default": null,
        "description": "Calling the function. closed — nobody; visitor — any site visitor; user — people signed in to the app; server — only a server holding the secret key."
      },
      "post": {
        "anyOf": [
          {
            "enum": [
              "closed",
              "visitor",
              "user",
              "server"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Post",
        "default": null,
        "description": "Inserting rows into the table. Same levels as `get`."
      },
      "apply": {
        "type": "boolean",
        "title": "Apply",
        "default": false,
        "description": "false (default) — only show the commands. true — apply them after the person's consent."
      },
      "patch": {
        "anyOf": [
          {
            "enum": [
              "closed",
              "visitor",
              "user",
              "server"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Patch",
        "default": null,
        "description": "Updating rows of the table. Same levels as `get`."
      },
      "delete": {
        "anyOf": [
          {
            "enum": [
              "closed",
              "visitor",
              "user",
              "server"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Delete",
        "default": null,
        "description": "Deleting rows of the table. Same levels as `get`."
      },
      "object": {
        "type": "string",
        "title": "Object",
        "description": "A table `schema.name` or a function `schema.name`; for an overloaded function — `schema.name(types)`. As listed by data_api_methods."
      },
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "confirmed": {
        "type": "boolean",
        "title": "Confirmed",
        "default": false,
        "description": "true — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent."
      },
      "expected_sql": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Expected Sql",
        "default": null,
        "description": "The `sql` commands from the preview answer that the person saw. Required with confirmed=true: only these are applied."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      }
    }
  }

  arguments 163 lines copy
• site_status auth-required never probed

  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 `/` route answers with its own 404: that is a running app, not a broken site — check a real route with `path`. `answered_by` tells who replied: `site`, `platform` (a Layero screen, named in `platform_screen`: `unavailable`, `coming-soon`, `starting`, `not-found`, `suspended`) or `none` (no response). Redirects are not followed: `redirect_to` shows the target. Waiting for a build: while the latest build is running the answer carries `poll_after_s` — call again after that many seconds. Or pass `wait_s` and the server waits for the build itself (mind your client's tool-call timeout, see the argument). `waited_s` says how long the call waited. Static sites: `served_fallback: true` means the requested `path` was answered with the HOME page (a missing file is replaced by `index.html` with code 200) — the address answers, but this page does not exist.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "title": "site_statusArguments",
    "required": [
      "project"
    ],
    "properties": {
      "path": {
        "type": "string",
        "title": "Path",
        "default": "/",
        "description": "Path to check on the site, from its root. Default `/`. For an API server with no `/` route pass a route that exists, e.g. `/api/health` or `/healthz`."
      },
      "wait_s": {
        "type": "integer",
        "title": "Wait S",
        "default": 0,
        "description": "Wait for a running build: if the latest build is queued/building, the call holds until it finishes or `wait_s` seconds pass, then answers as usual. Default 0 — answer at once. At most 120. 🚨 Your client has its own tool-call timeout, often 60 s (Cursor, Codex): stay under it — 45 is safe everywhere — or the call is cut on your side while the build carries on. Still building afterwards → call again."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 26 lines copy
• whoami auth-required never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "whoamiArguments",
    "properties": {}
  }

  arguments 5 lines copy
• retry_deploy auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546

  {
    "type": "object",
    "title": "retry_deployArguments",
    "required": [
      "project"
    ],
    "properties": {
      "branch": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Branch",
        "default": null,
        "description": "Only with `redeploy=true`: the branch to build. Defaults to the production branch."
      },
      "deploy": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Deploy",
        "default": null,
        "description": "Build id (a UUID from `list_deploys`). Without it the latest build is used. Ignored with `redeploy=true`."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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": {
        "type": "boolean",
        "title": "Redeploy",
        "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."
      }
    }
  }

  arguments 46 lines copy
• search_docs auth-required never probed

  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 matching every word ranks above one repeating a single word. The index is the site's own search index, refreshed hourly.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "title": "search_docsArguments",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 5,
        "maximum": 20,
        "minimum": 1,
        "description": "How many results to return, 1–20."
      },
      "query": {
        "type": "string",
        "title": "Query",
        "description": "What to look for, in words: «environment variables», «layero.json node version», «rollback», «monorepo root directory». The docs are in Russian; both Russian and English queries work — common English platform terms are matched to their Russian counterparts."
      }
    }
  }

  arguments 22 lines copy
• my_projects auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "title": "my_projectsArguments",
    "properties": {
      "repo": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Repo",
        "default": null,
        "description": "Only projects built from this repository: `owner/repo` (case-insensitive; a full repository URL works too). Use it to see whether a repository is already linked and from which folders. `limit` applies after the filter."
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 30,
        "description": "How many of the most recent projects to return. The default of 30 is almost always enough; raise it (up to 100) only when the user is looking for an old site that is not in the list."
      }
    }
  }

  arguments 25 lines copy
• data_api_methods auth-required 1h ago

  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 gateway sees them.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "title": "data_api_methodsArguments",
    "properties": {
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      }
    }
  }

  arguments 32 lines copy
• data_api_status auth-required 1h ago

  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. The API cannot be enabled with a tool: enabling gives the database a public address, and that is the person's decision in the dashboard.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "title": "data_api_statusArguments",
    "properties": {
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      }
    }
  }

  arguments 32 lines copy
• connect_domain auth-required never probed

  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` to `shop.example.com` itself.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "connect_domainArguments",
    "required": [
      "project",
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "title": "Domain",
        "description": "The domain without scheme or slash: `example.ru` or `www.example.ru`."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• list_sources auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "title": "list_sourcesArguments",
    "properties": {
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the account's only organization, or the personal one; if there are several and none is personal, the tool lists the slugs."
      }
    }
  }

  arguments 19 lines copy
• import_repo auth-required never probed

  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 a later change in the repository is picked up. Only a decision is pinned — the app folder of a monorepo and the package manager named in `layero.json`. Until 2.1.1 the project stayed in `pending_setup` while the answer promised a build that never started. Two shapes, same as the CLI: GitHub goes through the App installation (project and webhook in one call); other providers create the project first and then connect the source — that step reports whether the webhook could be registered. If the provider is not connected, the result says `needs_connection` with the dashboard address: the person connects the token there, never through the chat. Monorepo: one project builds one app folder — pass `root_directory`. Several apps in one repository are several projects, one call each, with different `root_directory` and `name`. If the repository is already linked and the call would duplicate an existing project (same folder, or no `root_directory` given), nothing is created: the result is `already_linked` with `linked_projects` — slug, url, root_directory and branch of every project built from this repository. On `created`, `linked_projects` lists the OTHER projects already built from the same repository; `linked_projects_checked: true` says the check was made, so an empty list means there are none (`my_projects(repo=…)` answers the same question later). When the root has no app and detection sees a frontend + backend pair, `app_dir_candidates` names the folders.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778

  {
    "type": "object",
    "title": "import_repoArguments",
    "required": [
      "provider",
      "repo"
    ],
    "properties": {
      "name": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Name",
        "default": null,
        "description": "Project name; the slug and the address are derived from it. Defaults to the repository name — for a second app from the same monorepo give a distinct name."
      },
      "repo": {
        "type": "string",
        "title": "Repo",
        "description": "Repository path at the provider: `owner/repo`; GitLab paths may be nested (`group/sub/project`). The form `gitverse:owner/repo` is accepted too."
      },
      "branch": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Branch",
        "default": null,
        "description": "Production branch. Defaults to the repository's default branch."
      },
      "deploy": {
        "type": "boolean",
        "title": "Deploy",
        "default": true,
        "description": "Finish the setup wizard and start the first build right away. The framework, build command and output folder are not pinned: the builder detects them from the repository on every build (`layero.json` overrides). `false` leaves the project in the setup wizard: no builds until the person completes the setup in the dashboard."
      },
      "provider": {
        "type": "string",
        "title": "Provider",
        "description": "Provider: github, gitverse, gitlab, gitflic or sourcecraft."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the account's only organization, or the personal one; if there are several and none is personal, the tool lists the slugs."
      },
      "root_directory": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Root Directory",
        "default": null,
        "description": "Monorepo: the app folder inside the repository, relative to its root — `apps/web`, `frontend`. Omit it for an app in the repository root (if the root has no app and exactly one subfolder does, that folder is picked automatically). A repository already linked to a project can be imported again ONLY with a `root_directory` that no linked project uses."
      }
    }
  }

  arguments 78 lines copy
• list_environments auth-required never probed

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "title": "list_environmentsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 14 lines copy
• project_create auth-required never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "project_createArguments",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "title": "Name",
        "description": "Project name; the slug — the first label of `<slug>.layero.app` — is derived from it."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the account's only organization, or the personal one; if there are several and none is personal, the tool lists the slugs."
      }
    }
  }

  arguments 27 lines copy
• diagnose_deploy auth-required never probed

  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 already picked out what matters. Read `verdict` and the summary, fix the code, deploy again — you close this loop yourself, without involving the person. `build_facts` — how it was built: `project_type`, `framework`, `node_version`, `package_manager`, `install`, `build`, `output` (each with its origin in parentheses: default, auto-detected, layero.json, dashboard …), `source` (`git` / `cli`), `root_directory`, `queued_s`, `duration_s`. Apps built into a container (`node_web`, `python_web`, `ssr_next`, full-stack) also get `runtime_kind`, `start` (the start command), `port`, `env` and, for full-stack, `fullstack` / `fullstack_frontend`. A value marked `(as built)` is the platform's record of this very build; `(current settings: …)` is what the project settings resolve to now, not a fact about this build. A missing key means the platform did not report that fact — on a failed build often because it did not get that far, on a `ready` build it just is not recorded (static builds print more than container builds); it is not a sign of a problem. `sources_note` appears when a value is marked `(from dashboard)` / `(from hint)`: that is «saved in the project settings», by a person or by import-time detection — the platform does not record which. `candidate_app_dirs` is filled when the builder found several app folders in a monorepo and needs a `root_directory`. Three log excerpts, all untrusted: `build_log_excerpt` — the build itself; `launch_log_excerpt` — the platform's lines about starting the app after the build (container launch, readiness probe, wake-ups), empty for static sites; `runtime_log_excerpt` — what the app printed. `next_action` is the instruction for you. `next_actions` is a separate, machine-readable list of platform codes, possibly empty: `wait`, `poll_status`, `fix_config`, `fix_code`, `fix_runtime`, `check_env`, `inspect_logs`, `retry_deploy`, `runtime_idle` (the app is scaled to zero — normal, it wakes on the next request).

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "diagnose_deployArguments",
    "required": [
      "project"
    ],
    "properties": {
      "deploy": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Deploy",
        "default": null,
        "description": "id of a specific build (a UUID from `list_deploys`). Without it the latest build is used — the one that reflects the project's current state."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 27 lines copy
• env_vars auth-required never probed

  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. `set` does not require knowing the other variables — the platform keeps them. `unset` removes only the named ones. A change needs a new deploy: variables are picked up at build time, not on the fly. Say so, or the user will think nothing happened.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657

  {
    "type": "object",
    "title": "env_varsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "keys": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Keys",
        "default": null,
        "description": "For `action=\"unset\"`: names of the variables to remove."
      },
      "action": {
        "enum": [
          "list",
          "set",
          "unset"
        ],
        "type": "string",
        "title": "Action",
        "default": "list",
        "description": "`list` — show the names (values are never returned), `set` — set the variables from `values`, `unset` — remove the variables listed in `keys`."
      },
      "values": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Values",
        "default": null,
        "description": "For `action=\"set\"`: name → value pairs. The project's other variables are kept — no need to send them again."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 57 lines copy
• project_settings auth-required never probed

  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 > project settings > detection > framework default: a field with `policy: "locked_by_file"` is set by `layero.json`, and changing the project setting will not change the build — edit the file instead. `update` CHANGES HOW THE PROJECT IS BUILT — ask the person first unless they asked for exactly this change. Prefer `layero.json` in the repository for anything that should live with the code; use this tool for what the file cannot hold (`root_directory`, `project_type`) and for projects you cannot push to. Nothing is rebuilt by the update itself: apply it with `retry_deploy(redeploy=true)` or a push.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177

  {
    "type": "object",
    "title": "project_settingsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "port": {
        "anyOf": [
          {
            "type": "integer",
            "maximum": 65535,
            "minimum": 0
          },
          {
            "type": "null"
          }
        ],
        "title": "Port",
        "default": null,
        "description": "Container apps: the port the app listens on. `0` resets to the default."
      },
      "action": {
        "enum": [
          "get",
          "update"
        ],
        "type": "string",
        "title": "Action",
        "default": "get",
        "description": "`get` — show the build settings and what they resolve to. `update` — change the settings passed in the other arguments; arguments you omit stay as they are."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      },
      "framework": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Framework",
        "default": null,
        "description": "Framework preset for a static build: `vite`, `nextjs`, `astro`, `generic`, `static` …"
      },
      "force_type": {
        "type": "boolean",
        "title": "Force Type",
        "default": false,
        "description": "Set `project_type` even though the platform detected another type."
      },
      "node_version": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Node Version",
        "default": null,
        "description": "Node major, e.g. `22`. `\"\"` resets to auto-detection."
      },
      "project_type": {
        "anyOf": [
          {
            "enum": [
              "spa",
              "ssr_next",
              "node_web",
              "python_web",
              "streamlit",
              "gradio",
              "flask"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project Type",
        "default": null,
        "description": "How the project runs: `spa` — static files (any static framework); the others — an app in a container. The platform checks the repository and may object (409): then re-read the objection and pass `force_type=true` only if the person insists."
      },
      "build_command": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Build Command",
        "default": null,
        "description": "Build command, whole: `npm run build`."
      },
      "start_command": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Start Command",
        "default": null,
        "description": "Container apps: start command, listening on `0.0.0.0` and `$PORT`. `\"\"` resets to detection by entry point."
      },
      "root_directory": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Root Directory",
        "default": null,
        "description": "App folder inside the repository (`apps/web`). `\"\"` resets to the repository root. Changing it clears the detected framework and commands of the old folder."
      },
      "install_command": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Install Command",
        "default": null,
        "description": "Install command. `\"\"` resets to auto-detection by lockfile."
      },
      "package_manager": {
        "anyOf": [
          {
            "enum": [
              "npm",
              "yarn",
              "pnpm",
              "bun"
            ],
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Package Manager",
        "default": null,
        "description": "Package manager override."
      },
      "output_directory": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Output Directory",
        "default": null,
        "description": "Folder that holds `index.html` AFTER the build (`dist`, `build`, `dist/client`)."
      }
    }
  }

  arguments 177 lines copy
• connect_analytics auth-required never probed

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

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "connect_analyticsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "branch": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Branch",
        "default": null,
        "description": "The branch whose traffic is counted. Defaults to the production branch; pass it only when the user asks to track a preview branch."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 27 lines copy
• site_analytics auth-required never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "title": "site_analyticsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "period": {
        "enum": [
          "7d",
          "30d",
          "90d"
        ],
        "type": "string",
        "title": "Period",
        "default": "7d",
        "description": "Observation window: 7, 30 or 90 days."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 25 lines copy
• check_performance auth-required never probed

  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 measurement in parallel — it will occupy the queue and add nothing.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "check_performanceArguments",
    "required": [
      "project"
    ],
    "properties": {
      "wait": {
        "type": "boolean",
        "title": "Wait",
        "default": true,
        "description": "Wait for the measurement result (tens of seconds) or return at once. `false` — when the user needs the run started, not its result."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• check_domain auth-required never probed

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "check_domainArguments",
    "required": [
      "project",
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "title": "Domain",
        "description": "The domain without scheme — exactly the one that was connected."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• list_domains auth-required never probed

  The project's own domains and their state.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "title": "list_domainsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 14 lines copy
• read_site auth-required never probed

  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. The full source is on the user's disk. `served_fallback=true` means this path was answered with the home page: there is no page at this address, and the storage answered the missing key with its `index.html` and a 200. Do not take that for success.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "read_siteArguments",
    "required": [
      "project"
    ],
    "properties": {
      "path": {
        "type": "string",
        "title": "Path",
        "default": "/",
        "description": "Page path from the site root: `/`, `/about`, `/blog/post`. A page, not a file — the tool refuses files."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• site_screenshot auth-required never probed

  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 "just in case": for "what is wrong with the site" `site_issues` is cheaper and more specific.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "title": "site_screenshotArguments",
    "required": [
      "project"
    ],
    "properties": {
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 14 lines copy
• site_issues auth-required never probed

  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 main ones and ask whether to fix them.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "site_issuesArguments",
    "required": [
      "project"
    ],
    "properties": {
      "path": {
        "type": "string",
        "title": "Path",
        "default": "/",
        "description": "Page path from the site root. Defaults to the home page."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• refactor_site auth-required never probed

  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-party hosts, re-encoding images to webp and untangling inline styles are NOT included: they need the files themselves, which the server does not have, or a judgement about the intended look. `site_issues` names those problems — with a location and an explanation; whoever holds the files fixes them. The gain is measured with `check_performance` BEFORE and AFTER the publish. A difference under three points is measurement noise, not an improvement — say so.

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "title": "refactor_siteArguments",
    "required": [
      "html",
      "fix"
    ],
    "properties": {
      "fix": {
        "enum": [
          "meta",
          "lazy_images"
        ],
        "type": "string",
        "title": "Fix",
        "description": "`meta` — fill in lang and Open Graph markup from what the page already says. `lazy_images` — defer loading of images below the first screen (the first image is left alone: LCP is measured on it)."
      },
      "html": {
        "type": "string",
        "title": "Html",
        "description": "The contents of `index.html` — the file on the user's disk. Read the file yourself and pass it here."
      }
    }
  }

  arguments 24 lines copy
• list_deploys auth-required never probed

  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 running), `failure_stage` for failed ones, `is_active` — the build now served on the canonical address.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "list_deploysArguments",
    "required": [
      "project"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 10,
        "description": "How many of the latest builds to return. Default 10, at most 50."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 20 lines copy
• rollback auth-required never probed

  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 to simply switch to. If the platform refuses, explain that to the person plainly and suggest rebuilding the earlier commit — do not repeat the call.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "rollbackArguments",
    "required": [
      "project"
    ],
    "properties": {
      "deploy": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Deploy",
        "default": null,
        "description": "id of the build to roll back to. Without it the platform takes the nearest suitable earlier one."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 27 lines copy
• cancel_deploy auth-required never probed

  Stop a build that is still running. The live address does not change — the previous version stays on it.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "title": "cancel_deployArguments",
    "required": [
      "project"
    ],
    "properties": {
      "deploy": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Deploy",
        "default": null,
        "description": "Build id (a UUID from `list_deploys`). Without it the latest build is used."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      }
    }
  }

  arguments 27 lines copy
• deploy_logs auth-required never probed

  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 the app behaves rather than in a failure. You get the TAIL. `truncated` says earlier lines were dropped; do not present the tail as the whole log. For build logs, package-manager network chatter is hidden BEFORE the tail is cut, so the tail holds meaningful lines; `noise_hidden` says how many were hidden and `include_noise=true` shows them.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849

  {
    "type": "object",
    "title": "deploy_logsArguments",
    "required": [
      "project"
    ],
    "properties": {
      "kind": {
        "enum": [
          "build",
          "runtime"
        ],
        "type": "string",
        "title": "Kind",
        "default": "build",
        "description": "`build` — what the build printed. `runtime` — what the app itself prints (apps only, not static sites)."
      },
      "tail": {
        "type": "integer",
        "title": "Tail",
        "default": 100,
        "description": "How many of the last lines to return, at most 200."
      },
      "deploy": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Deploy",
        "default": null,
        "description": "Build id (a UUID from `list_deploys`). Without it the latest build is used."
      },
      "project": {
        "type": "string",
        "title": "Project",
        "description": "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."
      },
      "include_noise": {
        "type": "boolean",
        "title": "Include Noise",
        "default": false,
        "description": "Build logs only. By default the package manager's network chatter (`npm http fetch …`, `npm http cache …`, `npm timing/sill/verb …` — one line per downloaded package, often three quarters of the log) is hidden and counted in `noise_hidden`. `true` returns the log as is — for registry or network problems."
      }
    }
  }

  arguments 49 lines copy
• publish_landing auth-required never probed

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

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566

  {
    "type": "object",
    "$defs": {
      "FilePayload": {
        "type": "object",
        "title": "FilePayload",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "title": "Path"
          },
          "content": {
            "type": "string",
            "title": "Content"
          },
          "encoding": {
            "enum": [
              "text",
              "base64"
            ],
            "type": "string",
            "title": "Encoding",
            "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."
          }
        }
      }
    },
    "title": "publish_landingArguments",
    "required": [
      "files",
      "project_name"
    ],
    "properties": {
      "files": {
        "type": "array",
        "items": {
          "$ref": "#/$defs/FilePayload"
        },
        "title": "Files",
        "description": "Same as in `publish_site`: the site files with `index.html` in the root."
      },
      "project": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project",
        "default": null,
        "description": "Same as in `publish_site`: id of an existing project."
      },
      "project_name": {
        "type": "string",
        "title": "Project Name",
        "description": "Same as in `publish_site`: the project slug."
      }
    }
  }

  arguments 66 lines copy
• data_api_keys auth-required never probed

  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 does not store secret keys. Hand it to the person for their server and do not repeat it afterwards. Revoking breaks everyone who uses the key — including the site, if the key is baked into its build (`in_build`). Issuing and revoking need a token with the admin scope.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103

  {
    "type": "object",
    "title": "data_api_keysArguments",
    "properties": {
      "key": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Key",
        "default": null,
        "description": "For revoke: id or prefix of the key from the list."
      },
      "kind": {
        "enum": [
          "public",
          "secret"
        ],
        "type": "string",
        "title": "Kind",
        "default": "public",
        "description": "For issue: public — for the site (lives in the browser), secret — for a server only."
      },
      "label": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Label",
        "default": null,
        "description": "For issue: a label to recognise the key by in the list."
      },
      "action": {
        "enum": [
          "list",
          "issue",
          "revoke"
        ],
        "type": "string",
        "title": "Action",
        "default": "list",
        "description": "`list` — keys with prefixes, no values; `issue` — issue a key, its value is returned ONCE; `revoke` — revoke the key named in `key`."
      },
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "confirmed": {
        "type": "boolean",
        "title": "Confirmed",
        "default": false,
        "description": "true — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      },
      "expires_in_days": {
        "anyOf": [
          {
            "enum": [
              30,
              90,
              365
            ],
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Expires In Days",
        "default": null,
        "description": "For issue: lifetime in days; without it the key never expires."
      }
    }
  }

  arguments 103 lines copy
• data_api_origins auth-required never probed

  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 removing need the person's consent; a removed site is refused on every request. Needs a token with the admin scope.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475

  {
    "type": "object",
    "title": "data_api_originsArguments",
    "properties": {
      "url": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Url",
        "default": null,
        "description": "For add and remove: the site origin with scheme, `https://shop.example`."
      },
      "note": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Note",
        "default": null,
        "description": "For add: why the site was added."
      },
      "action": {
        "enum": [
          "list",
          "add",
          "remove"
        ],
        "type": "string",
        "title": "Action",
        "default": "list",
        "description": "`list` — addresses of the database's projects and the manually added ones; `add` — allow a site; `remove` — remove a site."
      },
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "confirmed": {
        "type": "boolean",
        "title": "Confirmed",
        "default": false,
        "description": "true — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      }
    }
  }

  arguments 75 lines copy
• data_api_probe auth-required never probed

  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 from the database to the outside, session locks or the daily call quota. The answer is real: grants, row policies and refusals are the same the site will see. Needs a token with the admin scope.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123

  {
    "type": "object",
    "title": "data_api_probeArguments",
    "required": [
      "method",
      "path"
    ],
    "properties": {
      "body": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": true
          },
          {
            "type": "array",
            "items": {}
          },
          {
            "type": "null"
          }
        ],
        "title": "Body",
        "default": null,
        "description": "Body for POST and PATCH."
      },
      "path": {
        "type": "string",
        "title": "Path",
        "description": "Path from the database address: `/rest/v1/products`, `/rest/v1/rpc/order_create` or `/whoami` (GET only)."
      },
      "role": {
        "enum": [
          "visitor",
          "user",
          "server"
        ],
        "type": "string",
        "title": "Role",
        "default": "visitor",
        "description": "On whose behalf: visitor — a visitor with the public key, user — a signed-in user (needs user_id), server — the secret key."
      },
      "query": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Query",
        "default": null,
        "description": "Query parameters, PostgREST style: {\"select\": \"id,title\", \"price\": \"gt.100\"}."
      },
      "method": {
        "enum": [
          "GET",
          "POST",
          "PATCH",
          "DELETE"
        ],
        "type": "string",
        "title": "Method",
        "description": "HTTP method."
      },
      "schema": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Schema",
        "default": null,
        "description": "The table's schema: api, public or app. Without it the name is looked up in the order api → public → app — pass it when tables with the same name exist in several schemas. Not needed for functions and /whoami."
      },
      "user_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "User Id",
        "default": null,
        "description": "For role=user: id of the app user."
      },
      "database": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Database",
        "default": null,
        "description": "The database: name, slug or id. Without it — the organization's only database with the Data API enabled."
      },
      "organization": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Organization",
        "default": null,
        "description": "Organization slug. Without it — the only one, or the personal one."
      }
    }
  }

  arguments 123 lines copy
• check_copy unknown 1h ago

  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. Plain style, sentence length, officialese, signs of AI slop — that is judgement, and it lives in the `layero://editorial/ru` resource. Read it when asked to "make the text better" rather than "fix the typography".

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "type": "object",
    "title": "check_copyArguments",
    "properties": {
      "path": {
        "type": "string",
        "title": "Path",
        "default": "/",
        "description": "Page path when checking a project. Defaults to the home page."
      },
      "text": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Text",
        "default": null,
        "description": "The text to check. Either this or `project` — exactly one of them."
      },
      "project": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Project",
        "default": null,
        "description": "Project slug: check the copy of the PUBLISHED page. Handy when editing someone's site, or your own after a publish."
      }
    }
  }

  arguments 38 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.