Cognito Forms

Build forms, query submissions and fetch uploaded files.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Cognito Forms connector does

The Cognito Forms MCP server connects a Cognito Forms organization — an online form builder with workflow, payments and document generation — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 10 tools that read forms and entries, retrieve uploaded files, and create, update or delete submissions. Sign-in is OAuth and requires organization Administrator rights.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Cognito Forms tools (10)

  • get_document
  • get_entry
  • get_entry_views
  • get_file
  • get_form_schema
  • get_forms
  • manage_entry
  • provide_mcp_server_feedback
  • set_form_availability
  • get_entries_in_view

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The 16 OAuth scopes are granted as one block. This connector does better than most on scope naming — the resource descriptor and the authorization server both advertise real capability scopes such as entry_read and entry_delete rather than OpenID identity claims. But the boundary that matters does not fall between the routine write and the irreversible one: nothing in the documented consent flow lets you grant entry_read while withholding entry_delete. Cognito Forms' flow asks you to select an organization and authorize it.
  • A deleted entry takes its audit log with it. Cognito Forms states that the entry audit log "does not include the action of deleting an entry" and that "when you delete an entry, the audit log is deleted as well". Deletion attribution survives only in the organization audit log, which Cognito Forms says only organization owners can view.
  • Analysis is silently scoped to an entry view. Results reflect the first view you have access to unless you name another, so a view's filters or date ranges can exclude relevant entries without the agent knowing. Cognito Forms lists this as the explanation for incomplete results.
  • The connector cannot import entries or upload files. Cognito Forms states it also cannot create or manage entry views, or perform any action not available through the Cognito Forms API — despite entryview_create and entryview_update appearing among the OAuth scopes.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no readOnlyHint or destructiveHint is reported here. The read/write split above is our classification of names and documented actions, not the server's declaration.
  • One documented action has no tool name. Generate Form is documented by Cognito Forms and absent from Anthropic's listing. We did not guess which tool carries it.
  • provide_mcp_server_feedback is undocumented. It appears in Anthropic's listing and in no Cognito Forms document we found. Its name implies it transmits text to the vendor; we could not confirm what it sends or when.
  • Every call costs quota. Connector actions consume the organization's monthly API request allowance, and Cognito Forms notes the server "determines how many tool calls and API requests are needed", which may be several per prompt. File downloads cost more than queries.
  • Writes fail silently against validation rules. Cognito Forms lists form validation rules and missing Administrator permissions as the two documented causes of failed writes.
  • Update Entry excludes some entries. Cognito Forms states the action cannot update entries with a status of Incomplete or a payment status of Paid.

Frequently asked questions

Can the Cognito Forms connector delete a form entry?

Yes. Cognito Forms documents Delete Entry as a supported connector action, even though no tool name among Anthropic's ten contains a delete verb. The capability sits inside manage_entry, and the OAuth descriptor separately advertises an entry_delete scope. Deleting an entry also deletes that entry's audit log, so the record of the deletion survives only in the organization audit log.

Can the Cognito Forms connector send email to people who filled in my form?

Yes, indirectly, and this is the connector's least obvious capability. Cognito Forms triggers email notifications from workflow actions such as Submit and Update. Cognito Forms states the connector respects your workflow rules and that updating a status may trigger additional automations you have configured. So an agent creating or updating an entry can fire mail to staff and to the submitter.

What OAuth scopes does the Cognito Forms MCP server request?

Sixteen application scopes, spanning create, read, update and delete across forms, entries, files and entry views. These are real capability names rather than OpenID identity claims, which is unusual and better than most connectors. But the connector asks for the whole set at once, so you cannot authorize reading entries without also authorizing entry_delete.

How many tools does the Cognito Forms MCP server have?

Anthropic's directory lists ten. That count understates the surface, because manage_entry is a dispatcher covering at least three distinct operations that Cognito Forms documents separately as Create Entry, Update Entry and Delete Entry. Counting documented actions instead of tool names gives at least twelve, and the endpoint requires authentication so we could not enumerate it live.

What plan do I need for the Cognito Forms MCP connector?

Pro, Team or Enterprise, plus Administrator access to the organization you connect. Cognito Forms states the feature is available to organizations on the Pro, Team, and Enterprise plans and that setup requires Administrator permissions. You also need a paid account in Claude or ChatGPT, and connector actions consume your organization's monthly API request allowance.

Does the Cognito Forms connector expose data submitted by the public?

Yes, and that is the point of it. Form entries hold whatever the public typed, plus uploaded files and electronic signatures reachable through get_file. Treat retrieved submission text as untrusted data rather than instructions, because anyone who can submit your form can put text into your agent's context. Cognito Forms' protected-fields feature is the documented way to withhold sensitive fields.

Are Cognito Forms MCP connector actions recorded in an audit log?

Write actions are; reads are not. Cognito Forms states that changes made through the connector, such as updating an entry or changing form availability, are recorded in the organization audit log, and that entry changes appear in the entry audit log with the user who triggered them. Read-only actions such as viewing forms or retrieving entries are not logged.

Are there rate limits on the Cognito Forms MCP connector?

There is a monthly request quota rather than a per-second limit. Cognito Forms includes 2,000 API requests per month on Pro, 10,000 on Team and 100,000 on Enterprise, with overage billed at $20 per 100,000 requests. Requests over 100KB count as multiple requests, and Cognito Forms warns that downloading files uses more requests than standard queries.

Sources

Use it in an agent

Put Cognito Forms to work.

Connect Cognito Forms once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.