Tally

Name: Tally MCP Server
Availability: InStock
Author: Tally

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Productivity26 tools

Build Tally forms from a sentence and read the responses back without exporting a CSV. 26 tools, OAuth 2.0 or an API key, free on every Tally plan.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 8 September 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Tally via MCP

https://api.tally.so/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Tally once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Tally Tools & Capabilities (26)

apply_logic

configure_blocks

create_blocks

create_new_form

extract_brand

fetch_insights

fetch_submissions

inspect_custom_css

list_blocks

list_forms

list_workspaces

load_form

move_blocks

remove_blocks

remove_pages

remove_questions

reposition_pages

reposition_questions

save_form

search_documentation

set_column_layout

set_form_title

update_custom_css

update_settings

update_styling

update_text

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

Tool names come from Anthropic's directory, not a handshake. The endpoint is OAuth-gated, so we could not read per-tool descriptions, JSON schemas or safety annotations. Read/write labels on this page are documentation-derived. Treat any tool as capable of writing unless Tally says otherwise.
Tally's own tool count disagrees with the directory. Tally's comparison articles say the connector exposes "21 tools" and "20+ MCP tools" (Tally, last updated 2026-08-05); Anthropic's directory listed 26 names on 2026-09-08. Both figures are the vendor-and-directory pair, five weeks apart, and the live server is the tiebreaker we could not read. The likeliest reading is growth between the two dates, not an error in either.
The server is in beta. Tally's developer documentation states the Tally MCP server is currently in beta and subject to change (fetched 2026-09-08).
The deletion guardrail does not cover questions, pages or blocks. It covers forms and submissions only.
Removing a question's effect on collected answers is undocumented for the MCP connector. See the FAQ above for the two bounding facts and what they do and do not establish.
An API key inherits the whole user. Tally warns that each API key is tied to a specific user, inherits that user's permissions as they change, and grants access to all of that user's resources. There are no fine-grained key permissions today, and Tally says the key is shown once. A key also stops working when that user leaves the organisation.
Everyone in a Tally organisation has the same rights. Tally states all users within an organisation have the same rights to create, edit, view and delete forms and workspaces, with only two extra privileges reserved to the owner. There is no read-only teammate to connect instead.
Several referenced features are plan-gated. Custom CSS, team collaboration and drop-off insights are Tally Pro ($29/mo); submissions data retention control is Tally Business ($89/mo); version history runs 7 days free, 30 on Pro, 90 on Business; visit insights show 7 days free (Tally plans and pricing, fetched 2026-09-08).
Rate limit: 100 requests per minute, per Tally's API documentation, returning HTTP 429. Tally publishes no separate MCP-specific limit and the 401 exposed no x-ratelimit-* headers.
Fair-use rather than hard caps on volume. Tally advertises unlimited forms and submissions on the free plan but names thresholds in its fair use policy — roughly 50,000 submissions a month, 100 GB of file uploads a month or 500 GB of total storage, 50,000 email notifications a month — above which it contacts you to arrange a custom plan.
Deletion is not immediate. Deleted forms, workspaces and submissions sit in Trash for 90 days before permanent deletion, and Tally states deleted form data is removed from backups within 90 days unless you empty the Trash sooner.
A restored version is not a published one. Tally states that restoring an older version of a published form does not automatically update the live form; you must click Publish.
The server declares no prompts. Its RFC 9728 descriptor reports mcp_prompts_supported false and mcp_resources_supported true (read 2026-09-08). Anthropic's directory also lists zero prompt names. We could not read the resources list without authenticating.

Frequently asked questions

No. Tally states the MCP server is free to use on all plans, including the free plan, with no separate add-on or upgrade required. Its Claude connector guide repeats this and adds that you need only a free claude.ai account to connect. Tally's paid tiers gate individual product features such as custom CSS and data retention, not access to the connector itself.

No, and Tally names this a safety guardrail on three of its own pages: the assistant can edit and create forms but cannot delete forms or individual submissions. Read the limit precisely, though. The connector does expose remove_blocks, remove_pages and remove_questions, so it can strip content out of a form it cannot delete outright.

Only when you ask it to, per Tally's MCP documentation. Tally states that submissions are not pre-loaded or sent to the AI without a direct request, and that a query such as analysing your survey responses is what pulls them into the conversation. Tally's GDPR page names the form creator as data controller of respondent data and Tally as the processor.

Tally does not document this for the MCP connector, and we did not test it. Two facts from Tally's own docs bound the question. Its version history stores questions, logic and settings but explicitly not submissions, and its public API models a question with an isDeleted flag alongside a numberOfResponses count, which indicates a soft delete rather than an erasure.

Any MCP-compatible client, per Tally. Its documentation names claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, Zed, Cline and Continue, and states the server should work in any tool that supports remote MCP servers. Claude and ChatGPT have one-click directory listings; every other client is added manually with the server URL.

Yes. Tally's developer docs document a bearer token in the Authorization header as the alternative to OAuth, and publish a Cursor configuration that uses one. Note Tally's own warning about the trade-off: an API key is tied to a specific user, inherits that user's permissions as they change, and grants access to all of that user's resources.

Tally documents a limit of 100 requests per minute on its API, which is the surface the MCP server sits on, and returns HTTP 429 when you exceed it. Tally does not publish a separate MCP-specific limit. Its docs recommend webhooks over polling for new submissions, because webhook delivery does not count against that rate limit.