Tally MCP connector
Connect Tally to Elaichi and Claude, ChatGPT, Cursor or any MCP client can build and edit your Tally forms and read their submissions, with every person signed in as themselves.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Tally to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Tally once
-
Open Connections, choose Add connection, and pick Tally.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Tally. Tally's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Tally MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Tally MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Tally MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Tally to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Tally through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Turn a brief into a lead form
Describe the campaign and the fields you need, and the agent drafts the Tally form, then adjusts questions when the brief changes.
-
Product
Hear what beta testers said this week
Ask for a rundown of the latest submissions to the feedback form and get the recurring requests and complaints grouped, without opening the results tab.
-
People
Draft the onboarding questionnaire for new hires
Set up the questions a new starter answers in their first week, then edit wording or add a section before it goes out.
-
Support
Spot the unhappy answers in a satisfaction survey
Pull the low scores and their comments from the survey submissions so someone can follow up the same day.
-
Events
Build registration and check the headcount
Create the registration form, then ask how many people have signed up and who flagged a dietary requirement.
-
Research
Summarize open-ended answers without the spreadsheet
Read hundreds of free-text responses and get the themes, with example quotes, instead of exporting and scrolling.
Try asking
- “Summarize this week's submissions to the customer feedback form”
- “Add a question about company size to the lead form”
- “Which event registration answers mention a dietary requirement?”
Compare
Elaichi vs Zapier MCP vs Composio for Tally
All three can connect Tally to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Tally tools | Allow or restrict single Tally tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Tally call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Tally gets you
5 screens from the product, each doing one job for your Tally account.
The agent
Ask about submissions in plain language.
Three starter prompts, answers drawn from your live Tally forms and responses.
- forms
- submissions
- questions
- respondents
Ask Elaichi to work across your apps.
Summarize this week's submissions to the customer feedback form
Add a question about company size to the lead form
Which event registration answers mention a dietary requirement?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Tally in every client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Tally toolbox.
Marketing builds forms, Research reads submissions, each scoped to what that team needs.
- Marketing
- Product
- People
- Support
ElaichiToolboxesShared connections
Teammates use Tally without ever seeing a credential.
One person connects Tally, shares it, and the table shows who works through it.
- Marketing
- Product
- People
- Support
ElaichiConnectionsAudit log
Every Tally call is logged, nobody argues later.
When, who, what happened, type and resource, for each form created or submission read.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, a person approves.
New Tally submissions are fetched, grouped, drafted into a digest, approved, and posted back.
Tally digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch forms
Tally
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Tally
Queued
Collections and dashboards
Tally submission numbers arrive without anyone asking.
Four metrics, fourteen days of submissions, a breakdown by team, computed without a model.
Tally health
Refreshed 4 minutes ago · every 15 minutes · from the forms collection
Forms
1,284 ↓ 12%
Submissions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Forms created
Last 14 days
By team
Share of activity
Marketing 34%
Product 27%
People 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Tally to Claude?
In Elaichi, choose Tally and click connect; Tally opens its own sign-in page, you authorize Elaichi, and that is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can now work with your Tally forms and submissions as you.
Does Tally work with ChatGPT and Cursor as well as Claude?
Yes. Tally is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, goes into Claude, ChatGPT, Cursor or any MCP client, and the Elaichi Agent uses it too. Each person signs in as themselves whichever client they open.
What can an AI agent actually do with my Tally data?
With Tally connected, an agent can create a form, add or reword questions on an existing one, and read the submissions a form has collected so it can count, group and summarize them. What it can reach depends on what your own Tally account has set up. Short, concrete asks such as "summarize this week's feedback form submissions" work better than long paragraphs.
Does connecting Tally give the AI access to every form in my workspace?
No. Access follows the person who signed in, so an agent only sees the Tally forms and submissions that person can already open in Tally. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Tally itself allows.
Can I stop an agent from deleting or changing things in Tally?
Yes. Restrictions in Elaichi work per action, so you can allow reading Tally submissions while blocking edits or form creation. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Tally connection when someone leaves?
Offboarding that person in Elaichi ends their access to Tally through every client at once. A shared Tally connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Tally once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Tally MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tally is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Tally?
Yes. Both let Claude, ChatGPT or Cursor use Tally. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Tally call.
How is Elaichi different from Composio for Tally?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Tally: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tally in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.