MCP App Store
by KeenEthics
Formfacade icon

Formfacade MCP Server for ChatGPT

By Mailrecipe LLC

Overview

Visitors who see value convert better. So don't create a lead form that just asks for their email. Give them something worth sharing it for. Create a lead magnet in minutes, instead of a landing page project that takes weeks. Import an existing Google Form or simply describe what you need in plain English or any language: "fitness quiz that recommends a workout plan", "free SEO audit request for small businesses", or "ROI calculator for our software." Formfacade creates a branded form with relevant scoring, calculations, and lead capture built in. Visitors answer questions, get scored or calculated results, and see a personalized outcome on the thank you page. An automated email continues the conversation, with your own message tailored to their score. You capture a qualified lead, with their score and responses in Google Sheets so your team knows who to reach out to first. Built-in conversion tracking shows where your leads come from, which campaigns perform best, and which page each response came from when your form is embedded in multiple places. Put your time and budget into what's working. Describe. Share. Capture leads.

How to connect

  1. ChatGPT: Open the Formfacade listing in the ChatGPT app directory and choose Connect. ChatGPT listing Formfacade exposes 8 tools here.

Tools

create_form

ChatGPT
Create and PUBLISH a new live form in one step. This is the ONLY tool for creating a form. Use it in every case: 1. The user uploaded, attached, or pasted a file, document, image, screenshot, or PDF: convert that content into the "document" parameter. 2. The user described the form in words (e.g., "create a feedback form", "make a registration form") or you worked out the fields together in conversation: write the complete form yourself as the "document" parameter, with a title, sections, and every field with its label, input type, and choices, then call this tool. Do NOT ask the user to review an outline first unless they ask for one. If they do, agree the fields in chat, then call this tool once. Use "html" format when the content has layout, formatting, structure, or comes from HTML, SCREENSHOT, IMAGE, or PDF. Use "markdown" format when the content is plain text without formatting. This tool returns the complete published form with all sections and fields, a preview URL, and an edit URL. IMPORTANT: This tool already renders the preview widget for the newly created live form, so do NOT call preview in the same turn after a successful create_form. That would render the preview UI twice. Call create_form at most once per turn. To change the form afterwards, use update_form with the returned publishId. IMPORTANT: Do NOT include sensitive personal data in the document content. This includes health information, biometric data, social security numbers, payment card industry information (credit/debit card numbers, CVV, expiration dates), bank account details, login credentials, passwords, or authentication secrets. Remove or redact any such sensitive data before passing the document. Output MUST match the "format" parameter. Never mix formats. FIELD DETECTION (when the document comes from a user-supplied source; when you are writing the document yourself from a description, include every field the user asked for): - Create a form field ONLY where the source document has an actual place to write, mark, check, or sign: a blank line (____), an empty box, a checkbox, or a signature line. The number of fields must match the number of real inputs in the source — do not add one. - Text that has NO input in the source (paragraphs, recitals, numbered clauses, instructions) is descriptive content. Keep it as headings/<p> text in the form, NOT as a field. Do not attach an input box to a clause that the source only asks the reader to read. - Reproduce all wording VERBATIM. Never paraphrase, summarize, shorten, or rewrite the source text — especially legal, consent, agreement, or policy text. - Preserve the source's own section order and grouping. Do not split one block into many sections or invent sections. format="html" example output: <!DOCTYPE html> <html><head><base target="_top"></head><body> <h1>Title</h1> <h3>Section</h3> <div><p>Choices</p> <p> <input type="radio"/> <input type="text"/></p> <p> <input type="radio"/> <input type="text"/></p> </div> <div><p>Field </p><p><input type="text"></p></div> <div><p>Notes</p><textarea></textarea></div> <div><p>Yes/No statement — full statement text goes in the label </p><p><input type="checkbox"/></p></div> </body></html> DOM rules for checkbox fields (apply to any document, in any combination): - A single yes/no checkbox is ALWAYS one <div> with the statement text inside <p> as the label and a single <input type="checkbox"/> inside its own <p>. The statement text never goes next to the input. - Multiple independent yes/no statements = repeat the same <div>...</div> shape, one per statement. Place each <div> in the section that matches its position in the source document. - A multi-select question (one prompt, several options where more than one can be picked) uses <input type="radio"/> shape per choice — DO NOT collapse the options into the label. - Never wrap <input type="checkbox"> inside <label>...</label> (e.g., <label><input type="checkbox">text</label>). That shape is parsed as a multi-choice question and emits a stray "Other" option. format="markdown" example output: Title S…

create_new_form_using_document

