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

# LearnUpon API and MCP server

> LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 Oct 2026). The REST API uses API keys that an admin generates under Settings > Integrations > API Keys, and Support grants them when the option is missing. The official MCP server gives AI tools access to reporting data; its page lists no tools and no write actions.

Learning management system for companies, training providers and associations: courses, learning paths, groups, enrollments and reports in one portal.

## What is the LearnUpon API?

Cotlet's LearnUpon API exposes 14 endpoints for your own LearnUpon account: list users, get user, list groups, list group users, list courses, list enrollments, invite users, create group, add users to group, enroll users, enroll group, unenroll users, set enrollment complete and disable user. The list_users endpoint returns users of the portal with name, email, user type and status; search by name or email, filter by group. Each endpoint takes simple JSON inputs like group_id, query or status and works both as an operation of the learnupon_read or learnupon_write MCP tool for agents and as a REST call for scripts.

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

LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for LearnUpon with 14 endpoints (6 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does LearnUpon have an official API?

LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 Oct 2026). The REST API uses API keys that an admin generates under Settings > Integrations > API Keys, and Support grants them when the option is missing. The official MCP server gives AI tools access to reporting data; its page lists no tools and no write actions.

| Task | LearnUpon official | Cotlet |
|---|---|---|
| Read users, groups, courses and enrollments | Partly: REST API with API keys; the official MCP server covers reporting data | Yes |
| Invite users to the portal or a group | Partly: REST API (POST /portal_invite); no official MCP tool | Yes |
| Add users to a group | Partly: REST API group memberships; no official MCP tool | Yes |
| Enroll learners and groups on courses | Partly: REST API (POST /enrollments); no official MCP tool | Yes |
| Unenroll learners | Partly: REST API (DELETE /enrollments/{id}); no official MCP tool | Yes |
| Mark an enrollment complete | Partly: REST API MarkCompletes; no official MCP tool | Yes |
| Disable a user account | Partly: REST API (PUT /users/{id}); no official MCP tool | Yes |
| Work without API keys | No | Yes |

