Tilda MCP with bulk editing via CDP
tilda-mcp-cdp
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
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Write tools publish changes to the live site immediately by default
- Replacements use regular expressions, an imprecise pattern can change more than intended
Install
Manual install
git clone https://github.com/skiddgoddamn/tilda-mcp-cdp.git && cd tilda-mcp-cdp && npm install && npm run buildBuild from source, no ready npm package.
This is third-party code. Review the repository files before installing.
What it does
Tilda's official API is read-only, so the server adds 11 write tools that drive your already logged-in Chrome via the debug protocol (CDP): connection and session checks, setting the Yandex Metrika ID in project settings, regex replacement inside T123 HTML code blocks and Zero Block links, publishing a page, and checking live HTML for substrings present or absent. A separate group of five tools gives a full Zero Block element editor based on the artboard model: list elements with their real ids and fields, patch them with deep-merged JSON (text, color, font, position, link), add an element by cloning an existing one, delete an element, and regex-replace text across the whole block model. Five read tools (projects, pages, export) go through Tilda's official API and need no browser.
Who it is for. For people running many similar Tilda landing pages who want to bulk-edit counters, links and text in one command instead of clicking through every site.
Good fit when
- You need to bulk-change the Metrika counter or a button link across dozens of identical landing pages
- You need to precisely edit a Zero Block element (text, color, position) by id or a text fragment
- You need to verify that a specific string appeared or disappeared on the live site after an edit
Not a fit when
- You only need reading and export: the five official tools are enough, no CDP Chrome required
- You are not ready to keep a separate Chrome profile with a debug port permanently logged into Tilda: this is required for every write tool
Example request
Set Metrika ID 109756541 on project 23943806 and publish its pagesLimitations
Every write tool requires a separately running Chrome with a debug port on a dedicated profile logged into Tilda, and none work without it. Replacements everywhere use regular expressions rather than exact matches, so a pattern mistake can hit more than intended. Write actions publish the page immediately by default (publish: true). The Zero Block field schema is not hardcoded and can differ between blocks, so zero_get_elements must always be called first before editing.
How to disable. Close the debug Chrome instance and remove the tilda server from your MCP client config.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| TILDA_PUBLIC_KEY required | Public key for reading, from Tilda account settings |
| TILDA_SECRET_KEY required, secret | Secret key for reading |
| TILDA_CDP_URL | CDP address of the running debug Chrome, required for all write tools, defaults to http://localhost:9222 |
Security check
- Write tools publish changes to the live site immediately by default
- Replacements use regular expressions, an imprecise pattern can change more than intended
README in short
The README explains the reason: Tilda's official API is read-only, so the server adds an action layer by driving a logged-in Chrome via CDP. It covers requirements, installation, starting a debug Chrome on a separate profile, the Streamable HTTP mode, all 16 tools across three groups (read, actions, Zero Block editor), and a "how it works under the hood" section with details like saving via POST /zero/submit/ and bypassing cache when checking live HTML.
FAQ
Why can't the site be edited with the official API alone?
Tilda's official API is read-only; any change (counters, links, publishing) is officially available only in the UI, so the server drives a logged-in Chrome directly instead.
How do I find the real Zero Block element ids before editing?
Call zero_get_elements first, it shows the type, text, links, geometry and every field of the block's elements.
Related
Official Claude Code plugin from the Next.js repo: adopting Cache Components and Partial Prefetching, and verifying changes on a running dev server
Official shadcn/ui skill and MCP server: the agent searches registries, adds components via the CLI and follows the library's rules
A frontend design skill with 23 commands, live browser iteration and 61 detector rules for common AI-generated UI tells
Vercel Agent Skills
Agent Skills
Vercel's skills: React and Next.js performance, UI guideline audits, React Native, component composition and deploys