Connecting Tilda through MCP

📅 November 18, 2026⏱ 3 min read
Table of Contents

What gets connected

SEO Writer sends articles to Tilda Feeds. Set up your blog and its display template before connecting. This adapter does not change ordinary builder pages, Zero Block or the product catalogue.

Tilda access

You need Personal or Business. Open MCP server in your Tilda profile, create a key for the project and choose its expiry. Grant reading feeds and posts, creating, editing and publishing posts. Grant image uploads for media. The key is shown once: store it securely and never publish it.

Connect in SEO Writer

  1. Add a site and select Tilda.
  2. Enter the site address and MCP key. Load projects, choose a project and load its feeds. With restricted permissions, enter the project ID and feed UID manually.
  3. Select the article feed and check its fields. The project domain must match the site address.
  4. For custom feeds, map the body, summary, cover and optional category. Supply required defaults such as an author name. Do not invent experts.
  5. Save the connection. The key is not displayed again. Leave its field blank to keep the existing key when editing settings.

Your first delivery

Keep scheduling off and choose Draft. Generate an article or send a completed one. Open it in Tilda and check content, SEO fields, cover, images, video and mobile presentation. Publish it, then verify an update to the same post. You can then configure publication days, times and time zone.

Custom feeds

The integration supports one main blockText field, summary, cover and a select-field category. Additional simple text, numeric and supported choice fields use configured defaults. Unknown required fields are not filled automatically. Multiple independent complex body fields require separate verification. Updates preserve applicable existing values; defaults do not replace a populated author name.

Retries and updates

The service stores the remote post ID and uses it for updates. The URL is preserved. A post deleted in Tilda is not automatically recreated. A later cover updates the current remote post without sending unpublished local edits.

Parallel delivery of the same article is rejected while a delivery is in progress. Creation and uploads are not blindly repeated after a lost response. Your completed text stays saved. Retrying an uncertain creation first searches for the uniquely marked draft. If it cannot be identified, contact support instead of creating copies manually.

Troubleshooting

Check your Tilda plan, key expiry and permissions, site address and selected feed. Reload fields after changing the feed structure. Wait before retrying a rate-limited request. Delivery errors do not require regenerating the text. If a site already has linked articles, add a separate connection for another project or feed.

Was this article helpful?