Skip to content

Tally MCP connector

Connect Tally to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can build and edit your Tally forms and read their submissions, with every person signed in as themselves.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Summarize this week's submissions to the customer feedback form

Working in Tally with Elaichi

  • Looked in Tally
Ask anything…
Governance / Audit log Last 24 hours
Tally Looked in Tally Emily Carter · ChatGPT · 9:41 AM Done
Tally Looked in Tally Megan Brooks · Claude · 9:38 AM Done
Tally Looked in Tally Ryan Hayes · Cursor · 9:35 AM Done

How to connect Tally to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Tally MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Tally MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Tally MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Tally MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Tally to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Tally through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Tally is logged.

  • 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?”

What connecting Tally gets you

5 screens from Elaichi, each doing one job for your Tally account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about submissions in plain language.

Three starter prompts, answers drawn from your live Tally forms and responses.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint puts Tally in every client.

Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.

ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

Tally · lead forms and campaign feedback

Tally starter 18 Mar 4, 2026

Product toolbox

Tally · beta feedback and feature requests

— 9 Mar 2, 2026

People toolbox

Tally · hiring and onboarding questionnaires

— 24 Feb 27, 2026

Support toolbox

Tally · satisfaction surveys and follow-ups

Tally starter 6 Feb 19, 2026

Events toolbox

Tally · registrations and attendee details

— 31 Jan 30, 2026

Research toolbox

Tally · open-ended answers and study responses

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Tally toolbox.

Marketing builds forms, Research reads submissions, each scoped to what that team needs.

ElaichiConnections
Connection Scope Status Access
TA

Tally (Marketing)

Connected by Emily Carter

Personal • Active 1 team · 6 members
TA

Tally (Product)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
TA

Tally (People)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
TA

Tally (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
TA

Tally (Events)

Connected by Ryan Hayes

Personal • Active Not shared
TA

Tally (Research)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Tally without ever seeing a credential.

One person connects Tally, shares it, and the table shows who works through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Tally Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Tally Forms Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Tally Forms List Toolbox

Audit log

Every Tally call is logged, nobody argues later.

When, who, what happened, type and resource, for each form created or submission read.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Tally digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch forms

    Tally

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Tally

    Queued

Workflows

A schedule starts the work, a person approves.

New Tally submissions are fetched, grouped, drafted into a digest, approved, and posted back.

Tally health

Refreshed 4 minutes ago · every 15 minutes · from the forms collection

Live

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%

Collections and dashboards

Tally submission numbers arrive without anyone asking.

Four metrics, fourteen days of submissions, a breakdown by team, computed without a model.

Why connect Tally's MCP server through Elaichi

Tally builds and runs this MCP server. Elaichi sits in front of it, so Tally's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Tally's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Tally's tools at the same Elaichi address as every other connected app. Nobody adds Tally's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Tally sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Tally's server. By default, a tool Tally does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Tally

    Tally builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Tally team.

    tally.so/support

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Tally, by what to check
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 Free for one person; $15 per user per month on Gold. 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.

Questions, answered

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, Microsoft Copilot 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 my team share one Tally connection?

Yes. One person connects Tally in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a form or read its submissions, not the account owner.

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 restricting edits or form creation. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot