Integration

Cognito Forms integration

Cognito Forms is an online form builder. With this API an agent can list the organization's forms, read a form's field schema, create, read, update and delete entries, generate an entry's document from a form template, download an entry's uploaded files, upload a file to attach to an entry, bulk import entries from a spreadsheet, and open or close a form's public link for a date range. Entry field values are never returned (entries are read back as their Id, status, dates and links): forms can hold protected answers such as Password fields, which the API would return in clear. The REST API is available on the Pro, Team and Enterprise plans; each plan includes a monthly number of API requests (2,000, 10,000 or 100,000) shared with Zapier, Make and Power Automate, and calls are rate limited to 300 per 5 minutes. Authentication is an API key created by an organization owner or administrator under Settings, Integrations, sent as a Bearer token; the key's form and entry scopes and the forms it can access decide which tools work.

Connect Cognito Forms How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Cognito Forms.Built from the 12 Cognito Forms tools below, on the connection you add once.

What you can do with Cognito Forms

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Entry, 4 operations

create_entryCreate entryPOSTCreates an entry on a form from field values and returns its Id and metadata (number, status, links). Like an entry made through Zapier or Make, it sends the form's enabled notification emails. Needs Entry Read/Write.
delete_entryDelete entryDELETEPermanently deletes an entry from a form. This cannot be undone. Needs the Entry Read/Write/Delete scope.
get_entryGet entryGETReturns one entry's Id and metadata: number, status, dates, submitting user, entry and document links. Field values are not returned (forms can hold protected answers such as passwords). Needs Entry Read.
update_entryUpdate entryPATCHUpdates an entry: only the fields sent change; an array is sent whole and an empty array clears it. Entries that are Incomplete or have a Paid payment cannot be updated. Returns the Id and metadata. Needs Entry Read/Write.

File, 2 operations

get_entry_fileGet entry fileGETReturns a file uploaded to an entry: Name, ContentType, Size, a File download link and the bytes base64-encoded in Content. Needs Entry Read.
upload_fileUpload filePOSTUploads a file and returns its file Id, to put in a file upload field of create_entry or update_entry. The Id expires if it is not attached to an entry within 48 hours. Needs Entry Read/Write.

Document, 1 operation

get_entry_documentGet entry documentGETReturns an entry's document built from one of the form's document templates: Name, ContentType, Size, a File download link and the bytes base64-encoded in Content. Needs Entry Read.

Form, 1 operation

list_formsList formsGETLists the forms of the organization that the API key can access (archived forms are left out), each with its Id and Name. Pass an Id as formId to the other tools. Needs the Form Read scope.

Import entry, 1 operation

import_entriesImport entriesPOSTImports entries into a form from an .xlsx or .csv file and returns an import Id; poll get_import_status with it. Depending on ImportMode it creates, updates or DELETES entries. Needs Form Read and Entry Read/Write/Delete.

Import status, 1 operation

get_import_statusGet import statusGETReturns the progress of an import started with import_entries: its Status, an ErrorMessage when it failed, and the counts of successful, unsuccessful and total entries. Needs Form Read.

Public link availability, 1 operation

set_form_availabilitySet form availabilityPOSTChanges when the form's public link accepts entries (a start and end date-time) and the message people see outside that window. This changes what respondents see. Needs the Form Read/Write scope.

Schema, 1 operation

get_form_schemaGet form schemaGETReturns the JSON schema of a form: every field with its internal name, data type, description and allowed values. Call it with input=true before create_entry or update_entry to learn which fields can be set. Needs Form Read.

Use Cognito Forms from Claude Code, Cursor or Codex

Connect Cognito Forms in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cognito Forms operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cognito Forms

Create your workspace
Sign up free. Nothing to install.
Connect Cognito Forms once
Add your Cognito Forms connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.