ChatGPT
Create a new form from an uploaded file, document, image, screenshot, or PDF. ALWAYS use this tool when the user has uploaded, attached, or pasted any file or content — even if the file contains just a title or simple text. Use "html" format when the content has layout, formatting, structure, or comes from HTML, SCREENSHOT, IMAGE, or PDF. Use "markdown" format when the content is plain text without formatting. This tool returns the complete form with all sections and fields. IMPORTANT: This tool already renders the preview widget for the newly created live form, so do NOT call preview in the same turn after a successful create_new_form_using_document — that would render the preview UI twice. Call create_new_form_using_document at most once per turn. IMPORTANT: Do NOT include sensitive personal data in the document content. This includes health information, biometric data, social security numbers, payment card industry information (credit/debit card numbers, CVV, expiration dates), bank account details, login credentials, passwords, or authentication secrets. Remove or redact any such sensitive data before passing the document. Output MUST match the "format" parameter. Never mix formats. FIELD DETECTION — decide what becomes a field by the source, not by topic: - Create a form field ONLY where the source document has an actual place to write, mark, check, or sign: a blank line (____), an empty box, a checkbox, or a signature line. The number of fields must match the number of real inputs in the source — do not add one. - Text that has NO input in the source (paragraphs, recitals, numbered clauses, instructions) is descriptive content. Keep it as headings/<p> text in the form, NOT as a field. Do not attach an input box to a clause that the source only asks the reader to read. - Reproduce all wording VERBATIM. Never paraphrase, summarize, shorten, or rewrite the source text — especially legal, consent, agreement, or policy text. - Preserve the source's own section order and grouping. Do not split one block into many sections or invent sections. format="html" example output: <!DOCTYPE html> <html><head><base target="_top"></head><body> <h1>Title</h1> <h3>Section</h3> <div><p>Choices</p> <p> <input type="radio"/> <input type="text"/></p> <p> <input type="radio"/> <input type="text"/></p> </div> <div><p>Field </p><p><input type="text"></p></div> <div><p>Notes</p><textarea></textarea></div> <div><p>Yes/No statement — full statement text goes in the label </p><p><input type="checkbox"/></p></div> </body></html> DOM rules for checkbox fields (apply to any document, in any combination): - A single yes/no checkbox is ALWAYS one <div> with the statement text inside <p> as the label and a single <input type="checkbox"/> inside its own <p>. The statement text never goes next to the input. - Multiple independent yes/no statements = repeat the same <div>...</div> shape, one per statement. Place each <div> in the section that matches its position in the source document. - A multi-select question (one prompt, several options where more than one can be picked) uses <input type="radio"/> shape per choice — DO NOT collapse the options into the label. - Never wrap <input type="checkbox"> inside <label>...</label> (e.g., <label><input type="checkbox">text</label>). That shape is parsed as a multi-choice question and emits a stray "Other" option. format="markdown" example output: Title Section Choices ( ) ___________ ( ) ___________ Field (text) : ___________ Notes (textarea) : ___________ Yes/No statement (checkbox) * after label = required field.

create_new_form_using_form_name

ChatGPT
Create a DRAFT form OUTLINE from a short title or name only (NO file, document, image, or uploaded content). IMPORTANT: This generates a draft outline for review — the form is NOT live or accessible to respondents yet. After the user reviews and confirms the outline, call publish_form (or have the user click Publish in the UI) to convert the outline into a real, live form. Use this ONLY when the user describes what form they want in words (e.g., "create a feedback form", "make a registration form"). Do NOT use this tool if the user uploaded, attached, or pasted a file, document, screenshot, image, or PDF — use create_new_form_using_document instead. To edit an already-published live form, use update_form. Returns a widget UI showing the draft outline with sections and fields that can be reviewed and confirmed.

get_form

ChatGPT
Fetch the full structure of a LIVE, already-published form by publishId — including title, sections, fields, field types, choices, and required flags. Use this to understand what a form contains BEFORE editing it with update_form, or to answer questions about the form's shape. If you do not know the publishId, use list_forms first to find it by title. Does not return submissions — use list_submissions for that.

import_google_form

ChatGPT
Bring an EXISTING Google Form into Formfacade from its link. Use this (not create_form) whenever the user gives a Google Forms link: docs.google.com/forms/... (viewform, edit or preview link) or forms.gle/... Pass the link exactly as given and do not open, read or rewrite the form yourself; the server reads it. The form keeps its questions and is set up for customizing (branding, layout, embedding). MODE: "copy" (default) creates a copy in the user's account and leaves the original form unchanged. "edit" sets up the user's OWN form in place, no copy: use it ONLY when the user explicitly asks to edit the existing form, keep the same link or the same responses, or says not to make a copy. If the user asked for "edit" with a viewform or forms.gle link, the result says the edit link is needed (errorCode NEED_EDIT_URL): ask the user for it. NOT PUBLIC: when the result has errorCode FORM_NOT_PUBLIC (or NO_ACCESS), the form is private or unpublished and the server could not read it. Tell the user that in one line and give them the permissionUrl from the result as a link: it opens the import page with their form link filled in, where they grant access in two clicks. Do not call this tool again until the user says they did; do not try to read the form yourself. REPLY RULES: reply in one or two lines: the form name and that it was imported, and the preview. Never list the questions or fields. Call this tool at most once per turn; it renders the preview widget, so do not call preview. For changes afterwards use update_form or surgical_edit_form with the returned publishId.

