[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Formstack API and MCP server

> Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 Oct 2026). The API covers forms, fields, folders, submissions, notification and confirmation emails and webhooks. You need the Forms API add-on, a Personal Access Token and your own code. Formstack offers an llms.txt file for coding assistants and does not help build custom integrations.

Online form builder: forms you publish, the submissions they collect, and the notification and confirmation emails, redirects and integrations that run after each submission.

## What is the Formstack API?

Cotlet's Formstack API exposes 12 endpoints for your own Formstack account: list forms, list folders, get form, list submissions, get submission, get notification emails, copy form, move forms to a folder, update submission, update notification recipients, resend notification email and set form availability. The list_forms endpoint returns forms in your account with ID, name, folder and submission count. Each endpoint takes simple JSON inputs like form_id, submission_id or query and works both as an operation of the formstack_read or formstack_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 12 (6 read, 6 write)
- **Updated:** 2026-10-21

Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Formstack with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Formstack have an official API?

Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 Oct 2026). The API covers forms, fields, folders, submissions, notification and confirmation emails and webhooks. You need the Forms API add-on, a Personal Access Token and your own code. Formstack offers an llms.txt file for coding assistants and does not help build custom integrations.

| Task | Formstack official | Cotlet |
|---|---|---|
| List forms and folders, read a form with its fields | Yes: Forms API; add-on, token and your code | Yes |
| Read and search submissions | Yes: Forms API, paginated, with date ranges and field search | Yes |
| Edit a submission | Yes: Forms API, PUT on one submission | Yes |
| Copy a form | Yes: Forms API, copy endpoint | Yes |
| Change the recipients of a notification email | Yes: Forms API, notification email endpoints with recipients and conditional logic | Yes |
| Close a form on a date or after a number of submissions | Partly: Forms API updates form properties; the reference we read does not list the disable settings | Yes |
| Resend a notification email for one submission | No: A Resend button in the app; the API reference lists no resend endpoint | Yes |
| Use it without the API add-on, a token or code | No: The add-on comes from Formstack sales | Yes |

