# sounny/sounnyforms-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/sounny/sounnyforms-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 47  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sounny-sounnyforms-mcp

## Description
Serverless form backend, lead triage and contact form generator for static sites, React and JAMstack apps.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sounnyforms-mcp": {
    "command": "npx",
    "args": ["-y","sounnyforms-mcp"]
  }
}
```

## Documentation

## What sounny/sounnyforms-mcp does

The sounny/sounnyforms-mcp MCP server exposes SounnyForms operations to MCP-compatible AI assistants and coding environments. It focuses on three tasks: sending structured inquiries, generating frontend form snippets, and checking whether the SounnyForms service is available.

`submit_form` accepts a destination email address or custom form ID, the submitter’s name and email, a message, and optional key-value fields. The submission is delivered to the configured inbox and recorded in the SounnyForms dashboard. The submitter’s email is used for direct replies.

`generate_form_snippet` produces form code in one of six requested formats: React, Next.js, plain HTML, Tailwind, CDN, or cURL. You can provide a form identifier and a list of additional fields such as phone, company, or budget.

`check_endpoint_health` checks the live service for availability, response latency, and SMTP gateway status.

## How it works

The MCP process runs locally and communicates with the selected client through standard input and output. Requests are sent to the SounnyForms service, so the server does not require a user-supplied API key. For form submissions, the destination can be a recipient email address or an existing form ID.

SounnyForms stores submissions in its encrypted Cloud Firestore-backed account storage and forwards leads to the recipient inbox. The platform also describes automatic honeypot injection and velocity-based spam protection for its form handling.

## Setup and configuration

The sounny/sounnyforms-mcp MCP server requires Node.js 18 or newer. With npm available, clients can launch it using `npx -y sounnyforms-mcp`. Claude Desktop and Cursor use the same MCP configuration shape: define an `sounnyforms` server with `npx` as the command and `-y sounnyforms-mcp` as its arguments.

The README also documents the same setup for Google Antigravity. Alternatively, clone the repository, run `npm install`, and start it with `node server.js`. No environment variables or API keys are listed as required configuration.

## Tools and capabilities

- Submit inquiries to an email address or form ID.
- Include required identity and message fields plus optional custom data.
- Generate React, Next.js, HTML, Tailwind, CDN, or cURL form examples.
- Add a custom form ID and named fields to generated code.
- Inspect service availability, latency, and SMTP gateway health.

## Limitations and notes

The documented tools depend on the SounnyForms hosted service for delivery, storage, and health checks. `submit_form` requires a destination, name, submitter email, and message; extra fields are optional. The README does not describe authentication beyond its zero-API-key model, account-management operations, filtering or retrieval tools, or deployment modes other than the local Node.js process. This makes the sounny/sounnyforms-mcp MCP server most relevant to developers who need form generation or submission, rather than a general-purpose lead-management interface.

_Full upstream README: https://allmcps.com/mcp/sounny-sounnyforms-mcp/readme_