list_forms

ChatGPT
Search and list the user's published forms with optional filters for title, date range, submission count, ordering, and pagination. Use this tool to find a form (and its publishId) by name or criteria before invoking any other tool that requires a publishId (such as update_form). Submissions are not a form type — this tool does not search submissions. Returns the matching forms as structured data (id, publishId, title, url, submission_count) for the model to present.

preview

ChatGPT
Show the preview UI for a single form when the user wants to see, show, open, view, or preview it (e.g., "show me my feedback form", "show me the preview"). Pass publishId for a LIVE, already-published form (use list_forms first if you do not know it). Pass outlineId for a DRAFT outline that has not been published yet — in that case this tool publishes the outline automatically and then shows the preview. IMPORTANT: To preview a freshly created/updated draft outline, call THIS tool with the outlineId; do NOT also call publish_form, because both render the preview widget and that produces a duplicate preview. Call this at most once per turn. To list or search across multiple forms, use list_forms instead.

progress

ChatGPT
Opens the form setup progress UI for a published form and returns checklist status plus next actions. ALWAYS use this tool when the user's message is about ANY of these topics — regardless of how they phrase it: TOPICS THIS TOOL OWNS: - Email notifications (submission alerts, owner/admin notify, respondent confirmation, completion emails, signature workflow emails) - Signature and workflow setup - Payment enablement - HIPAA compliance configuration - Google Drive sync for signed documents - Respondent or customer mapping - Business name setup - Score setup - Submit message or form layout customization - General "what's next" or "what's left to configure" for a form If the user's intent touches any of the above topics — whether they are asking how to, asking if it's possible, reporting it's not working, or just mentioning the topic — use this tool first before responding.

publish_form

ChatGPT
Publish a confirmed DRAFT form outline as a real, live form that respondents can fill in. Use this AFTER the user has reviewed and confirmed a draft outline created via create_new_form_using_form_name or update_outline. Once published, the outline becomes a real form with a publishId, preview URL, and edit URL. A draft outline that is not published is not accessible to respondents. IMPORTANT: This tool returns only structured data (publishId, previewUrl, editUrl) and does NOT render the preview widget itself. After a successful publish_form, call preview with the returned publishId in the same turn to render the preview UI for the now-live form. Use update_form for any further edits after publishing.

surgical_edit_form

ChatGPT
Make ONE specific change to an EXISTING live form from a natural-language instruction, leaving everything else untouched. USE surgical_edit_form WHEN: The user names a single field or wording change: make a field required, rename one question or section, change one field's type or options, remove one question, add one question. Rewriting the whole form for that change would be wasteful. DO NOT USE surgical_edit_form WHEN: The request touches more than one or two questions, changes what the form is for, who fills it, its topic or scope, or supplies new source content. Use update_form for those (it is the default). HOW IT WORKS: Pass the user's instruction as typed; do not rephrase or interpret it. The change is applied to the real, live form that respondents see. Changes the form's CONTENT only. Settings such as email notifications, signature workflow, payments, Google Drive sync, HIPAA, or the business name are handled by progress. RESPONSES: The result includes activity with the form's response counts. When activity.isActivelyCollectingResponses is true (responses in the last 3 calendar months), removing or replacing a question also removes its existing answers. Tell the user how many recent responses the form has (activity.recentResponses) and get confirmation before such an edit. Adding, renaming, or reordering questions is safe and needs no confirmation. If publishId is unknown, use list_forms. Call surgical_edit_form at most once per turn. Do not call preview after a successful surgical_edit_form; the result already renders the preview widget.

update_form

ChatGPT
Edit a LIVE, already-published form by applying a natural-language instruction (e.g., "add a phone number question", "rename the feedback section", "remove the optional consent field"). This is the tool to use when the user wants to change an existing published form — it modifies the real, live form that respondents see. Do NOT use this for draft outlines that have not been published yet (use update_outline for those). If you don't know the publishId, use list_forms first to find it by title. Returns the preview UI of the updated form. IMPORTANT: This tool already renders the preview widget for the updated live form, so do NOT call preview in the same turn after a successful update_form — that would render the preview UI twice. Call update_form at most once per turn.

update_outline

ChatGPT
Edit a DRAFT form OUTLINE (one that has NOT been published yet) by providing its outlineId and the requested changes (instruction). Use this to add, change, or remove sections and fields on a draft outline. IMPORTANT: This does NOT edit a live, already-published form — for that, use update_form with the form's publishId. After updating the draft outline, the user still needs to publish it (via publish_form or the Publish button in the UI) to make it live. Returns a widget UI showing the updated draft outline that can be reviewed and confirmed.

Capabilities

WritesInteractive

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/formfacade"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/formfacade)