Connect Tally to Claude Code

Read Tally forms, submissions and analytics, and build and manage forms and webhooks. Add Toolspoke to Claude Code once and it can use 15 Tally actions. Your Tally credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Tally and connect it

    Add Tally to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    API key
    Tally → Settings → API keys (tally.so/settings/api-keys) → Create API key. The key acts as you on every workspace you belong to.
  3. Choose what Claude Code may do

    All 15 actions start on. Switch off any of the 6 actions that change something in Tally, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Tally actions that only read, so they are safe to try first.

  • Read the account the key belongs to, including its plan and organization
  • List the forms you can reach, newest first, with their status and submission counts
  • Read one form with all its blocks and settings
  • List a form's questions with their ids and types

What Claude Code can do in Tally

9 actions read, one writes and 5 delete or permanently change something.

Reads

  • Get current user

    Read the account the key belongs to, including its plan and organization.

  • List forms

    List the forms you can reach, newest first, with their status and submission counts. Takes no arguments and proves the key reads real data, which is why an install tests itself with it.

  • Get form

    Read one form with all its blocks and settings. The form id is the code in its share link (tally.so/r/<formId>).

  • List questions

    List a form's questions with their ids and types. The question ids are what submission responses refer to.

  • List submissions

    List a form's submissions with their answers. Answers are what respondents typed, so the response is not written to the audit log.

  • Get submission

    Read one submission with its answers and the form's questions.

  • Get form metrics

    Read a form's aggregate metrics over a period, such as visits, submissions and completion rate.

  • List workspaces

    List your workspaces with their members.

  • List webhooks

    List the webhooks on the forms you can reach, with their target URLs and event types.

Writes

  • Create form

    Create a form as a draft. blocks follow Tally's block reference (developers.tally.so/blocks-reference); a form starts with a FORM_TITLE block. This operation cannot publish: status is limited to BLANK or DRAFT, and publishing is update_form's job.

Deletes or permanently changes

  • Delete submission

    Delete one submission. A respondent's answers cannot be recovered afterwards.

  • Update form

    Change a form's name, blocks, settings or status. Destructive because a published form is public: setting status to PUBLISHED, or editing the blocks of a form that is already live, changes what every respondent sees. blocks replaces the whole form body, so read it with get_form first.

  • Delete form

    Delete a form. It moves to the trash and its share link stops working for respondents at once.

  • Create webhook

    Send a form's submissions to a URL. Destructive because from then on every respondent's answers leave Tally for that address, which may be outside your organization.

  • Delete webhook

    Delete a webhook. Whatever relied on it stops receiving submissions.

Tally in Claude Code: questions

Does Claude Code see my Tally credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Tally?

Yes. Each of the 15 actions can be switched off for a project. Turn off the 6 that change something and Claude Code can only read.

Will 15 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Tally action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Tally call does not run in a sandbox, so it bills nothing.

Try Tally in Claude Code

Free to start, and tool calls cost nothing on any plan.