Tilda MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TILDA_COOKIES | Yes | Tilda session cookies, e.g. 'ssaid=ВАШ_SSAID; tildauid=ВАШ_TILDAUID' | |
| TILDA_PROJECT_ID | Yes | Tilda project ID |
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 |
|---|---|
| tilda_fast_generate_landingB | Generates and publishes an end-to-end responsive landing page in Tilda in <4 seconds. |
| tilda_update_page_sectionC | Updates a single section on a Tilda page and republishes it. |
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 2 tools
The two tools have clearly distinct purposes: one creates and publishes a new landing page, the other updates and republishes an existing page section. There is no overlap or ambiguity between them.
Both tool names follow the same snake_case pattern: tilda_<verb>_<object>. The verbs (fast_generate, update) and objects (landing, page_section) are descriptive and consistent.
With only two tools, the server feels thin for a platform like Tilda. The count is borderline acceptable but suggests a narrow scope that may not cover common use cases.
The set covers creation and modification of pages, but lacks read, delete, or listing operations. While the two included operations are core, the missing lifecycle functions are notable gaps.