# Formasty [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/QuantumCoderSys/formasty-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/formasty-2

## Description
Create, edit, validate, publish, and inspect Formasty forms and quizzes over authenticated MCP.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "formasty": {
    "url": "https://app.formasty.com/api/mcp"
  }
}
```

## Documentation

## What Formasty MCP server does

The Formasty MCP server gives authenticated AI agents access to Formasty’s hosted form-building and response-management capabilities. Agents can create forms from scratch or from starter templates, then build lead-capture forms, surveys, intake forms, applications, booking forms, waitlists, polls, and quizzes.

Operations cover the form lifecycle: adding, changing, moving, reordering, and removing steps and fields; configuring themes, covers, schedules, settings, thank-you screens, and endings; and building conditional workflows, variables, routing rules, matching quizzes, and score quizzes. Agents can validate and audit drafts before publishing, then retrieve share, embed, and connection assets.

The service also supports reading and managing submissions and creating response exports when the authenticated user has permission. Additional supported capabilities include webhooks, analytics pixels, tag managers, custom domains, and imports from Google Forms and Typeform. The public contract currently exposes 75 operations, while MCP `tools/list` provides the live schemas and safety annotations.

## How it works

The Formasty MCP server is hosted by Formasty rather than implemented in this repository. Connect an MCP client to `https://app.formasty.com/api/mcp` using Streamable HTTP. The legacy SSE endpoint is `https://app.formasty.com/api/mcp/sse`.

OAuth connections operate as the signed-in Formasty user. Access remains limited by OAuth or API-key scopes, workspace membership and role, selected workspace access, subscription feature gates, draft revision checks, and server-side validation. Tool invocation and workspace data require authentication; public discovery exposes tool definitions only.

Consequential actions may also require approval from the host and user. This matters for agents that publish forms, modify workspace content, or access submissions.

## Setup and configuration

The Formasty MCP server does not run from a cloned local package. Add the hosted URL to a client that supports remote MCP servers and complete the Formasty OAuth flow. Claude uses a custom connector, while Cursor, VS Code, and Cline provide remote-server configuration paths. Gemini CLI has an official extension that points to the hosted endpoint and does not install a local backend process.

Older Claude Desktop versions or other stdio-only clients can use `mcp-remote` as a bridge. The repository’s documented bridge invokes `npx -y mcp-remote` with the hosted MCP URL.

Use OAuth for user-facing clients. API keys are available as a fallback for developer-controlled clients, but credentials must not be placed in public repositories, shared configuration, issues, or screenshots.

## Tools and capabilities

The Formasty MCP server can support agents that need to:

- Create forms and quizzes from templates or new definitions.
- Edit fields, steps, themes, schedules, endings, and settings.
- Configure conditional logic, variables, routing, and scoring.
- Validate, audit, and publish drafts.
- Retrieve sharing, embedding, and connection assets.
- Read submissions and create response exports where permitted.
- Configure supported integrations and import supported external forms.

## Limitations and notes

The repository contains documentation and metadata, not the Formasty backend, infrastructure, credentials, or customer data. The hosted service is governed by Formasty’s terms, while the repository documentation and metadata use the MIT License.

Available operations and schemas may change, so clients should use MCP `tools/list` as the authoritative source. Feature availability can depend on the Formasty plan, workspace permissions, scopes, and selected workspace. Avoid exposing access tokens, API keys, response data, private form URLs, or customer information in support requests or public issues.

_Full upstream README: https://allmcps.com/mcp/formasty-2/readme_