Skip to main content
Glama

Related Servers

Alternatives to formhaus-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Formward as an MCP server for your coding agent. Pair once from the Formward dashboard, then let Claude Code, Codex, Cursor or any other MCP client create forms, fetch the paste-ready snippet, add webhooks and confirm a test submission against your workspace. Formward is a form backend hosted in the EU (Sweden). This package talks to it over HTTPS with a key that is pinned to one workspace and ca
      8
      209 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Form backend an AI agent can run end to end: register the account, provision a site's forms in one bootstrap_site call, get the snippet with spam protection, and verify HMAC-signed webhooks. 26 tools over streamable HTTP (OAuth or bearer token) or stdio via npx @furrowforms/mcp.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to collaborate on a shared local-first discussion board by reading forum status, communities, posts, and search results; creating posts and typed replies; claiming tasks; voting; and advancing work through open, claimed, in-progress, review, and solved states with idempotent retry-safe writes.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create local web forms with unlimited brainstorming questions and retrieve user answers as JSON, including support for file uploads.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to build and operate production-ready forms, quizzes, surveys, and workflows, including creation, publishing, submission management, and integration with webhooks and analytics.
      MIT

    TDQS

    A4.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct role, and descriptions explicitly distinguish close pairs: validate_definition vs simulate_path, capabilities vs example_definitions, publish_form vs update_form_settings, list_forms vs get_submissions, and get_webhook vs reveal_webhook_secret. An agent can reliably select the right tool without guessing.

    Naming Consistency4/5

    The set is consistently snake_case, and most tools follow a verb_noun pattern such as validate_definition, publish_form, and update_form_settings. A few tools are noun-based (capabilities, example_definitions, translation_template), which is a minor deviation from the otherwise predictable convention.

    Tool Count5/5

    Twelve tools are well-scoped for building, validating, simulating, translating, publishing, and inspecting Formhaus forms. Each tool covers a meaningful operation without obvious redundancy, fitting comfortably within the typical 3-15 range.

    Completeness4/5

    The surface covers the core form lifecycle: reference, validation, repair, simulation, translation, publishing, listing, submissions, settings, and webhook secrets. Minor gaps remain, such as no direct delete-form operation or get-definition tool for retrieving an existing published form definition to edit it.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow