Claude Cognito Forms connectorWhat Claude can do in your Cognito Forms account.
The Claude Cognito Forms connector exposes 10 tools. 4 of them read entries, files and documents, 1 changes something in your account, and 5 are described nowhere. Below: what Claude pulls out of your forms, what needs an admin, and where the tool list goes quiet.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for the person who handles form responses
Answering a question about form responses usually means opening Cognito Forms, picking a view and scrolling. With the connector, you ask Claude directly: it reads the entries through the view you name, fetches a file or a generated document, and can even close a form at a set time. All from the conversation.
Answer a question about many entries. An HR lead wants to know how many time-off requests are pending: get_entries_in_view reads the entries of a form through a given entry view, so Claude can count and summarize them.
Retrieve a file or a document. An insurance certificate was uploaded to one entry: get_file pulls it, including electronic signatures, and get_document fetches documents Cognito Forms generated, such as an invoice.
Close a registration on time. set_form_availability sets the availability of a form.
Now what the connector does not do. Cognito Forms says plainly that it cannot import entry data, upload files, or create and manage entry views. Five of the listed tools are described by no source, including the one that looks tied to entries. Cognito Forms documents creating, updating and deleting entries as actions, without naming the tool behind them. Nothing runs by itself either: to act on each new submission, an automation tool is the right job, and the Cognito Forms Make integration page covers it.
The vocabulary in one minute
Five words you will meet while plugging Cognito Forms into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Cognito Forms into Claude in three steps
- 01
Find Cognito Forms in Claude
In Claude's settings, open Customize, then Connectors, and look for Cognito Forms in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Cognito Forms in the window that Cognito Forms opens itself. If the link ever breaks later on, use Disconnect and then plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Cognito Forms, not to Claude, and it is what decides what the access covers. You can also withdraw that access later from your Cognito Forms account.
The 10 tools, sorted by what they do
Cognito Forms gives Claude 10 tools: 4 that read your account, 1 that change something in it, and 5 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 4 read
- 1 write
- 5 not documented
What Claude reads (4)
4 toolsFour tools that read entries, files and documents without touching them.
get_document
Fetches documents generated by Cognito Forms, such as custom documents and the free standard documents it offers.
get_entry
Retrieves one specific entry, which lets Claude answer a precise question about a single submission.
get_file
Pulls files that people uploaded through a form's file upload field, along with electronic signatures captured on the form.
get_entries_in_view
Reads the entries of a form through a specific entry view, which is how Claude answers questions across many submissions at once.
What Claude changes (1)
1 toolOne tool that acts on a form. No source spells out its confirmation, so the general rule below applies.
set_form_availability
Approval: see the ruleSets the availability of a form, a change Cognito Forms records in the organization audit log, like the other changes made through the connector.
Not documented (5)
5 toolsThe directory publishes these five names and nothing else. No official text says what they do, and this page will not guess from a name.
get_entry_views
The directory lists this name and nothing more. Cognito Forms' help article does not mention it, and no page from Claude does either, so this page says nothing further about what it covers.
get_form_schema
Only its name appears on the directory sheet. No official source describes this tool, so any statement about its role would be a guess from the name, which this page refuses to make.
get_forms
Listed by the directory, left without a single line of explanation. Neither Cognito Forms' documentation nor Claude's help center says what it returns or when Claude would call it.
manage_entry
Cognito Forms documents entry-related actions without naming the tool behind them, and no sentence mentions this name. With no source describing it, this page does not say what it can or cannot touch.
provide_mcp_server_feedback
Nothing in the sources describes this tool beyond its listing in the directory. What it transmits, and to whom, is not documented anywhere we could read, on either side.
What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping reading open and closing writing. That setting applies to everyone and nobody gets around it from their own account. Finally, Claude works with your rights and nothing beyond: a form you cannot administer in Cognito Forms stays closed to it too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog rather than a gap in our reading.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. For the live state of this one, go to Cognito Forms's sheet in the official directory, the only place that shows it.
Where the Claude Cognito Forms connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a new entry is submitted or a payment arrives.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it, so the facts here come from the directory sheet and Cognito Forms' help article. That article names actions rather than tools, which is why five tools stay undocumented. Cognito Forms also limits the feature to some of its own subscription tiers. The partner badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. The Integrations hub gathers the automation families.
Need help connecting Cognito Forms to Claude?
A person reads every message.
