← Top 100 / Full directory (12,874)

Weavely AI Forms & Surveys

Communication Remote 13 tools Ready surface Auth required

Weavely is an AI-native form builder. This MCP server exposes 13 tools that cover the entire form-building lifecycle: create forms, add and update 25+ element types (text, rating, matrix, file upload, signature, and more), configure conditional logic, set themes, manage multi-step pages, and publish — all from natural language. The AI builds incrementally while a live preview URL updates in real time. When you're done, a single publish_form call returns an editor link to claim full ownership on the Weavely platform. No authentication required. After publishing, connect your form to Google Sheets, Zapier, n8n, HubSpot, Notion, and more.

Docs ↗

How to connect

1
Add the remote MCP URL
Paste this endpoint into Claude, ChatGPT, or Cursor MCP settings.
https://weavely--florian.run.tools
2
Verify the tools loaded
Confirm tools/list returns the expected tools before relying on them in production.

Listing quality

Observable facts from our catalog and daily probe — not a safe-to-install badge.

Surface
Ready surface
Live handshake
Auth required
Auth gate
Auth gate
Tools source
tools/list (live)

Observable catalog + probe facts — not a safe-to-install badge.

Tools

(13)
  • create_form

    Create a new Weavely form. Returns a formId and a live preview URL. IMPORTANT: This MUST be the first tool you call — all other tools require the formId returned by this tool. IMPORTANT: Call all tools ONE AT A TIME, sequentially. NEVER call multiple tools in parallel. IMPORTANT: Pass the formId from this response to ALL subsequent tool calls. The preview URL is a live link the user can open to see the form at any point. It updates automatically as you make changes — the user just needs to refr

  • get_form_summary

    Get the current form structure: pages, elements (with IDs, types, labels), theme, and settings. Call this to see available page and element IDs before making edits. Requires create_form to have been called first.

  • add_element

    Add an element to a page. The element is appended to the end of the page. Call this sequentially — NEVER call multiple add_element in parallel. Use get_form_summary to see available pageIds. Element types and their specific params: - Input fields: input-text, input-number, input-email, input-phone-number, input-url, input-time, input-date, text-area - File upload: input-file (supports maxFiles, maxFileSize, allowedFileType) - Choice fields: radio-buttons, checkbox-buttons, dropdown, ranking (re

  • update_element

    Update an existing element's properties. Only send the fields you want to change. Use get_form_summary to find element IDs. Note: you cannot change an element's type — remove it and add a new one instead.

  • remove_element

    Remove an element from the form by its ID. Use get_form_summary to find element IDs.

  • reorder_elements

    Move an element to a new position within the same page or to a different page. Use get_form_summary to see current page and element IDs.

  • add_page

    Add a new form page. By default it is inserted before the ending page. Use this to create multi-page forms. After adding, use add_element to populate the page.

  • remove_page

    Remove a form page and all its elements. Cannot remove the ending page or the last remaining form page.

  • reorder_pages

    Reorder the form pages. Provide the form page IDs in the desired order. The ending page is always kept last automatically — do not include it.

  • set_theme

    Set the form's visual theme. Choose colors, fonts, layout, and component styles that match the form's topic and tone. Be creative — pick a cohesive palette. Only send what you want to change — unset properties keep their current values. COLORS (all hex values): - primary: main accent color (buttons, highlights) - background: page background - text: general body text - question: question/label text - answer: user input text - secondary: secondary UI elements - surface: input field backgrounds -

  • set_settings

    Configure form-level settings. Only send what you want to change. Supported language codes: ar, ca, zh-Hans, zh-Hant, hr, cs, da, nl, en, et, fi, fr, de, el, he, hi, hu, id, it, ja, ko, no, pl, pt, ru, es, sv, tr, uk, vi.

  • set_logic

    Set conditional logic rules and/or event triggers. This replaces ALL existing rules/triggers. Use get_form_summary to see element and page IDs for building conditions. Logic rule structure (FOLLOW THIS EXACTLY): { "id": "<uuid>", "name": "Human-readable rule description", "conditions": [ { "id": "<uuid>", "variable": "field:<elementId>", "operator": "isNotEmpty", "value": null } ], "logicalOperator": "all", "actions": [ { "id": "<uuid>",

  • publish_form

    Publish the form so the user can keep it, share it, and collect real responses. ONLY call this when the user EXPLICITLY asks to publish, save, or share their form. Do NOT call this automatically — the preview URL is sufficient during the building process. Creates a permanent copy of the form and returns an editor URL. The user can create a Weavely account there to claim full ownership. IMPORTANT: If this tool fails, tell the user there was an error publishing and they should try again. Do NOT

Tool source: tools/list (live) · last probed 2026-10-01

Related servers