Tilda MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TILDA_PUBLIC_KEY | Yes | Your Tilda public key | |
| TILDA_SECRET_KEY | Yes | Your Tilda secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectsA | Получить список проектов Tilda. |
| get_project_infoA | Получить подробную информацию о проекте Tilda (домен, настройки экспорта). Опц. webconfig=htaccess|nginx — пример конфига веб-сервера. |
| get_pagesB | Получить список страниц проекта Tilda. |
| get_pageA | Получить полную страницу Tilda (HTML с , CSS, JS; ссылки на Tilda CDN). metadata_only=true — без html/css/js. |
| get_page_bodyA | Получить только тело страницы Tilda (HTML без ; ссылки на Tilda CDN) — для быстрого чтения/preview. metadata_only=true — без html/css/js. |
| get_page_exportA | Экспорт полной страницы Tilda для самостоятельного хостинга (HTML с + локализованные ассеты {from,to}). metadata_only=true — без html/css/js. |
| get_page_export_bodyA | Экспорт тела страницы Tilda с локализованными ассетами {from,to} (без ) — для вставки в свой шаблон/CMS. metadata_only=true — без html/css/js. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: listing vs. details, full page vs. body vs. export. However, get_page and get_page_export both return full HTML but differ in asset localization, which could cause some confusion.
All tools follow a consistent get_<resource> or get_<resource>_<modifier> pattern in snake_case, with clear and predictable naming.
With 7 tools covering project info, page listing, and various export formats, the set is well-scoped without being too sparse or overpopulated.
The tools are thoroughly read-only, covering retrieval and export but lacking any create, update, or delete operations for projects or pages, which is a significant gap for a typical CMS integration.