Sources: [LearnUpon API guide](https://docs.learnupon.com/api/), [LearnUpon: Connect LearnUpon to your AI workspace (MCP)](https://www.learnupon.com/platform/learnupon-mcp/), [LearnUpon Help: Enroll groups on a course](https://support.learnupon.com/hc/en-us/articles/360017454617-Enroll-groups-on-a-course), [LearnUpon Help: Upload users by batch CSV file](https://support.learnupon.com/hc/en-us/articles/360002659997-Upload-users-by-batch-CSV-file)

## For AI agents

```text
LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 Oct 2026). The REST API uses API keys that an admin generates under Settings > Integrations > API Keys, and Support grants them when the option is missing. The official MCP server gives AI tools access to reporting data; its page lists no tools and no write actions.
Cotlet provides a hosted MCP server and REST API for LearnUpon: 14 tools (6 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=learnupon, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    learnupon_read, learnupon_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/learnupon, each operation at its own route, e.g. POST /api/v1/learnupon/users/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_users, get_user, list_groups, list_group_users, list_courses, list_enrollments, invite_users, create_group, add_users_to_group, enroll_users, enroll_group, unenroll_users, set_enrollment_complete, disable_user
Confirm      invite_users, add_users_to_group, enroll_users, enroll_group, unenroll_users, set_enrollment_complete, disable_user (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/learnupon-api-mcp-server.md

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

## What can an AI agent do in LearnUpon?

Cotlet is best for LearnUpon admins and L&D teams who want their AI agent to invite learners, enroll groups and clean up leavers without running or fixing a server.

- **[Invite and enroll new learners](https://cotlet.dev/integrations/learnupon-api-mcp-server/invite-and-enroll-new-learners.md)** (runs: weekly): "Invite these 12 new hires to LearnUpon as learners in the Onboarding group, and enroll anyone who is not covered by the group on Data privacy basics." → `list_users`, `invite_users`, `list_courses`, `enroll_users`
- **[Re-enroll a group for recertification](https://cotlet.dev/integrations/learnupon-api-mcp-server/reenroll-group-for-recertification.md)** (runs: weekly): "It is January: re-enroll the Warehouse group on Forklift safety, including people who already completed it, and tell me who is affected." → `list_groups`, `list_courses`, `list_enrollments`, `enroll_group`
- **[Offboard leavers from training](https://cotlet.dev/integrations/learnupon-api-mcp-server/offboard-leavers-from-training.md)** (runs: weekly): "These 3 people left the company. Unenroll them from unfinished courses and disable their LearnUpon accounts. Do not delete anything." → `list_users`, `get_user`, `unenroll_users`, `disable_user`
- **Mark course completions from attendance** (runs: weekly): "Here are the attendees of Tuesday's workshop. Set their Workshop attendance enrollment to Completed with today's date and a note." → `list_enrollments`, `set_enrollment_complete`
- **Set up a group for a new cohort**: "Create a group called Autumn 2026 cohort, add these learners to it and enroll the group on Welcome and Tools basics." → `create_group`, `add_users_to_group`, `enroll_group`

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

Yes. Cotlet does not replace your automation platform: it gives it a LearnUpon 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 invite and enroll new learners, 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/learnupon/users. | 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/learnupon/users with your API key. | cron or GitHub Actions. |

## Tools

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

### list_users

Users of the portal with name, email, user type and status; search by name or email, filter by group. Access: read. REST: `GET /api/v1/learnupon/users`. MCP: `learnupon_read → list_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name or email address to search for. |
| `group_id` | string | no | Only users in this group. |
| `status` | enum | no | pending or deletion_pending. Leave out for active users. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns users of the portal you are signed in to, a page at a time; pass next_cursor back as cursor for the next page. query matches a name or an email address. status pending returns invited people who have not accepted yet, and deletion_pending returns accounts in the 30 days after deletion; leave it out for active users. user_id is the id the other tools take.

Example response:

```json
{
  "users": [
    {
      "user_id": "51872",
      "name": "Maria Nowak",
      "email": "maria.nowak@example.com",
      "user_type": "learner",
      "login_enabled": true
    },
    {
      "user_id": "51890",
      "name": "Tom Reyes",
      "email": "tom.reyes@example.com",
      "user_type": "learner",
      "login_enabled": true
    }
  ],
  "next_cursor": null
}
```

### get_user

One user with groups, enrollments, user type and whether login is enabled. Access: read. REST: `GET /api/v1/learnupon/users/{user_id}`. MCP: `learnupon_read → get_user`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_id` | string | yes | User id from list_users. |

Returns the profile of one user: name, email, user type, Login enabled, expiry date, the groups the user belongs to and every enrollment with its status. Use it before unenrolling or disabling someone, to see what will change. A pending user has no enrollments until they accept, unless you enrolled them by email.

Example response:

```json
{
  "user_id": "51872",
  "name": "Maria Nowak",
  "email": "maria.nowak@example.com",
  "user_type": "learner",
  "login_enabled": true,
  "expires": null,
  "groups": [
    {
      "group_id": "4821",
      "name": "Onboarding"
    }
  ],
  "enrollments": [
    {
      "enrollment_id": "90417",
      "course": "Data privacy basics",
      "status": "In Progress"
    },
    {
      "enrollment_id": "90102",
      "course": "Welcome and Tools basics",
      "status": "Completed"
    }
  ]
}
```

### list_groups

Groups of the portal with name, description and number of users. Access: read. REST: `GET /api/v1/learnupon/groups`. MCP: `learnupon_read → list_groups`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the group name. |

Returns the groups you can see: admins see all of them, a manager sees only the groups assigned to them. Use group_id as the group parameter of the other tools. users is the count LearnUpon shows on the group page.

Example response:

```json
{
  "groups": [
    {
      "group_id": "4821",
      "name": "Onboarding",
      "description": "New hires, first 90 days",
      "users": 10
    },
    {
      "group_id": "4830",
      "name": "Warehouse",
      "description": "Warehouse team",
      "users": 48
    }
  ]
}
```

### list_group_users

Users in one group, with their user type and whether they accepted the invite. Access: read. REST: `GET /api/v1/learnupon/group-users`. MCP: `learnupon_read → list_group_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Group id from list_groups. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the users of one group, a page at a time; pass next_cursor back as cursor. Pending invitees appear with pending true until they accept. A manager sees a group only if an admin assigned it to them.

Example response:

```json
{
  "users": [
    {
      "user_id": "51872",
      "name": "Maria Nowak",
      "user_type": "learner",
      "pending": false
    },
    {
      "user_id": "51890",
      "name": "Tom Reyes",
      "user_type": "learner",
      "pending": true
    }
  ],
  "next_cursor": null
}
```

### list_courses

Courses of the portal with name and published or draft status. Access: read. REST: `GET /api/v1/learnupon/courses`. MCP: `learnupon_read → list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the course name. |

Returns the courses in the portal with their status. Only published courses can take enrollments: LearnUpon does not enroll anyone, individual or group, on a draft. Use course_id in the enrollment tools.

Example response:

```json
{
  "courses": [
    {
      "course_id": "10233",
      "name": "Forklift safety",
      "status": "published"
    },
    {
      "course_id": "10240",
      "name": "Data privacy basics",
      "status": "published"
    },
    {
      "course_id": "10251",
      "name": "Workshop attendance",
      "status": "draft"
    }
  ]
}
```

### list_enrollments

Enrollments on one course with learner, group and completion status; filter by group, status and creation date. Access: read. REST: `GET /api/v1/learnupon/courses/{course_id}/enrollments`. MCP: `learnupon_read → list_enrollments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course id from list_courses. |
| `group_id` | string | no | Only learners in this group. |
| `status` | enum | no | not_started or in_progress. Leave out for all. |
| `created_after` | date | no | Only enrollments created on or after this date. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the enrollments of one course as the course Enrollments page shows them, a page at a time; pass next_cursor back as cursor. status filters Not Started or In Progress. group_id keeps one group. created_after keeps enrollments made on or after a date. Each row has the enrollment_id that set_enrollment_complete takes.

Example response:

```json
{
  "enrollments": [
    {
      "enrollment_id": "90417",
      "user_id": "51872",
      "name": "Maria Nowak",
      "group": "Onboarding",
      "status": "In Progress"
    },
    {
      "enrollment_id": "90433",
      "user_id": "51890",
      "name": "Tom Reyes",
      "group": "Onboarding",
      "status": "Not Started"
    }
  ],
  "next_cursor": null
}
```

### invite_users

Invite people by email as learner, instructor or manager, optionally into a group. Access: write, asks the user first. REST: `POST /api/v1/learnupon/users/invite`. MCP: `learnupon_write → invite_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `emails` | array | yes | Email addresses to invite. |
| `user_type` | enum | no | learner, instructor or manager. Default: learner. |
| `group_id` | string | no | Group the invitees join on accepting. |
| `expires` | date | no | Date when access runs out. |

Sends an invite to each address, with the default user type learner. With group_id, the invitees join that group when they accept, and courses assigned to the group enroll them then. Invitees stay pending until they accept. A manager can be invited but cannot get a group before accepting. Admin invites are not made by this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invited": 2,
  "group_id": "4821",
  "status": "pending",
  "emails": [
    "maria.nowak@example.com",
    "tom.reyes@example.com"
  ]
}
```

### create_group

Create an empty group with a name and description. Access: write. REST: `POST /api/v1/learnupon/groups`. MCP: `learnupon_write → create_group`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Group name. |
| `description` | string | no | Group description. |

Creates one group and returns its group_id. It reaches no one and changes no account; an admin can delete an empty group in LearnUpon, which does not delete any accounts, so this call does not wait for your OK. Only admins can create groups.

Example response:

```json
{
  "group_id": "4902",
  "name": "Autumn 2026 cohort",
  "users": 0
}
```

### add_users_to_group

Add existing or new users to a group by email. Access: write, asks the user first. REST: `POST /api/v1/learnupon/groups/{group_id}/users-to-groups`. MCP: `learnupon_write → add_users_to_group`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Group id from list_groups. |
| `emails` | array | yes | Email addresses to add. |
| `process_enrollments` | boolean | no | Enroll on courses assigned to the group. Default: true. |

Adds the users to one group. An email without an account in the portal gets an invite and stays pending until it is accepted. With process_enrollments true, users are enrolled on courses assigned to the group. Removing a user from a group by hand does not unenroll them. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "group_id": "4902",
  "added": 2,
  "invited": 1
}
```

### enroll_users

Enroll learners on published courses by email, pending learners included. Access: write, asks the user first. REST: `POST /api/v1/learnupon/users/enroll`. MCP: `learnupon_write → enroll_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `emails` | array | yes | Learner email addresses. |
| `course_ids` | array | yes | Course ids from list_courses. |
| `re_enroll_completed` | boolean | no | Enroll again on courses already completed. Default: false. |

