Tally MCP
Related Servers
Alternatives to Tally MCP
No user-submitted related servers found.
Related Servers
- -licenseBqualityNot gradedmaintenanceA comprehensive Model Context Protocol server that enables Claude Desktop users to manage Tally forms with 23 powerful tools for creating, editing, and analyzing forms, submissions, questions, webhooks, and conditional logic.231-
- 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-
- 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
- AlicenseNot gradedqualityCmaintenanceMCP server for reading, editing, and publishing Google Forms with the official Google Forms API. Enables AI agents to programmatically create, modify, and manage forms and responses.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
- FlicenseNot gradedqualityDmaintenanceEnables form management, response handling, and analytics via the Fillout.io API, allowing users to create, update, and fetch forms and submissions through natural language.-
TDQS
Scored across 15 tools
The tool set has clear distinct purposes for core operations like create_form, get_form, list_forms, and manage_team, but there is significant overlap and confusion around deletion tools. The deprecated delete_form, bulk_delete_forms, and their preview/confirm counterparts create ambiguity, as agents might misselect between deprecated and active tools or misunderstand the multi-step workflow required for deletions.
Most tools follow a consistent verb_noun pattern (e.g., create_form, get_form, list_forms), which aids readability. However, there are minor deviations such as analyze_submissions (verb_noun) versus manage_team (verb_noun) and manage_workspace (verb_noun), which are consistent internally but slightly less so with others. The naming is generally predictable with only small inconsistencies.
With 15 tools, the count is reasonable for managing Tally forms, submissions, and workspace settings, covering a broad scope. It is slightly high due to redundant deletion tools (deprecated and new workflow), but overall, it aligns well with the server's purpose without being overwhelming.
The tool set provides comprehensive coverage for Tally form management, including CRUD operations (create_form, get_form, modify_form, deletion workflow), submission handling (get_submissions, analyze_submissions), workspace and team management (manage_workspace, manage_team), and sharing (share_form). There are no obvious gaps; the deprecated tools are noted but replaced with a secure workflow, ensuring agents can handle all essential tasks.