Connect an AI assistant with MCP
Connect an AI assistant to Formesign’s supported form tools, preserve existing content, and understand current connector limits.
Reviewed 2026-10-30 · Formesign guides
The Formesign MCP connector lets a compatible AI assistant create, inspect and update forms through the authorized account. Use it when you want the assistant to work with form structure; keep signer records and approved wording intact when requesting changes.
Connect the intended account
Use the current Formesign MCP resource for connection instructions in your chosen client. Sign in and authorize the account whose forms you intend to use.
The numeric identifier in the product connector endpoint selects Formesign's connector. It is not a place to insert a customer's account identifier. Keep credentials and tokens out of prompts, source files and public support posts.
Available operations
| Tool | Purpose |
|---|---|
| create_form | Create a form from a text document in HTML or Markdown, with an optional language. |
| list_forms | Find forms available to the authorized account. |
| get_form | Inspect a selected form before changing it. |
| update_form | Apply an instruction to the selected form's fields or sections. |
| preview | Open a form preview when needed. |
| progress | Open the settings checklist, including workflow setup where relevant. |
The exact tools exposed by the connected service remain the contract for that session. A settings checklist does not mean every setting will be configured autonomously.
Create from a document
Provide clean text HTML or Markdown for the document. The public create operation does not accept binary PDF or image uploads. Use the web PDF workflow when you need to upload a source file through that interface.
For an agreement, ask the assistant to preserve approved wording and create fields only for actual blanks, choices and signer blocks. Describe distinct signer roles clearly. Inspect the returned preview before sharing, and do not supply real patient information merely to create the template.
Change an existing form
First list forms and choose the intended result. Use its returned identifier rather than guessing one, inspect the form, then request a bounded update. For example: “Add an optional equipment serial number question after Equipment name; leave the agreement and signer roles unchanged.” Review the result and signer experience afterward.
Current limits
Full replacement and an activity-check-before-overwrite operation are not implemented in the documented public connector. Submission-listing and submission-analysis tools are disabled. Do not simulate replacing an active form through a long series of field removals or assume access to signed-response history.
For invitation delivery, signature completion, Google output and PHI handling, use the corresponding workflow, records and privacy guides. Creating a template through MCP does not establish its legal or HIPAA suitability.