MCP prompt example

MCP form builder prompt example

A concrete prompt example for asking an MCP-connected agent to build a FormNode form in front of n8n without exposing secrets or publishing too early.

Direct answer

A good MCP form builder prompt gives the agent the workflow goal, fields, dynamic data sources, approval rules, webhook contracts, publish boundary, and documentation expectations. It should not include API secrets or ask the agent to publish before readiness checks pass.

Example agent prompt
Build a draft FormNode form for Microsoft 365 user onboarding.

Use n8n as the workflow engine.

Fields:
- Client organization
- First name
- Last name
- Start date
- Manager
- Copy-from user
- License SKU
- Approval contact

Dynamic data:
- Manager, copy-from user, and license fields will use read-only n8n option webhooks.
- Final submission will use a separate production n8n webhook.

Requirements:
- Keep stable field keys for n8n.
- Include organization context in the final payload.
- Add approval before provisioning.
- Do not publish until webhook readiness is verified.
- Document the payload contract for the n8n workflow.
Notes
  • Give the agent the workflow contract, not just the visible form labels.
  • Tell the agent to create a draft first and keep publishing behind a readiness check.
  • Never paste n8n API keys, bearer tokens, or customer secrets into the prompt.
  • Ask for payload documentation so the n8n workflow has a stable contract to consume.
Common questions

What should I include in an MCP form builder prompt?

Include the form goal, fields, source systems, dynamic option endpoints, approval rules, webhook contracts, tenant context, and publish boundary.

Should an MCP prompt include secrets?

No. Secrets should stay in n8n credentials, FormNode settings, or the relevant secret manager. Prompts should describe contracts and configuration intent.

Related pages