Tally + Claude
Connect Tally to Claude
Prepare a grounded submission review briefing
Read forms with Claude and Agent200. Prepare a submission review briefing within the configured Tally account scope.
On this page
Overview
Ask Claude for a focused submission review briefing from one selected form. Compare its answer with the retrieved source and separate suggestions from recorded facts.
Start with one identified form. Preserve returned form, question, submission and answer fields; report missing data and keep the workflow read-only.
Provider reference: Tally API.
Use the provider credential described on the Tally parent page. Keep it in secure configuration and verify the selected tenant or account before reading.
- Connector
- Tally
- Works with
- Claude ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Tally enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Tally to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Tally and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Tally form I identify and prepare a submission review briefing. Name the source and use only form, question, submission and answer fields. State access gaps; do not change records.
What should come back
- The selected form is identified.
- Only the returned form, question, submission and answer fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected form ID, account scope, read permission and pagination. Submission pages expose hasMore and total. Follow them before claiming a count; treat answers as personal data where applicable.
Get your API key
Create a key in the Agent200 dashboard. It reaches Tally and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Tally to Claude.
Goal: connect Tally to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/tally/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Tally is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. Check it works with this request: "Read the Tally form I identify and prepare a submission review briefing. Name the source and use only form, question, submission and answer fields. State access gaps; do not change records." What should come back: - The selected form is identified. - Only the returned form, question, submission and answer fields are reported. - Access gaps and missing context are explicit; no source data is changed. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/tally/framework/claude.md
Tally tools Claude can call
-
List forms
Readtally_list_formsFind forms visible to the API token.
-
Read a form
Readtally_get_formRetrieve one identified form.
-
List questions
Readtally_list_questionsRead question definitions for a selected form.
-
List submissions
Readtally_list_submissionsFind submissions with supported filters and pagination.
-
Read a submission
Readtally_get_submissionRetrieve one identified submission.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in Tally.
-
02
Claude picks a tool
It sees the Tally tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Tally with your Agent200 API key, within the endpoints your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The source cannot be read
Check the selected form ID, account scope, read permission and pagination. Submission pages expose hasMore and total. Follow them before claiming a count; treat answers as personal data where applicable.
FAQ
How do I verify this result?
Compare the named form and returned form, question, submission and answer fields with the source. Treat missing information as missing, not as a fact.
