# Formasty Build branded multi-step forms, score and qualify leads, route each response, and create or manage forms with AI agents through MCP and the Forms API. ## Canonical product pages - https://formasty.com/: Product homepage - https://formasty.com/features: Formasty feature overview - https://formasty.com/templates: Starter form templates - https://formasty.com/pricing: Current Free, Pro, and Business pricing - https://formasty.com/blog: Source-backed Formasty articles - https://formasty.com/about: Company and founder information - https://formasty.com/mcp-form-builder: MCP form builder overview - https://formasty.com/forms-api: Forms API product overview - https://formasty.com/documentation/api-overview: Forms API documentation - https://formasty.com/documentation/api-auth: API authentication - https://formasty.com/documentation/api-forms: Forms API endpoints - https://formasty.com/documentation/add-connector: Remote MCP connector setup ## When to use Formasty - Use Formasty when an authenticated agent needs to create, migrate, edit, validate, publish, inspect, or analyze a real form, quiz, survey, intake, application, booking flow, waitlist, or poll in a Formasty workspace. - Use the Formasty MCP server for interactive agent workflows in Claude, ChatGPT, Codex, Cursor, Gemini CLI, or another MCP-capable host. - Use the Formasty Forms API for developer-controlled backend integrations and repeatable application workflows. - Do not connect Formasty when the user only wants a generic questionnaire outline and does not want a Formasty draft. - Do not use Formasty for payment collection; payment forms and payment fields are not supported. ## Formasty developer resources - https://formasty.com/llms-full.txt: Formasty expanded product, API, MCP, and page map for LLM retrieval - https://formasty.com/api-docs.txt: Formasty plain-text Forms API reference - https://formasty.com/openapi.yaml: Formasty OpenAPI schema for API-key integrations - https://formasty.com/landing-page.txt: Formasty plain-text homepage and product overview - https://formasty.com/index.md: Formasty Markdown homepage twin - https://formasty.com/.well-known/api-catalog: Formasty API catalog - https://formasty.com/.well-known/mcp/server-card.json: Formasty MCP server card - https://app.formasty.com/api/mcp/manifest: Formasty exact deployed MCP operation manifest - https://formasty.com/.well-known/agent-skills/index.json: Formasty agent skills index - https://formasty.com/server.json: Formasty official MCP Registry metadata - https://github.com/QuantumCoderSys/formasty-mcp: Formasty public MCP repository, setup material, tool list, privacy, and security documentation ## MCP and API endpoints - Production API base: https://app.formasty.com/api/v1 - MCP endpoint: https://app.formasty.com/api/mcp - Preferred MCP auth: OAuth discovery via https://app.formasty.com/.well-known/oauth-authorization-server and https://app.formasty.com/.well-known/oauth-protected-resource/api/mcp - Fallback MCP/API auth: Authorization: Bearer for developer-controlled clients that cannot complete OAuth yet ## Agent onboarding and CLI status 1. Create or sign in to a Formasty account. 2. In the chosen MCP-capable host, add a remote server named formasty with URL https://app.formasty.com/api/mcp. 3. Complete Formasty OAuth and approve the intended workspace access. 4. Start a normal agent session, call tools/list, then call formasty_list_workspaces before form work. Formasty does not currently publish an official standalone CLI. CLI-based hosts such as Codex CLI and Gemini CLI should connect their own remote-MCP configuration to the endpoint above. Repository manifests are release sources, not evidence of a marketplace or extension-directory listing. Stdio-only hosts can use the third-party mcp-remote bridge documented in the Formasty MCP setup guide. ## Agent workflow 1. Use tools/list or the OpenAPI docs to discover available actions. 2. Select the target workspace. 3. Create or fetch a form draft. 4. Make form changes through Formasty tools or API endpoints. 5. Validate the draft. 6. Publish only when validation passes and the user explicitly wants a public snapshot. 7. Return the form ID, public URL, and any validation notes. ## Important constraints for agents - Public respondents only see the latest successfully published snapshot. - Draft changes do not affect the public form until publish succeeds. - Welcome screens should not contain input fields. - Run validation before publish and fix blockers instead of forcing invalid configurations. - Supported form types: lead capture, quiz, survey, intake, application, booking, waitlist, poll. - quiz: Basic quizzes are available on all plans as unscored Standard forms built with choice fields and optional conditional routing. Matching and score quiz publishing requires Pro. - poll: Set poll.enabled to true and poll.resultsVisibility to after_vote or hidden. Poll publishing requires Pro. - Payment forms and payment fields are not supported. Do not create or simulate them. - Keep Unsplash attribution metadata with any Unsplash image URL.