Enrolls each email address on each course. A pending learner can be enrolled, so the course is ready when they accept. Draft courses fail and are listed in the result. re_enroll_completed adds learners to a course they already finished. LearnUpon notifies learners on enrollment. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "enrolled": 2,
  "course_ids": [
    "10240"
  ],
  "failed": []
}
```

### enroll_group

Enroll all users of a group on published courses, completed learners included on request. Access: write, asks the user first. REST: `POST /api/v1/learnupon/groups/{group_id}/enroll`. MCP: `learnupon_write → enroll_group`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group_id` | string | yes | Group id from list_groups. |
| `course_ids` | array | yes | Course ids from list_courses. |
| `re_enroll_completed` | boolean | no | Enroll again on courses already completed. Default: false. |

Enrolls the group on each course. Group enrollments can take longer than individual ones, so the call returns processing and list_enrollments shows the progress. re_enroll_completed true adds learners who already finished. Users with a disabled account are caught up when their account is enabled again. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "group_id": "4821",
  "course_ids": [
    "10233"
  ],
  "re_enroll_completed": true,
  "status": "processing"
}
```

### unenroll_users

Remove learners from one course. Access: write, asks the user first. REST: `POST /api/v1/learnupon/courses/{course_id}/users/unenroll`. MCP: `learnupon_write → unenroll_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course id from list_courses. |
| `user_ids` | array | yes | User ids from list_users. |