Sources: [Formstack blog: Introducing the Formstack Forms 2025 API](https://www.formstack.com/blog/introducing-formstack-forms-2025-api-a-more-secure-modern-and-developer-friendly-way-to-build), [Formstack developers: API reference index (llms.txt)](https://developers.formstack.com/llms.txt), [Formstack Help: Formstack API Overview](https://help.formstack.com/hc/en-us/articles/44593115536403-Formstack-API-Overview), [Formstack Help: Formstack Personal Access Tokens](https://help.formstack.com/hc/en-us/articles/44593278449555-Formstack-Personal-Access-Tokens)

## For AI agents

```text
Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 Oct 2026). The API covers forms, fields, folders, submissions, notification and confirmation emails and webhooks. You need the Forms API add-on, a Personal Access Token and your own code. Formstack offers an llms.txt file for coding assistants and does not help build custom integrations.
Cotlet provides a hosted MCP server and REST API for Formstack: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=formstack, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    formstack_read, formstack_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/formstack, each operation at its own route, e.g. PATCH /api/v1/formstack/forms/{form_id}/notifications/{notification_id}/recipients
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_forms, list_folders, get_form, list_submissions, get_submission, get_notification_emails, copy_form, move_forms_to_folder, update_submission, update_notification_recipients, resend_notification, set_form_availability
Confirm      copy_form, update_submission, update_notification_recipients, resend_notification, set_form_availability (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/formstack-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=formstack, requests Formstack in the Cotlet console and creates an API key there.
2. The user signs in to Formstack once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Formstack for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Formstack server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Formstack in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Formstack only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Formstack login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Formstack's terms; Cotlet is not affiliated with Formstack.
```

## What can an AI agent do in Formstack?

Cotlet is best for Formstack admins and ops teams who want their AI agent to reroute notification emails, fix submissions and close full forms, with no API add-on, without running or fixing a server.

- **[Change notification email recipients](https://cotlet.dev/integrations/formstack-api-mcp-server/change-notification-recipients.md)**: "In the Events folder, find every Formstack form that sends its notification email to sam@example.com. Replace him with dana@example.com, keep other recipients and leave forms that route by answer for me." → `list_forms`, `get_notification_emails`, `update_notification_recipients`
- **[Fix typos in form submissions](https://cotlet.dev/integrations/formstack-api-mcp-server/correct-submission-data.md)**: "In Event registration, find submissions where the email ends in gmial.com or gmail.con, correct the domain, and list anything else that looks wrong for me." → `list_submissions`, `get_submission`, `update_submission`
- **[Close a form after a set number of entries](https://cotlet.dev/integrations/formstack-api-mcp-server/close-form-after-limit.md)**: "Close every form in the Events folder after 150 submissions, with the message "Registration is full." Tell me which ones already have more." → `list_forms`, `get_form`, `set_form_availability`
- **Copy a form for a new campaign**: "Copy the Event registration form as "Autumn gala registration" and move the copy into the Events 2027 folder." → `list_folders`, `copy_form`, `move_forms_to_folder`
- **Resend a missed notification**: "Dana did not get yesterday's Contact us submissions. Resend those notification emails to her." → `list_submissions`, `get_submission`, `resend_notification`
- **Weekly digest of new submissions** (runs: weekly): "Every Monday, count last week's submissions on each form in the Sales folder and list the three busiest." → `list_forms`, `list_submissions`

## Can Formstack automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Formstack connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to weekly digest of new submissions, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/formstack/forms. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/formstack/forms with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Formstack.

### list_forms

Forms in your account with ID, name, folder and submission count. Access: read. REST: `GET /api/v1/formstack/forms`. MCP: `formstack_read → list_forms`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Only forms whose name contains this text. |
| `folder_id` | string | no | Only forms in this folder, from list_folders. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the forms your Formstack login can open, with name, folder and how many submissions each holds. Filter by part of the name or by folder. Forms in the Archived Forms folder come with that folder name. Use the form ID with every other tool. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "forms": [
    {
      "form_id": "5128834",
      "name": "Event registration",
      "folder": "Events",
      "submissions": 42,
      "created_at": "2026-08-14T10:12:00Z"
    },
    {
      "form_id": "5071209",
      "name": "Contact us",
      "folder": "Uncategorized",
      "submissions": 318,
      "created_at": "2026-03-02T08:40:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_folders

Folders and subfolders that hold your forms. Access: read. REST: `GET /api/v1/formstack/folders`. MCP: `formstack_read → list_folders`.

No parameters.

Returns every folder you can see with its ID, name and parent folder. A user with restricted permissions sees only the folders that hold forms in their permissions. Use the folder ID to filter list_forms or to move forms.

Example response:

```json
{
  "folders": [
    {
      "folder_id": "774120",
      "name": "Events",
      "parent_id": null
    },
    {
      "folder_id": "774133",
      "name": "Events 2027",
      "parent_id": "774120"
    }
  ]
}
```

### get_form

One form with its fields, availability and number of notification emails. Access: read. REST: `GET /api/v1/formstack/forms/{form_id}`. MCP: `formstack_read → get_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |

Returns the form name, folder and availability, then every field in order with its ID, label, type, whether it is required and whether it carries conditional logic. Availability says whether the form closes on a date or after a number of submissions. It reads the form as it is now, so a field added today is in the list.

Example response:

```json
{
  "form_id": "5128834",
  "name": "Event registration",
  "folder": "Events",
  "availability": {
    "disable": "never"
  },
  "fields": [
    {
      "field_id": "48211325",
      "label": "Full name",
      "type": "name",
      "required": true,
      "has_logic": false
    },
    {
      "field_id": "48211330",
      "label": "Email",
      "type": "email",
      "required": true,
      "has_logic": false
    },
    {
      "field_id": "48211341",
      "label": "Dietary needs",
      "type": "dropdown",
      "required": false,
      "has_logic": true
    }
  ],
  "notification_emails": 1
}
```

### list_submissions

Submissions of one form with their answers, newest first. Access: read. REST: `GET /api/v1/formstack/forms/{form_id}/submissions`. MCP: `formstack_read → list_submissions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `view` | string | no | all, read, unread or favorited. Default: all. |
| `query` | string | no | Only submissions where an answer contains this text. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the submissions of a form with ID, date, read and favorited flags and the answers keyed by field ID. The view is the one in the Submissions tab: all, read, unread or favorited. The query is the same text search as the search bar. Pass next_cursor back as cursor for the next page. The Submissions tab needs access: without it Formstack shows nothing to read.

Example response:

```json
{
  "submissions": [
    {
      "submission_id": "1128305944",
      "submitted_at": "2026-10-21T14:21:00Z",
      "read": false,
      "favorited": false,
      "answers": {
        "48211325": "Jordan Ellis",
        "48211330": "jordan.ellis@gmial.com",
        "48211341": "Vegetarian"
      }
    },
    {
      "submission_id": "1128301377",
      "submitted_at": "2026-10-20T09:03:00Z",
      "read": true,
      "favorited": true,
      "answers": {
        "48211325": "Ava Kim",
        "48211330": "ava.kim@example.com",
        "48211341": "None"
      }
    }
  ],
  "next_cursor": null
}
```

### get_submission

One submission with every answer and its integration status. Access: read. REST: `GET /api/v1/formstack/submissions/{submission_id}`. MCP: `formstack_read → get_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `submission_id` | string | yes | Submission ID from list_submissions. |

Returns the single view of a submission: the data submitted, the browser, the IP address, the unique ID and the status of its integrations. A failed integration shows as failed. The call does not mark the submission as read and does not run an integration again.

Example response:

```json
{
  "submission_id": "1128305944",
  "form_id": "5128834",
  "submitted_at": "2026-10-21T14:21:00Z",
  "unique_id": "f7c2a91e",
  "browser": "Chrome 141 on macOS",
  "ip_address": "203.0.113.24",
  "answers": {
    "48211325": "Jordan Ellis",
    "48211330": "jordan.ellis@gmial.com",
    "48211341": "Vegetarian"
  },
  "integrations": [
    {
      "name": "Mailchimp",
      "status": "failed"
    }
  ]
}
```

### get_notification_emails

The notification emails of one form with recipients and send options. Access: read. REST: `GET /api/v1/formstack/forms/{form_id}/notification-emails`. MCP: `formstack_read → get_notification_emails`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |

Returns every notification email set up on the form: ID, recipients, whether it sends all the data, a link to the data or a custom message, the message format (HTML or plain text), the reply-to address and whether Email Logic routes it by answer. Formstack creates one on every form. Forms on a trial account send none.

Example response:

```json
{
  "form_id": "5128834",
  "notification_emails": [
    {
      "notification_id": "30912774",
      "enabled": true,
      "recipients": [
        "sam@example.com",
        "events@example.com"
      ],
      "send": "all_data",
      "format": "html",
      "reply_to": null,
      "has_email_logic": false
    }
  ]
}
```

### copy_form

Copy a form into your own account, optionally under a new name. Access: write, asks the user first. REST: `POST /api/v1/formstack/forms/{form_id}/copy`. MCP: `formstack_write → copy_form`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `name` | string | no | Name for the copy. Default: the original name with "- COPY" added. |

Makes a copy of the form in your own account, the same as Copy > My Account in the Forms tab. Formstack names it after the original with "- COPY" added; pass name to rename it. The copy lands in the original's folder and the original is not changed. It counts toward the form allowance of your plan, and a copy you do not want is deleted by hand in Formstack. Copying to another account is not part of this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "5192046",
  "name": "Autumn gala registration",
  "folder": "Events",
  "copied_from": "5128834"
}
```

### move_forms_to_folder

Move one or more forms into a folder, or into a new one. Access: write. REST: `POST /api/v1/formstack/forms-to-folder/move`. MCP: `formstack_write → move_forms_to_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_ids` | string[] | yes | Form IDs from list_forms. |
| `folder_id` | string | no | Folder ID from list_folders. Give this or new_folder_name. |
| `new_folder_name` | string | no | Name of a folder to create and move the forms into. |

Moves the forms into the folder, the same as the move to option in the Forms tab. Give folder_id for an existing folder, or new_folder_name to create it and move in one step. Moving reaches no one and is undone by moving the forms back, so it does not wait for your OK. Moving a form out of a folder removes it from users who only have access to that folder.

Example response:

```json
{
  "moved": [
    "5192046"
  ],
  "folder": {
    "folder_id": "774133",
    "name": "Events 2027"
  }
}
```

### update_submission

Change answers on a submission and return the old values. Access: write, asks the user first. REST: `PATCH /api/v1/formstack/submissions/{submission_id}`. MCP: `formstack_write → update_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `submission_id` | string | yes | Submission ID from list_submissions. |
| `answers` | object | yes | Field ID from get_form mapped to the new value. |

Edits the listed fields of a submission, the same as edit in the single view. It sends only the fields you pass. The response returns the old and new value of each field, because Formstack cannot revert an edit and the old value is the only way back. It does not resend notification emails or run an integration again. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "submission_id": "1128305944",
  "updated": [
    {
      "field_id": "48211330",
      "label": "Email",
      "old": "jordan.ellis@gmial.com",
      "new": "jordan.ellis@gmail.com"
    }
  ]
}
```

### update_notification_recipients

Set who receives one notification email of a form. Access: write, asks the user first. REST: `PATCH /api/v1/formstack/forms/{form_id}/notifications/{notification_id}/recipients`. MCP: `formstack_write → update_notification_recipients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `notification_id` | string | yes | Notification email ID from get_notification_emails. |
| `recipients` | string[] | yes | Email addresses that should receive it. |

Replaces the recipients of a notification email with the list you pass, the same as editing the Notification Email section of the form's Settings > Emails & Redirects. Pass the full list, including recipients to keep. The response returns the old and the new list. It changes recipients only: send option, message and Email Logic stay as they are. The next submission goes to the new list. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "5128834",
  "notification_id": "30912774",
  "old_recipients": [
    "sam@example.com",
    "events@example.com"
  ],
  "recipients": [
    "dana@example.com",
    "events@example.com"
  ]
}
```

### resend_notification

Resend the notification email of one submission to chosen addresses. Access: write, asks the user first. REST: `POST /api/v1/formstack/submissions/{submission_id}/notification/resend`. MCP: `formstack_write → resend_notification`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `submission_id` | string | yes | Submission ID from list_submissions. |
| `recipients` | string[] | yes | Email addresses to send it to. |

Sends the notification email of one submission to the addresses you pass, the same as the Resend button on the single submission view. It is a one-time send and does not add them as recipients of the form. The addresses can be outside your Formstack account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "submission_id": "1128305944",
  "sent_to": [
    "dana@example.com"
  ]
}
```

### set_form_availability

Close a form now, on a date or after a number of submissions, or reopen it. Access: write, asks the user first. REST: `PUT /api/v1/formstack/forms/{form_id}/availability`. MCP: `formstack_write → set_form_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `disable` | string | yes | now, on_date, after_submissions or never. |
| `on_date` | string | no | Date and time to close, ISO 8601. Used with on_date. |
| `after_submissions` | integer | no | Close after this many submissions. Used with after_submissions. |
| `message` | string | no | Text visitors see when the form is closed. Default: the Formstack message. |

Sets the Disable Form setting in the form's General Settings. The disable value is now, on_date, after_submissions or never. Now moves the form to the Archived Forms folder. The other two keep the form in its folder with a red badge next to its name. Visitors see the default closed message or the one you pass. Never reopens an expired form; an archived form is restored from the Archived Forms folder in Formstack. Save and Resume does not work while the form is closed. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "5128834",
  "disable": "after_submissions",
  "after_submissions": 150,
  "message": "Registration is full.",
  "folder": "Events"
}
```

## How do I connect Formstack to Claude Code, Codex or Cursor?

Connecting Formstack takes three steps: sign up, sign in to Formstack once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Formstack to your agent.

1. **Create an account** Sign up and add Formstack in the console. Your API key is there too.

2. **Sign in to Formstack in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Formstack there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Formstack tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
In the Events folder, find every Formstack form that sends its notification email to sam@example.com. Replace him with dana@example.com, keep other recipients and leave forms that route by answer for me.
```

### Call Formstack from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/formstack with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/formstack/forms/5128834/notifications/30912774/recipients \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"recipients":["dana@example.com","events@example.com"]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "form_id": "5128834",
  "notification_id": "30912774",
  "old_recipients": [
    "sam@example.com",
    "events@example.com"
  ],
  "recipients": [
    "dana@example.com",
    "events@example.com"
  ]
}
```

## Why use Cotlet for Formstack?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Formstack yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Formstack changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Formstack to Cotlet?

Yes. You sign in to Formstack yourself, in your own Cloud Browser, and we never save your password. Your agents only get Formstack once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Formstack integration?**

No, Cotlet is independent of Formstack. Formstack's own API is too limited for this work. Cotlet works through your own Formstack account, the way you use Formstack in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Formstack in your console: your agents lose access at once and you stay signed in. Signing out of Formstack in the browser works too, and Reset browser deletes the whole profile.

## Is there a Formstack MCP server on GitHub?

Zapier has a Formstack app. It starts a Zap on a new form or a new submission, creates a submission, and offers a raw API Request action (beta) where you write the HTTP call yourself. It has no search actions. Zapier is the right tool to react to a new submission; Cotlet is for an agent that reads and changes your forms, submissions and notification emails.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Add a connection, log in to Formstack to authorize it, build a Zap for each job | Sign up, sign in to Formstack once, add one MCP server or API key |
| What it does in Formstack | Two triggers (new form, new submission), one action (create a submission), raw API Request | Reads forms and submissions, edits a submission, changes notification recipients, closes and copies forms |
| When Formstack changes | It runs on the Formstack API, so changes to the web app do not touch it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Formstack session | A connection to your account, authorized with a Formstack login | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You reconnect the app in Zapier | Your Cloud Browser keeps you signed in; if Formstack logs you out, your agent gets a link to sign in again |
| Where it runs | In Zapier, as Zaps on a trigger | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | A Zapier plan; Zapier needs a paid Formstack account | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Formstack changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Formstack API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Formstack API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Formstack account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Formstack yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Formstack only after you enable it. When Formstack signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Formstack, sign out of Formstack in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Formstack's terms:** You use your own Formstack account and stay responsible for following Formstack's terms. Cotlet is independent and not affiliated with Formstack. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Formstack in the console and press Request access. Then you create your API key and connect Formstack there.

**Do I need to be technical?**

No. You sign in to Formstack once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Formstack to Cotlet?**

Yes. You sign in to Formstack yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Formstack once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Formstack sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Formstack cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Formstack's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Formstack sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Formstack login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Formstack offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need the Formstack API add-on or a token for Cotlet?**

No. Cotlet works in your signed-in Formstack account and does not use the Forms API. Formstack says the V2025 API is available to Forms customers with the API add-on, and Personal Access Tokens are enabled by an admin. What your agent can do follows your Formstack permissions: a user with restricted access sees only the folders and forms in their permissions, and the Submissions tab needs access.

**What can it not do?**

No tool builds or edits fields, conditional logic, Email Logic rules, themes or confirmation emails. get_form reads the fields and flags the ones that carry logic, and the notification tools change recipients only. Copying goes to your own account, not to another one. Deleting forms and submissions is left out on purpose. The Forms API does cover fields, logic and confirmation emails if you want them through code.

**Can my agent post or send messages in Formstack without asking me?**

No. Every call to copy_form, update_submission, update_notification_recipients, resend_notification or set_form_availability waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. move_forms_to_folder runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Formstack API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/formstack from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.