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

# Thought Industries API and MCP server

> Thought Industries has a REST API and a GraphQL API, but no MCP server you can connect today (checked 23 Oct 2026). Both APIs need a key an admin creates under Settings > Security, and the Claude plugin lists "a Thought Industries instance with API access enabled" as a prerequisite. The MCP server is announced, and the Claude plugin is in beta and writes drafts only.

Learning platform for customer, partner and employee training: courses, learning paths, webinars, certificates and client portals called Panoramas.

## What is the Thought Industries API?

Cotlet's Thought Industries API exposes 11 endpoints for your own Thought Industries account: list learners, get learner access, list courses, get course enrollment settings, list content actions, list Auto Assignment rules, enroll learner, import and invite learners, set content status, add learner to waitlist and remove learner from waitlist. The list_learners endpoint returns learners of your academy with email and Panorama; search by name or email. Each endpoint takes simple JSON inputs like learner, content_id or cursor and works both as an operation of the thought_industries_read or thought_industries_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Courses & training](https://cotlet.dev/integrations/category/courses-training.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-20

Thought Industries has a REST API and a GraphQL API, but no MCP server you can connect today (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Thought Industries with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Thought Industries have an official API?

Thought Industries has a REST API and a GraphQL API, but no MCP server you can connect today (checked 23 Oct 2026). Both APIs need a key an admin creates under Settings > Security, and the Claude plugin lists "a Thought Industries instance with API access enabled" as a prerequisite. The MCP server is announced, and the Claude plugin is in beta and writes drafts only.

| Task | Thought Industries official | Cotlet |
|---|---|---|
| List learners and read a learner profile | Yes: REST users list and details, with a key and code | Yes |
| List courses and read enrollment limits | Yes: REST content and course calls, with a key and code | Yes |
| Read enrollments, completions and certificates | Yes: Course Actions feed in REST, Content Actions Log in the admin | Yes |
| Enroll existing learners in courses | Yes: REST bulk content assignment takes users by ID or email | Yes |
| Import and invite new learners | Partly: REST bulk import takes the URL of a CSV file; the help center says a bulk upload through the API needs developer support | Yes |
| Set a learner's status on a course | Partly: Through a CSV import, not a call of its own | Yes |
| Add or remove a learner on a waitlist | No: The BI Connector reads waitlists; the REST docs list no call to change one | Yes |
| Read Auto Assignment rules | No | Yes |

Sources: [Thought Industries developer docs: MCP Server](https://developer.thoughtindustries.com/docs/mcp-server/), [Thought Industries developer docs: REST API](https://developer.thoughtindustries.com/docs/rest/), [Thought Industries developer docs: TI Admin Claude Plugin](https://developer.thoughtindustries.com/docs/claude-plugin/), [Thought Industries Help: Zapier](https://support.thoughtindustries.com/hc/en-us/articles/360045745514-Zapier)

## Quick reference

```text
Thought Industries has a REST API and a GraphQL API, but no MCP server you can connect today (checked 23 Oct 2026). Both APIs need a key an admin creates under Settings > Security, and the Claude plugin lists "a Thought Industries instance with API access enabled" as a prerequisite. The MCP server is announced, and the Claude plugin is in beta and writes drafts only.
Cotlet provides a hosted MCP server and REST API for Thought Industries: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=thought-industries, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    thought_industries_read, thought_industries_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/thought-industries, each operation at its own route, e.g. POST /api/v1/thought-industries/contents/{content_id}/learner/enroll
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_learners, get_learner, list_courses, get_course, list_content_actions, list_auto_assignment_rules, enroll_learner, import_learners, set_content_status, add_to_waitlist, remove_from_waitlist
Confirm      enroll_learner, import_learners, set_content_status, add_to_waitlist, remove_from_waitlist (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/thought-industries-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=thought-industries, requests Thought Industries in the Cotlet console and creates an API key there.
2. The user signs in to Thought Industries once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Thought Industries 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 Thought Industries 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 Thought Industries 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 Thought Industries 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 Thought Industries 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 Thought Industries's terms; Cotlet is not affiliated with Thought Industries.
```

## What can an AI agent do in Thought Industries?

Cotlet is best for Thought Industries admins who want an AI agent to enroll learners, send invites and report completions without running or fixing a server.

- **[Enroll new hires in onboarding courses](https://cotlet.dev/integrations/thought-industries-api-mcp-server/enroll-new-hires-in-courses.md)** (runs: weekly): "Import this week's new hires from the list below into Thought Industries, enroll them in the Onboarding 101 course and send the invite with this message." → `list_courses`, `import_learners`, `list_content_actions`
- **[Weekly course completion report](https://cotlet.dev/integrations/thought-industries-api-mcp-server/weekly-course-completion-report.md)** (runs: weekly): "Every Monday, list who completed a course last week in Thought Industries, count completions per course and tell me who lost access." → `list_content_actions`
- **[Enroll a learner in a course](https://cotlet.dev/integrations/thought-industries-api-mcp-server/enroll-learner-in-course.md)**: "Enroll priya.nair@example.com in Safety basics. Check first what she already has and whether the course has a seat limit." → `list_learners`, `get_learner`, `list_courses`, `get_course`, `enroll_learner`
- **Mark external training as completed**: "Mark Tom Becker as completed in Safety basics with the completion date 2026-10-14, he passed the course at the partner site." → `get_learner`, `set_content_status`
- **Move a learner off a waitlist into a course**: "A seat opened in the June webinar. Enroll Sam Okafor, who is waitlisted for it, and take him off the waitlist." → `get_learner`, `get_course`, `enroll_learner`, `remove_from_waitlist`

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

Yes. Cotlet does not replace your automation platform: it gives it a Thought Industries 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 enroll new hires in onboarding courses, 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/thought-industries/courses. | 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/thought-industries/courses with your API key. | cron or GitHub Actions. |

## Tools

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

### list_learners

Learners of your academy with email and Panorama; search by name or email. Access: read. REST: `GET /api/v1/thought-industries/learners`. MCP: `thought_industries_read → list_learners`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a learner name or email. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the Users > Learners list. Returns each learner's learner_id, name, email and Panorama. Pass learner_id or the email to get_learner, enroll_learner and set_content_status. Use cursor to read the next page. Reading changes nothing.

Example response:

```json
{
  "learners": [
    {
      "learner_id": "3f9a2b18-7c4d-4e2a-9b1f-0c5d6e7f8a90",
      "name": "Priya Nair",
      "email": "priya.nair@example.com",
      "panorama": "Retail"
    },
    {
      "learner_id": "5e1d7c2a-9b8f-4e3d-8c0a-1b2c3d4e5f60",
      "name": "Tom Becker",
      "email": "tom.becker@example.com",
      "panorama": "Retail"
    }
  ],
  "next_cursor": null
}
```

### get_learner

One learner's profile with the content on the Access tab and any waitlisted content. Access: read. REST: `GET /api/v1/thought-industries/learner`. MCP: `thought_industries_read → get_learner`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner` | string | yes | Learner email or learner_id from list_learners. |

Opens the learner profile and reads the Access tab: each piece of content with its type and status, and the Waitlisted Content container when the learner is on a waitlist. Waitlisted Content shows only for accounts allowed to provision learner access. Use it before enroll_learner to see what the learner already has.

Example response:

```json
{
  "learner_id": "3f9a2b18-7c4d-4e2a-9b1f-0c5d6e7f8a90",
  "name": "Priya Nair",
  "email": "priya.nair@example.com",
  "panorama": "Retail",
  "content": [
    {
      "content_id": "8f2a1c34-5b6d-4e7f-9a01-2b3c4d5e6f70",
      "title": "Onboarding 101",
      "type": "course",
      "status": "started"
    }
  ],
  "waitlisted": []
}
```

### list_courses

Content from Courses > All Courses with its content_id and type. Access: read. REST: `GET /api/v1/thought-industries/courses`. MCP: `thought_industries_read → list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of a content title. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads the Courses > All Courses list. Returns the content_id, title and content type (course, webinar, video and so on). Pass content_id to get_course, enroll_learner, import_learners and set_content_status. Use query for part of a title.

Example response:

```json
{
  "courses": [
    {
      "content_id": "8f2a1c34-5b6d-4e7f-9a01-2b3c4d5e6f70",
      "title": "Onboarding 101",
      "type": "course"
    },
    {
      "content_id": "4b1c2d3e-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
      "title": "Safety basics",
      "type": "course"
    }
  ],
  "next_cursor": null
}
```

### get_course

Enrollment limit and waitlist setting of one course. Access: read. REST: `GET /api/v1/thought-industries/contents/{content_id}/course`. MCP: `thought_industries_read → get_course`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `content_id` | string | yes | Course or other content ID from list_courses. |

Opens the content and reads its Enrollment step > Access tab: whether Limit Enrollments is on, the maximum number of enrollments and whether Enable Waitlisting is on. These settings belong to a session, so a webinar with several sessions returns one entry per session.

Example response:

```json
{
  "content_id": "4b1c2d3e-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
  "title": "Safety basics",
  "type": "course",
  "sessions": [
    {
      "name": "Default",
      "limit_enrollments": false,
      "max_enrollments": null,
      "waitlisting": false
    }
  ]
}
```

### list_content_actions

Enrollments, status changes, certificate grants and revoked access from the Content Actions Log. Access: read. REST: `GET /api/v1/thought-industries/content-actions`. MCP: `thought_industries_read → list_content_actions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | date | no | Only actions on or after this date. |
| `until` | date | no | Only actions on or before this date. |
| `type` | enum | no | enrollment, status_change, revoked_access or certificate_grant. |
| `source` | string | no | A source value such as course_completed, manager_course_enrollment or auto_enrollment. |
| `content` | string | no | Content title to filter by. |
| `learner` | string | no | Learner email to filter by. |
| `panorama` | string | no | Panorama (client) name to filter by. |
| `cursor` | string | no | Next page cursor from the previous call. |

Reads Reporting > Reports > Learner Actions > Content Actions Log with the same filters as the admin: date range, Panorama, content, learner, type and source. Each row has the learner email, Panorama, content type, content title, type, source and timestamp. type is enrollment, status_change, revoked_access or certificate_grant, and each source belongs to one type, for example course_completed under status_change. Use cursor to read every page.

Example response:

```json
{
  "actions": [
    {
      "email": "priya.nair@example.com",
      "panorama": "Retail",
      "content_type": "course",
      "content_title": "Safety basics",
      "type": "status_change",
      "source": "course_completed",
      "timestamp": "2026-10-13T14:02:00.000Z"
    },
    {
      "email": "sam.okafor@example.com",
      "panorama": "Field",
      "content_type": "course",
      "content_title": "Safety basics",
      "type": "status_change",
      "source": "course_completed",
      "timestamp": "2026-10-15T09:41:00.000Z"
    }
  ],
  "next_cursor": null
}
```

### list_auto_assignment_rules

Rules that enroll learners automatically, with conditions and unenroll setting. Access: read. REST: `GET /api/v1/thought-industries/auto-assignment-rules`. MCP: `thought_industries_read → list_auto_assignment_rules`.

No parameters.

Reads the Auto Assignment page. Each rule has its internal name, the courses or learning paths it assigns, its conditions, whether all or at least one must match, and whether it unenrolls learners who stop matching. The page exists only on instances where Auto Assignment is switched on, and holds at most 50 rules. Without it the call returns an error that says so.

Example response:

```json
{
  "rules": [
    {
      "name": "Developers to Cybersecurity Fundamentals",
      "assigns": [
        "Cybersecurity Fundamentals (learning path)"
      ],
      "conditions": [
        "User ref#1 is equal to Developer"
      ],
      "match": "all",
      "unenroll_when_unmet": true
    }
  ]
}
```

### enroll_learner

Add a course or other content to an existing learner's Access tab. Access: write, asks the user first. REST: `POST /api/v1/thought-industries/contents/{content_id}/learner/enroll`. MCP: `thought_industries_write → enroll_learner`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner` | string | yes | Learner email or learner_id from list_learners. |
| `content_id` | string | yes | Course or other content ID from list_courses. |

Opens the learner profile, goes to the Access tab and clicks Add Content for the content_id. The content then shows in the learner's access widget on their dashboard, and the Content Actions Log records an enrollment with the source manager_course_enrollment. Adding content the learner already has is refused. Check seats with get_course first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "learner_id": "3f9a2b18-7c4d-4e2a-9b1f-0c5d6e7f8a90",
  "content_id": "4b1c2d3e-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
  "title": "Safety basics",
  "status": "enrolled"
}
```

### import_learners

Create learners in bulk, give them content and optionally send invites. Access: write, asks the user first. REST: `POST /api/v1/thought-industries/learners`. MCP: `thought_industries_write → import_learners`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learners` | array | yes | Objects with first_name, last_name and email, up to 1,000. |
| `content_ids` | array | no | Content IDs from list_courses that every learner in the batch gets. |
| `send_invite` | boolean | no | Send an email invitation to new learners. Default: false. |
| `invite_message` | string | no | Message added to the invitation email. |

Runs Users > Learners > gear icon > Bulk Import Learners for you. Each learner needs first_name, last_name and email. All content_ids are given to every learner in the batch: courses, webinars, articles and single SCO content. One call takes up to 1,000 learners. The app queues the import, so enrollments show up a few minutes later in list_content_actions. A learner who already exists gets no invite, and content access can only be removed one learner at a time afterwards. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "status": "queued",
  "learners": 2,
  "content": [
    "Onboarding 101"
  ],
  "invites": "sent"
}
```

### set_content_status

Mark a learner as not-started, started, completed or not-completed on content. Access: write, asks the user first. REST: `PUT /api/v1/thought-industries/contents/{content_id}/status`. MCP: `thought_industries_write → set_content_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner` | string | yes | Learner email or learner_id from list_learners. |
| `content_id` | string | yes | Course or other content ID from list_courses. |
| `status` | enum | yes | not-started, started, completed or not-completed. |
| `completion_date` | date | no | Completion date, only when none is recorded yet. |

Updates an existing learner through the bulk import with a status column, using the name already on the profile. status is not-started, started, completed or not-completed. completion_date records a date for the content, and the app accepts it only when no completion date exists for that learner and content. The change shows in the Content Actions Log as a status change. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "learner": "tom.becker@example.com",
  "content": "Safety basics",
  "status": "completed",
  "completion_date": "2026-10-14T00:00:00.000Z"
}
```

### add_to_waitlist

Put a learner on the waitlist of content that has one. Access: write, asks the user first. REST: `POST /api/v1/thought-industries/contents/{content_id}/waitlists`. MCP: `thought_industries_write → add_to_waitlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner` | string | yes | Learner email or learner_id from list_learners. |
| `content_id` | string | yes | Course or other content ID from list_courses. |

Opens the learner profile, goes to the Access tab and adds the content under Waitlisted Content. Only content with an active waitlist can be added. The learner is enrolled only when someone buys the content or a manager provisions it, for example with enroll_learner. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "learner": "sam.okafor@example.com",
  "content": "June webinar",
  "waitlisted": true
}
```

### remove_from_waitlist

Take a learner off the waitlist of one piece of content. Access: write, asks the user first. REST: `DELETE /api/v1/thought-industries/contents/{content_id}/waitlists`. MCP: `thought_industries_write → remove_from_waitlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner` | string | yes | Learner email or learner_id from list_learners. |
| `content_id` | string | yes | Course or other content ID from list_courses. |

Opens the learner profile, goes to Waitlisted Content on the Access tab and clicks the trash icon next to the content, then confirms. add_to_waitlist puts the learner back, but at the end of the list. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "learner": "sam.okafor@example.com",
  "content": "June webinar",
  "waitlisted": false
}
```

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

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

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

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

```
Import this week's new hires from the list below into Thought Industries, enroll them in the Onboarding 101 course and send the invite with this message.
```

### Call Thought Industries 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/thought-industries 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 POST https://cotlet.dev/api/v1/thought-industries/contents/4b1c2d3e-6a7b-4c8d-9e0f-1a2b3c4d5e6f/learner/enroll \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"learner":"priya.nair@example.com"}'
```

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

```
{
  "learner_id": "3f9a2b18-7c4d-4e2a-9b1f-0c5d6e7f8a90",
  "content_id": "4b1c2d3e-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
  "title": "Safety basics",
  "status": "enrolled"
}
```

## Why use Cotlet for Thought Industries?

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

## Is it safe to connect Thought Industries to Cotlet?

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

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

## Is there a Thought Industries MCP server on GitHub?

No community MCP server for Thought Industries exists on GitHub. The usual way to automate it is Zapier: the Thought Industries Zapier app is private, you accept an invite link, connect with your host and an API key, and start Zaps from webhooks you add under Users > Notifications > Manager Notifications. Cotlet complements Zapier: it lets an agent or script ask for learners, enroll them and read the Content Actions Log on demand.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Accept the invite link, connect with your host and an API key, add a webhook per event in Manager Notifications | Sign up, sign in to Thought Industries once, add one MCP server or API key |
| What it does | Starts a Zap when a learner event fires, then acts in another app | Your agent or script asks, reads and acts on request: list, enroll, import, report |
| When Thought Industries changes | Zaps keep running while the webhook and API stay the same | Our team tests it daily and fixes it for you; failed calls are free |
| Your access | An API key from Settings > Security, stored in Zapier | Your own admin session in your Cloud Browser in the EU, profile encrypted, no API key needed, disabled for agents in one click |
| When access ends | The key works until you rotate or delete it | Your Cloud Browser keeps you signed in; if Thought Industries logs you out, your agent gets a link to sign in again |
| Upkeep | You keep the key, the webhooks and each Zap | Nothing to host or update |
| Where it runs and price | In Zapier, on your Zapier plan | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule. 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 Thought Industries 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 Thought Industries API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Thought Industries 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 10 credits (about $0.04 to $0.06), 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 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $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 Thought Industries 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 Thought Industries 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 Thought Industries only after you enable it. When Thought Industries 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 Thought Industries, sign out of Thought Industries 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.
- **Thought Industries's terms:** You use your own Thought Industries account and stay responsible for following Thought Industries's terms. Cotlet is independent and not affiliated with Thought Industries. [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 Thought Industries in the console and press Request access. Then you create your API key and connect Thought Industries there.

**Do I need to be technical?**

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

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

Thought Industries 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 API access on my Thought Industries instance?**

No. Cotlet works in your own admin session in the Cloud Browser and creates no API key. The official REST API, the Zapier app and the Claude plugin all need a key from Settings > Security, and the plugin docs list an instance with API access enabled as a prerequisite. What your agent can do still follows your admin role (Thought Industries developer docs, checked 23 Oct 2026).

**How does this differ from the Thought Industries Claude plugin?**

The plugin runs in the Claude desktop app on the REST API and is in beta. It browses the catalog and writes course content as drafts, and publishing stays manual. Cotlet covers learners: access, enrollments, imports, waitlists and the Content Actions Log, and it works from Claude Code, n8n or a script (Thought Industries developer docs, checked 23 Oct 2026).

**What can it not do yet?**

The tools read learners, courses, the Content Actions Log and Auto Assignment rules, and write enrollments, imports, content status and waitlists. They do not author or publish courses, remove a learner's access, change Auto Assignment rules, touch ecommerce, or edit Panorama and sublicense settings. Learning paths, subscriptions and Panorama access can only be set for new learners in an import, which is how Thought Industries bulk import works (Thought Industries Help, checked 23 Oct 2026).

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

No. Every call to enroll_learner, import_learners, set_content_status, add_to_waitlist or remove_from_waitlist waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Thought Industries 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/thought-industries 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.