[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)

# Jotform API and MCP server

> Jotform has a full REST API with API keys, and an official hosted MCP server with only 5 tools (checked 17 Oct 2026). The MCP covers listing and creating forms, editing forms, creating a submission and reading submissions. It has no tool for editing a submission, building a report or setting notification emails.

Online form builder: forms you publish, the submissions they collect, and the notification emails, reports and workflows that act on them.

## What is the Jotform API?

Cotlet's Jotform API exposes 10 endpoints for your own Jotform account: list forms, get form, list submissions, get submission, list reports, list notification emails, update submission, archive submissions, set notification recipients and create report. The list_forms endpoint returns forms in your account with ID, title and submission count. Each endpoint takes simple JSON inputs like form_id, query or limit and works both as an operation of the jotform_read or jotform_write MCP tool for agents and as a REST call for scripts.

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

Jotform has a full REST API with API keys, and an official hosted MCP server with only 5 tools (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Jotform with 10 endpoints (6 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Jotform have an official API?

Jotform has a full REST API with API keys, and an official hosted MCP server with only 5 tools (checked 17 Oct 2026). The MCP covers listing and creating forms, editing forms, creating a submission and reading submissions. It has no tool for editing a submission, building a report or setting notification emails.

| Task | Jotform official | Cotlet |
|---|---|---|
| List your forms | Yes: REST API and the official MCP (form_list) | Yes |
| Read submissions of a form | Yes: REST API and the official MCP (get_submissions) | Yes |
| Edit the answers of a submission | Yes: REST API (POST /submission/{id}); not in the official MCP | Yes |
| Create and list reports | Yes: REST API (/form/{id}/reports); not in the official MCP | Yes |
| Set who receives the notification email | Partly: The form properties endpoint changes form settings; a dedicated notification endpoint is not documented in what we read; not in the official MCP | Yes |
| Archive submissions | Partly: Archiving is a Tables and Inbox action; an API archive call is not documented in what we read | Yes |
| Run without an API key or OAuth app | No: API calls need a key from My Account; the MCP needs an OAuth approval | Yes |

Sources: [Jotform API documentation](https://api.jotform.com/docs/), [Jotform MCP server](https://www.jotform.com/mcp/), [Jotform Help: How to Set Up Email Notifications](https://www.jotform.com/help/25-setting-up-email-notifications/), [Jotform Help: How to Edit Submissions in Jotform Tables](https://www.jotform.com/help/325-how-to-edit-submissions-made-on-your-forms/)

## For AI agents

```text
Jotform has a full REST API with API keys, and an official hosted MCP server with only 5 tools (checked 17 Oct 2026). The MCP covers listing and creating forms, editing forms, creating a submission and reading submissions. It has no tool for editing a submission, building a report or setting notification emails.
Cotlet provides a hosted MCP server and REST API for Jotform: 10 tools (6 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=jotform, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    jotform_read, jotform_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/jotform, each operation at its own route, e.g. PATCH /api/v1/jotform/submissions/{submission_id}
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, get_form, list_submissions, get_submission, list_reports, list_notification_emails, update_submission, archive_submissions, set_notification_recipients, create_report
Confirm      set_notification_recipients, create_report (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/jotform-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=jotform, requests Jotform in the Cotlet console and creates an API key there.
2. The user signs in to Jotform once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Jotform 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 Jotform server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Jotform MCP server instead.

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 Jotform 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 Jotform 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 Jotform 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 Jotform's terms; Cotlet is not affiliated with Jotform.
```

## What can an AI agent do in Jotform?

Cotlet is best for form owners and operations teams who want an AI agent to report on, correct and route Jotform submissions without running or fixing a server, or wiring their own OAuth app.

- **[Build response reports for a form](https://cotlet.dev/integrations/jotform-api-mcp-server/build-form-response-reports.md)** (runs: weekly): "Every Monday, build an Excel report of last week's submissions for my Event registration form and tell me how many people signed up and which ticket type is most common." → `list_forms`, `list_submissions`, `create_report`
- **[Correct submission data in bulk](https://cotlet.dev/integrations/jotform-api-mcp-server/correct-submission-data.md)**: "In my Event registration form, find submissions where the email has a typo like "gmial.com" or "gmail.con", fix the domain, and list what you changed." → `get_form`, `list_submissions`, `get_submission`, `update_submission`
- **[Change who gets form notification emails](https://cotlet.dev/integrations/jotform-api-mcp-server/change-form-notification-recipients.md)**: "Our support lead changed. On every form whose notification email goes to maria@example.com, send it to dana@example.com instead, keep the CC, and list the forms you changed." → `list_forms`, `list_notification_emails`, `set_notification_recipients`
- **Summarize new form responses** (runs: daily): "Every morning, read the new submissions of my Contact us form, tell me what people asked in two lines each, and flag any that mention a refund." → `list_forms`, `list_submissions`, `get_submission`
- **Archive handled submissions** (runs: weekly): "Archive every submission in my Job application form that is older than 90 days and that I marked as handled, and tell me how many you moved." → `list_forms`, `list_submissions`, `archive_submissions`

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

Yes. Cotlet does not replace your automation platform: it gives it a Jotform 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 build response reports for a form, 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/jotform/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/jotform/forms with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 10 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 Jotform.

### list_forms

Forms in your account with ID, title and submission count. Access: read. REST: `GET /api/v1/jotform/forms`. MCP: `jotform_read → list_forms`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Only forms whose title contains this text. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the forms your Jotform account can see, newest first, with title, ID and how many submissions each has. Filter by part of the title. Use the form ID with every other tool. Pages hold up to 100 forms; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "forms": [
    {
      "form_id": "242831904782058",
      "title": "Event registration",
      "submissions": 42,
      "created_at": "2026-08-14T10:12:00Z"
    },
    {
      "form_id": "242790155512047",
      "title": "Contact us",
      "submissions": 318,
      "created_at": "2026-03-02T08:40:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_form

One form with its fields: ID, label and type of each. Access: read. REST: `GET /api/v1/jotform/forms/{form_id}`. MCP: `jotform_read → get_form`.

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

Returns the form title and every field in order, with the field ID, the label shown to respondents, the field type and whether it is required. Use the field IDs when you read or edit answers. It reads the form as it is now, so a field added today is in the list.

Example response:

```json
{
  "form_id": "242831904782058",
  "title": "Event registration",
  "fields": [
    {
      "field_id": "3",
      "label": "Full name",
      "type": "text",
      "required": true
    },
    {
      "field_id": "7",
      "label": "Email",
      "type": "email",
      "required": true
    },
    {
      "field_id": "9",
      "label": "Ticket type",
      "type": "dropdown",
      "required": true
    }
  ]
}
```

### list_submissions

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

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `created_from` | string | no | Only submissions created on or after this date, ISO 8601. |
| `created_to` | string | no | Only submissions created before this date, ISO 8601. |
| `query` | string | no | Only submissions where an answer contains this text. |
| `archived` | boolean | no | true to list the archive instead of the inbox. Default: false. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the submissions of a form with ID, date and the answers keyed by field ID. Filter by date range or by text in an answer. Archived submissions are left out unless you ask for them. Pages hold up to 100 submissions; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "submissions": [
    {
      "submission_id": "6012345678901234567",
      "created_at": "2026-10-09T14:21:00Z",
      "answers": {
        "3": "Jordan Ellis",
        "7": "jordan.ellis@gmial.com",
        "9": "Standard"
      }
    },
    {
      "submission_id": "6012345678901234555",
      "created_at": "2026-10-08T09:03:00Z",
      "answers": {
        "3": "Ava Kim",
        "7": "ava.kim@example.com",
        "9": "VIP"
      }
    }
  ],
  "next_cursor": null
}
```

### get_submission

One submission with every answer, labeled by field. Access: read. REST: `GET /api/v1/jotform/submissions/{submission_id}`. MCP: `jotform_read → get_submission`.

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

Returns one submission with its date and each answer next to the label of the field it answers. Use it right before an edit to check the row has not changed since you listed it.

Example response:

```json
{
  "submission_id": "6012345678901234567",
  "form_id": "242831904782058",
  "created_at": "2026-10-09T14:21:00Z",
  "answers": [
    {
      "field_id": "3",
      "label": "Full name",
      "value": "Jordan Ellis"
    },
    {
      "field_id": "7",
      "label": "Email",
      "value": "jordan.ellis@gmial.com"
    },
    {
      "field_id": "9",
      "label": "Ticket type",
      "value": "Standard"
    }
  ]
}
```

### list_reports

Reports built on one form, with type, title and link. Access: read. REST: `GET /api/v1/jotform/forms/{form_id}/reports`. MCP: `jotform_read → list_reports`.

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

Lists the reports of a form: Excel, CSV and visual reports, each with its ID, title, type and link. Use it to find a report before you build another one.

Example response:

```json
{
  "reports": [
    {
      "report_id": "5001234567890",
      "title": "Event registration, week 40",
      "type": "excel",
      "link": "https://www.jotform.com/excel/example-week-40"
    },
    {
      "report_id": "5001234567999",
      "title": "Event registration overview",
      "type": "visual",
      "link": "https://www.jotform.com/report/example-overview"
    }
  ]
}
```

### list_notification_emails

The notification emails of a form with recipients, CC, BCC and trigger events. Access: read. REST: `GET /api/v1/jotform/forms/{form_id}/notification-emails`. MCP: `jotform_read → list_notification_emails`.

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

Returns each Notification Email of a form with its ID, subject, recipients, CC and BCC, and whether it is sent when a submission is received and when one is edited. Use the email ID with set_notification_recipients. A new form has one Notification Email once it has a field.

Example response:

```json
{
  "emails": [
    {
      "email_id": "1",
      "subject": "New Event registration submission",
      "recipients": [
        "maria@example.com"
      ],
      "cc": [
        "team@example.com"
      ],
      "bcc": [],
      "send_on_received": true,
      "send_on_edited": true
    }
  ]
}
```

### update_submission

Change the answers of one submission, field by field. Access: write. REST: `PATCH /api/v1/jotform/submissions/{submission_id}`. MCP: `jotform_write → update_submission`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `submission_id` | string | yes | Submission ID from list_submissions. |
| `answers` | object | yes | Field ID to new value, for example {"7": "jordan.ellis@gmail.com"}. Field IDs come from get_form. |

Changes the answers you pass, keyed by field ID, and leaves every other answer as it was. It works like the inline edit in Jotform Tables: the new value is saved and no notification email or integration runs. It reaches no one and is undone by calling it again with the old value, so it does not ask for confirmation. Submissions of Sign documents cannot be edited.

Example response:

```json
{
  "submission_id": "6012345678901234567",
  "updated_fields": [
    {
      "field_id": "7",
      "label": "Email",
      "old_value": "jordan.ellis@gmial.com",
      "new_value": "jordan.ellis@gmail.com"
    }
  ],
  "notifications_sent": false
}
```

### archive_submissions

Move submissions to the archive, or back to the inbox. Access: write. REST: `POST /api/v1/jotform/forms/{form_id}/submissions/archive`. MCP: `jotform_write → archive_submissions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `submission_ids` | array | yes | Submission IDs from list_submissions. |
| `unarchive` | boolean | no | true to move the submissions back to the inbox. Default: false. |

Archives the submissions you list, or moves them back to the inbox with unarchive set to true. Archiving keeps the entry indefinitely, unlike deleting, which sends it to Trash for 30 days. Archived entries still count toward your submission storage. It reaches no one and is undone in one call, so it does not ask for confirmation.

Example response:

```json
{
  "form_id": "242831904782058",
  "archived": 2,
  "submission_ids": [
    "6012345678901234555",
    "6012345678901234501"
  ]
}
```

### set_notification_recipients

Change who receives a form's notification email. Access: write, asks the user first. REST: `PUT /api/v1/jotform/forms/{form_id}/notification-recipients`. MCP: `jotform_write → set_notification_recipients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `email_id` | string | yes | Notification email ID from list_notification_emails. |
| `recipients` | array | no | Email addresses that replace the current recipients. |
| `cc` | array | no | Email addresses that replace the current CC list. |
| `bcc` | array | no | Email addresses that replace the current BCC list. |

Replaces the recipients, CC or BCC of one Notification Email with the lists you pass and leaves the rest of the email unchanged. Lists you leave out stay as they are. A free account has one Notification Email and one recipient per form, and paid plans allow up to 10 recipients in total, so a longer list is refused with the limit in the error. From then on the people on the list receive every submission of that form, personal data included. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "form_id": "242831904782058",
  "email_id": "1",
  "recipients": [
    "dana@example.com"
  ],
  "cc": [
    "team@example.com"
  ],
  "bcc": []
}
```

### create_report

Create an Excel, CSV or visual report from one form. Access: write, asks the user first. REST: `POST /api/v1/jotform/forms/{form_id}/reports`. MCP: `jotform_write → create_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `form_id` | string | yes | Form ID from list_forms. |
| `type` | enum | yes | excel, csv or visual. |
| `title` | string | no | Report name. Default: the form title. |
| `field_ids` | array | no | Field IDs to include in an Excel or CSV report. Default: all fields. |

Creates a report on one form and returns its link. Excel and CSV reports are plain data exports with the fields you pick, all fields by default. A visual report is the default one Report Builder makes, with the form title and charts for the responses. A report link can reach people outside the form, so the access level of a visual report stays as Jotform sets it and is returned in the response. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "report_id": "5001234567890",
  "form_id": "242831904782058",
  "title": "Event registration, week 41",
  "type": "excel",
  "link": "https://www.jotform.com/excel/example-event-registration"
}
```

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

Connecting Jotform takes three steps: sign up, sign in to Jotform 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 Jotform to your agent.

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

2. **Sign in to Jotform in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Jotform 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 Jotform 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.

```
Every Monday, build an Excel report of last week's submissions for my Event registration form and tell me how many people signed up and which ticket type is most common.
```

### Call Jotform 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/jotform 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/jotform/submissions/6012345678901234567 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"answers":{"7":"jordan.ellis@gmail.com"}}'
```

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

```
{
  "submission_id": "6012345678901234567",
  "updated_fields": [
    {
      "field_id": "7",
      "label": "Email",
      "old_value": "jordan.ellis@gmial.com",
      "new_value": "jordan.ellis@gmail.com"
    }
  ],
  "notifications_sent": false
}
```

## Why use Cotlet for Jotform?

**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 Jotform 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 Jotform changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Jotform to Cotlet?

Yes. You sign in to Jotform yourself, in your own Cloud Browser, and we never save your password. Your agents only get Jotform 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 Jotform integration?**

No, Cotlet is independent of Jotform. Jotform's own API is too limited for this work. Cotlet works through your own Jotform account, the way you use Jotform 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 Jotform in your console: your agents lose access at once and you stay signed in. Signing out of Jotform in the browser works too, and Reset browser deletes the whole profile.

## Is there a Jotform MCP server on GitHub?

Yes. Third-party Jotform MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it a Jotform API key, and fix it when Jotform changes. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an API key in My Account, store it, add the server to each MCP client | Sign up, sign in to Jotform once, add one MCP server or API key |
| When Jotform changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Jotform access | An API key in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you create a new key or fix the server by hand | Your Cloud Browser keeps you signed in; if Jotform logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | 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 Jotform 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 Jotform API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Jotform 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 Jotform 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 Jotform 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 Jotform only after you enable it. When Jotform 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 Jotform, sign out of Jotform 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.
- **Jotform's terms:** You use your own Jotform account and stay responsible for following Jotform's terms. Cotlet is independent and not affiliated with Jotform. [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 Jotform in the console and press Request access. Then you create your API key and connect Jotform there.

**Do I need to be technical?**

No. You sign in to Jotform 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 Jotform to Cotlet?**

Yes. You sign in to Jotform yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Jotform 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 Jotform 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 Jotform 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 Jotform's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Jotform 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 Jotform 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?**

Jotform 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 a Jotform API key or the official MCP for Cotlet?**

No. Cotlet works through your own Jotform login, so you create no API key and install no OAuth app. Jotform API keys have daily request limits by plan, from 1,000 on Starter to unlimited on Enterprise, and the official MCP can only be installed by workspace admins (Jotform API documentation, Jotform MCP server).

**Which plan do I need to set several notification recipients?**

A paid plan. The Starter (free) plan allows one Notification Email and one recipient per form, and paid plans allow up to 10 recipients in total on a Notification Email (Jotform Help: How to Set Up Email Notifications).

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

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

**Can I use the Jotform 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/jotform 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.