Provider REST API

15 actions

Connect Claude to Tally

Read Tally forms, submissions and analytics, and build and manage forms and webhooks. Toolspoke puts 15 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 15
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Tally
Open the marketplace in your workspace, add Tally to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Tally shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Tally asks for

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 keyRequired: Tally → Settings → API keys (tally.so/settings/api-keys) → Create API key. The key acts as you on every workspace you belong to.; tly-…

What Claude can do in Tally

15 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 9Reads
Writes: 1Writes
Destructive: 5Destructive

Reads

Fetches data and changes nothing.

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

Creates or updates something on the other side.

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.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

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.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 15 actions above are the whole of it. A call to any other name is refused before it reaches Tally rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Tally of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Tally: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Tally. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Tally's own rate limits. A call that Tally refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Tally?

15 named actions: 9 that only read, 1 that write and 5 that delete or permanently alter something. They include get_current_user, list_forms and get_form. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Tally connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Tally connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 15 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Tally connector not do?

The 15 actions above are the whole of it. A call to any other name is refused before it reaches Tally rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Tally of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Tally. An agent has to ask. Toolspoke does not retry, queue or back off around Tally's own rate limits. A call that Tally refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Tally's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Tally?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More productivity connectors

Browse all of them