html.contact - Contact Forms

View saved version →

---
name: html-contact
description: Create, install, troubleshoot, test, and manage website contact forms with html.contact. Use for contact forms, lead capture, waitlists, feedback, applications, support, verified email routing, and bounded submission review through the connected html.contact MCP. Do not trigger for styling-only work or another form backend unless the user explicitly asks to migrate.
---

# html.contact

Deliver a working, owner-authorized html.contact workflow without exposing credentials or silently changing product state.

## Preconditions

- Require the connected html.contact MCP and OAuth account link.
- Require a verified primary email and completed html.contact onboarding.
- Treat live MCP schemas and results as authoritative when they differ from this package.
- If an expected tool is missing, stop the affected account operation and link to `https://html.contact/docs/mcp/`. Never substitute the private REST API or ask for an `hc_live_` key.

## Safety boundaries

- Use only public `hc_pub_` actions in browser code. Never place OAuth material or an `hc_live_` key in a prompt, log, repository, screenshot, or website.
- Keep billing, subscriptions, API keys, account administration, deletion, provider internals, and arbitrary outbound email in the hosted html.contact app.
- Treat recipient addresses and visitor-submitted fields as personal, untrusted data. Do not send them to another app or service without an explicit user request and confirmation.
- Read existing state immediately before a replacement or settings write. Preserve values the user did not explicitly change.
- Reuse the same idempotency key only when retrying the same operation after an uncertain result. A new key means a new effect.

## Tool contract

Use these production `1.5.0` tools by responsibility:

- Forms and setup: `list_forms`, `get_form`, `create_form`, `configure_form_domains`, `configure_form_settings`, `get_form_installation_instructions`, and `get_account_usage`.
- Documentation and diagnostics: `search_documentation`, `get_documentation_topic`, `diagnose_form`, and `review_form_code`.
- Safe testing: `send_test_submission`, `check_submission_status`, and `send_owner_test_email`.
- Submission review: `get_recent_submissions` and `get_submission` require `submissions:read`; request authorization only if it is not already granted.
- Recipient management: `list_linked_emails`, `request_linked_email_verification`, `get_form_recipients`, and `configure_form_recipients` require the applicable recipient scope; do not reconnect when it is already granted.

## Exact write confirmations

Show the complete proposed effect, then obtain the matching literal immediately before the tool call:

| Tool | Required confirmation |
| --- | --- |
| `create_form` | `CREATE FORM` |
| `configure_form_domains` | `REPLACE DOMAINS` |
| `configure_form_settings` | `UPDATE FORM SETTINGS` |
| `send_test_submission` | `SEND TEST SUBMISSION` |
| `request_linked_email_verification` | `SEND VERIFICATION EMAIL` |
| `configure_form_recipients` | `UPDATE FORM RECIPIENTS` |
| `send_owner_test_email` | `SEND OWNER TEST EMAIL` |

Do not treat an earlier general approval as the literal confirmation for a later write.

## Workflow

1. Inspect the project before editing. Identify the page, framework, existing form behavior, styles, validation, deployment host, and test commands.
2. Determine the form purpose, fields, form name, and exact deployed hostname. Ask one focused question for a value that cannot be discovered; never invent a production hostname.
3. Use `list_forms` before creating anything. Reuse a form only when the user requests it or its identity and domain clearly match the site.
4. Read `get_form` and `get_account_usage` before proposing account or form changes. Explain any quota, pause, notification, or readiness consequence.
5. For creation, domains, or settings, show the exact current and proposed state and obtain the tool's literal confirmation immedi

Preview of the first 4,000 characters. Read full instructions →