A
licenseNot graded
qualityA
maintenanceEnables 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
niceform-mcp-server
Related Servers
Alternatives to niceform-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables users to create and manage GDPR-compliant, EU-hosted forms from any MCP-compatible AI assistant, with tools for listing forms, building them from descriptions, and retrieving submissions when explicitly requested.5198 npmMIT
Formswrite MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables LLMs to convert documents to Google Forms, edit questions, list and publish forms, and run AI form assistant tools through the Formswrite API.MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, manage, and analyze Google Forms with all question types, sections, quiz mode, and Google Drive/Sheets integration.11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to create multi-field forms, send approval requests via email, and retrieve structured human responses. It facilitates human-in-the-loop workflows by allowing agents to collect data and check form completion status.1,809 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create local web forms with unlimited brainstorming questions and retrieve user answers as JSON, including support for file uploads.MIT
TDQS
A4.2/5.0
Scored across 9 tools
Disambiguation4/5
Most tools target clearly different actions/resources, especially the response tools (list_form_responses vs summarize_responses vs export_responses_csv). However, get_preview_url and get_form overlap somewhat in retrieving draft/form status and details, and create_form can also publish via publish:true, which slightly blurs the create-vs-publish boundary.
Naming Consistency5/5
All tools use consistent snake_case with a verb-first pattern (create_form, publish_form, list_forms, get_form, close_form, etc.). get_preview_url fits the same convention, and there are no mixed casing or vague tool names.
Tool Count5/5
Nine tools is well-scoped for a form lifecycle server: creation, preview, publishing, listing, inspection, response retrieval, summarization, export, and closing. Each tool appears to earn its place without excessive granularity.
Completeness3/5
The server covers the main lifecycle of creating, publishing, collecting, summarizing, exporting, and closing forms. However, there is no tool to update a form's fields/questions after creation and no delete_form, leaving notable gaps if a draft needs correction or cleanup.
Maintenance
ActivityMaintained
ResponsivenessNo issues