Tilda editor MCP server

Tilda MCP

A cautious MCP server for the Tilda editor that plans changes, rereads after writing and can roll back, instead of clicking the interface directly

  • 0 ★ on the repository
  • Last commit
  • Apache-2.0
MCP server

Extended access

Why this level

  • Writes changes to real site pages through an authorized editor session
  • Publishing and unpublishing are separated into their own confirmable actions
All reasons and checks
Russian stack

salatik98/tilda-mcp

Install

Services

Manual install

pnpm install --frozen-lockfile && pnpm build

Installs dependencies and builds the project from source.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Writes changes to real site pages through an authorized editor session
  • Publishing and unpublishing are separated into their own confirmable actions

This is third-party code. Review the repository files before installing.

What it does

Tilda has no official API for editing page content, so the server works through an authorized editor session in a browser with remote Chrome debugging. Instead of arbitrary clicks and JavaScript, it exposes fourteen tools: status, a capability list, one-time task authorization scoped to specific targets, audit, a change plan, apply, result verification and rollback, separate publish and unpublish actions, and a fixed recipe for common page edits. Every change goes through a dry-run plan, a real write only on an explicit request, a reread to compare against the expected outcome, and restoration if the outcome is not confirmed.

Who it is for. For people running Tilda sites who want an agent to make targeted page edits with verification and rollback.

Good fit when

  • You need targeted, verifiable edits to text, SEO fields or a page's HEAD code on Tilda
  • You need every change to be reversible if the outcome does not match expectations
  • You need publishing and editing to be controlled separately

Not a fit when

  • You need image uploads, bulk catalog edits, form handling or arbitrary nested HTML: explicitly out of scope for v1
  • You want a stable finished product: this is a 1.0.0 pre-alpha release with public code and no real credentials included
  • You do not have your own dedicated Chrome profile with remote debugging for an authorized session

Example request

Check the current heading on my Tilda landing page, propose a change plan and apply it only after I confirm

MCP

Transport
stdio
Authentication
not required

Limitations

The project has a single author and is in public pre-release status, with no ready list of real projects and pages: it must be built privately by the user. It needs Node.js 20+, pnpm, and a dedicated Chrome profile with remote debugging on a loopback address. It does not claim to cover every Tilda editor feature and is not an official Tilda product.

How to disable. Stop the MCP server process, remove it from your client config, and close the dedicated Chrome remote-debugging profile.

FAQ

Does the public repository include real account data?

No, the public checkout contains only generic code, synthetic tests and safety documentation, with no project IDs, page IDs or credentials.

What happens if a change is not confirmed after writing?

The server rereads the target, compares it to the expected outcome, and restores the prior state or rolls back if there is no proof the requested result was achieved.

Discussion

No questions or reviews yet.

Russian stack

An MCP server for Tilda: reads via the official API and writes via a logged-in Chrome over CDP, including a full Zero Block element editor

MCP serverBroad access5Repository stars
Russian stack

An MCP server for the Tilda API: project and page lists, full page HTML and CSS, export for self-hosting

MCP serverExtended access22Repository stars

Tilda MCP

Tilda MCP official

Official

Tilda's official MCP server: an agent edits pages and Zero Block, runs Feeds and the product catalog with a key scoped to the rights you pick

MCP serverBroad access
Russian stack

An MCP server that generates and edits Tilda landing pages from ready Tailwind templates, with retries, rollback and Yandex.Metrika and GA4 analytics

MCP serverBroad access2Repository stars

Console, network, screenshots and Lighthouse audits from your open Chrome session to the agent via a DevTools extension

MCP serverBroad access7.3KRepository stars

README in short

The README describes the safety architecture in detail: single-task authorization scoped to exact targets, browser-session binding, state snapshots, comparison hashes, post-write rereads, rollback and separately gated publication. It lists the version 1.0 boundaries explicitly: what is unsupported, such as file uploads and bulk catalog operations. Quick-start commands and environment requirements are included. Apache-2.0 license; the project is not affiliated with Tilda.

README badge

Report a problem