Tally MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | true |
| NODE_ENV | No | Environment setting for development | development |
| TALLY_API_KEY | Yes | Your Tally API key (starts with tally_) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tally_formsC | Get list of Tally forms |
| create_tally_formC | Create a new Tally form |
| get_tally_formC | Get details of a specific Tally form |
| update_tally_formC | Update an existing Tally form with comprehensive options including name, status, blocks, and settings |
| delete_tally_formC | Delete a Tally form |
| get_form_submissionsC | Get list of submissions for a specific form |
| get_form_submissionC | Get details of a specific form submission |
| delete_form_submissionC | Delete a specific form submission |
| get_form_questionsC | Get list of questions for a specific form |
| get_tally_webhooksC | Get list of webhooks for a specific form |
| create_tally_webhookC | Create a new webhook for a form |
| update_tally_webhookC | Update an existing webhook |
| delete_tally_webhookC | Delete a webhook |
| update_form_statusC | Update the status of a form (BLANK, PUBLISHED, DRAFT) |
| update_form_settingsC | Update specific form settings like notifications, closing options, etc. |
| configure_form_notificationsC | Configure email notifications for form owner and respondents |
| get_tally_block_typesB | Get comprehensive information about all available Tally form block types and their structures for building forms |
| get_tally_form_templatesB | Get pre-built form templates for common use cases (contact forms, surveys, registration, feedback, etc.) |
| create_conditional_logic_blockC | Create properly structured conditional logic blocks with validation for form flow control |
| validate_form_logic_flowC | Analyze and validate the logical flow of a form to identify potential issues or dead ends |
| get_conditional_logic_templatesC | Get pre-built conditional logic templates for common scenarios like progressive disclosure, skip logic, and branching surveys |
| validate_multiple_choice_logicB | Validate conditional logic for multiple choice questions to prevent common errors like using "equals" instead of "contains" |
| create_dynamic_question_setsB | Create questions with conditional option sets that change based on previous answers (like Q5/Q6 in complex surveys) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools have distinct purposes, such as create_tally_form for form creation and get_form_submissions for data retrieval, but some overlap exists, like update_form_settings and update_form_status, which could be confused as both modify form properties, though their descriptions clarify specific focuses.
Tool names follow a consistent verb_noun pattern throughout, such as create_tally_form, get_form_submissions, and update_tally_webhook, with no deviations in style or convention, making them predictable and readable.
With 23 tools, the count is borderline high for a form management server, as it includes many specialized tools like validate_multiple_choice_logic, which might be excessive for core operations, but it's not extreme and covers a broad scope.
The tool set provides comprehensive CRUD and lifecycle coverage for Tally forms, including creation, retrieval, updating, and deletion of forms, submissions, and webhooks, along with advanced features like conditional logic and validation, leaving no obvious gaps.