FormVault MCP Server
Related Servers
Alternatives to FormVault MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceManage Tally.so forms through AI conversation. Create, update, and organize forms using natural language instead of web interfaces. Features safe bulk operations and works with all major MCP clients.1619 npm8ISC
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables users to create forms, read submissions, and build and publish invitations from Claude, ChatGPT, Cursor, or any MCP client via a remote, OAuth-secured connection.MIT
- FlicenseAqualityCmaintenanceMCP server for FormsList, a form-backend SaaS. Enables creating form endpoints, reading submissions, configuring auto-responses, and generating embed snippets via natural language.7-

formbase MCP serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to collect and verify customer information by creating prefilled, branded form requests for individual recipients, reading their submissions, and building, publishing, translating, and sharing forms through a hosted MCP connection.MIT- AlicenseNot gradedqualityFmaintenanceMCP server for Dashform (getaiform.com) - create and manage AI-powered forms, quizzes, and surveys. Supports form creation, response collection, analytics, and AI-driven form building with 15 tools across form management, response handling, and AI operations.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource+action: list_forms and list_submissions return different collections, get_form retrieves a single form definition, and create/delete are unambiguous write operations. There is no meaningful overlap between any pair.
All five tools follow a strict snake_case verb_noun pattern (list_forms, get_form, list_submissions, create_form, delete_form). The convention is applied uniformly with no deviations.
Five tools is well-scoped for a form-management server, with each tool earning its place across form listing, retrieval, creation, deletion, and submissions. No redundancy or padding.
The surface covers create/read/delete for forms and read for submissions, but there is no update_form (editing an existing form is a core workflow) and no submission-level operations beyond listing. These gaps will force agents to work around missing lifecycle steps.