Unenrolls the users from one course, which removes their access to it. A manager needs the permission to unenroll users, which is off by default. Completed courses stay in the training record when you only unenroll from open ones. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "course_id": "10233",
  "unenrolled": 2
}
```

### set_enrollment_complete

Set an enrollment to Completed, Passed or Failed with a date and a note. Access: write, asks the user first. REST: `PUT /api/v1/learnupon/enrollments/{enrollment_id}/complete`. MCP: `learnupon_write → set_enrollment_complete`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enrollment_id` | string | yes | Enrollment id from list_enrollments. |
| `status` | enum | yes | completed, passed or failed. |
| `score` | number | no | Score, for status passed. |
| `date` | date | no | Completion date. Default: today. |
| `notes` | string | no | Note saved with the completion. |
| `award_badges` | boolean | no | Award associated badges. Default: false. |

Marks one enrollment as finished, as the Manual Enrollment Completion dialog does. status is completed, passed or failed; passed takes a score. award_badges turns on Award associated badges. A manager needs the permission to mark learners complete. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "enrollment_id": "90433",
  "status": "completed",
  "date": "2026-10-20",
  "notes": "Attended the Tuesday workshop"
}
```

### disable_user

Turn off Login enabled for a user; data and enrollments stay. Access: write, asks the user first. REST: `POST /api/v1/learnupon/users/{user_id}/disable`. MCP: `learnupon_write → disable_user`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `user_id` | string | yes | User id from list_users. |

Sets Login enabled to off. The user cannot sign in, and the account keeps its data, enrollments and training history until an admin turns it on or deletes it. While disabled, the user is not enrolled on group courses. Managers can disable only users in their own groups. This tool never deletes an account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "user_id": "51872",
  "login_enabled": false
}
```

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

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

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

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

```
Invite these 12 new hires to LearnUpon as learners in the Onboarding group, and enroll anyone who is not covered by the group on Data privacy basics.
```

### Call LearnUpon 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/learnupon 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/learnupon/users/enroll \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails":["maria.nowak@example.com","tom.reyes@example.com"],"course_ids":["10240"]}'
```

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

```
{
  "enrolled": 2,
  "course_ids": [
    "10240"
  ],
  "failed": []
}
```

## Why use Cotlet for LearnUpon?

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

## Is it safe to connect LearnUpon to Cotlet?

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

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

## Is there a LearnUpon MCP server on GitHub?

Yes. Community LearnUpon MCP servers exist on GitHub, usually maintained by one person. They run on the REST API, so you generate API keys, install the server and fix it yourself when it breaks. Cotlet hosts the same kind of server for you and keeps it working. It signs in as you in your own Cloud Browser, so no API keys are needed.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Get API keys from LearnUpon, clone the repo, install it, add it to each MCP client | Sign up, sign in to LearnUpon once, add one MCP server or API key |
| When LearnUpon 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 LearnUpon access | API keys in a file on your computer, readable by any program you run | Your own Cloud Browser session in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Calls fail until you replace the keys | Your Cloud Browser keeps you signed in; if LearnUpon 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 LearnUpon 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 LearnUpon API cost?

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

**Do I need to be technical?**

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

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

LearnUpon 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 keys or a higher LearnUpon plan?**

No. Cotlet works in your own LearnUpon account and does not use API keys. LearnUpon gives API keys under Settings > Integrations > API Keys and asks you to contact Support if the option is missing. Your role still counts: admins can enroll groups on published courses, and a manager needs the permission Can enroll learners on courses.

**Can it delete users?**

No. disable_user turns Login enabled off and keeps enrollments and training history. LearnUpon deletes an account in stages: it stays 30 days, then personal data is removed and Support cannot restore it. That step stays in LearnUpon under Users > Delete User.

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

No. Every call to invite_users, add_users_to_group, enroll_users, enroll_group, unenroll_users, set_enrollment_complete or disable_user waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_group runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the LearnUpon 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/learnupon 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.