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

# WorkRamp API and MCP server

> WorkRamp has a REST API, but it is private: you ask support@workramp.com for access, it needs an enterprise account, and tokens come only from Admin users (checked 22 Oct 2026). WorkRamp's own MCP server is announced in its June 2026 product roundup and described as read and search of guides and assignments, with no write tools.

Learning platform for employee training: guides, paths and challenges assigned to learners and groups, with due dates, reminders, events and automations run from an Admin Console.

## What is the WorkRamp API?

Cotlet's WorkRamp API exposes 13 endpoints for your own WorkRamp account: list trainings, list learners, list groups, list assignments, get learner transcript, get reminder settings, list automations, assign training, remind learners, change due date, unassign learner, set reminder cadence and run automation. The list_trainings endpoint returns list guides, paths, challenges and SCORM courses in your WorkRamp. Each endpoint takes simple JSON inputs like training_id, cursor or learner_ids and works both as an operation of the workramp_read or workramp_write MCP tool for agents and as a REST call for scripts.

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

WorkRamp has a REST API, but it is private: you ask support@workramp.com for access, it needs an enterprise account, and tokens come only from Admin users (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for WorkRamp with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does WorkRamp have an official API?

WorkRamp has a REST API, but it is private: you ask support@workramp.com for access, it needs an enterprise account, and tokens come only from Admin users (checked 22 Oct 2026). WorkRamp's own MCP server is announced in its June 2026 product roundup and described as read and search of guides and assignments, with no write tools.

| Task | WorkRamp official | Cotlet |
|---|---|---|
| List trainings and their assignments | Partly: Private API: guides, paths and assignments in a date range | Yes |
| Assign a training and change its due date | Partly: Private API: create and update assignment | Yes |
| Unassign a learner | Partly: Private API: delete assignment | Yes |
| Read a learner's assignment history | Partly: Private API lists assignments; the transcript is an export in My Team | Yes |
| Send a manual reminder to learners | No | Yes |
| Read or change reminder cadence in Settings > Emails | No | Yes |
| List automations and run one now | No | Yes |

Sources: [WorkRamp Help: June 2026 Product Roundup](https://help.workramp.com/en/articles/15190747-june-2026-product-roundup), [WorkRamp Help: Academies API](https://help.workramp.com/en/articles/6993413-academies-api), [WorkRamp developers: Getting started](https://developers.workramp.com/reference/getting-started), [WorkRamp developers: API reference index](https://developers.workramp.com/llms.txt)

## For AI agents

```text
WorkRamp has a REST API, but it is private: you ask support@workramp.com for access, it needs an enterprise account, and tokens come only from Admin users (checked 22 Oct 2026). WorkRamp's own MCP server is announced in its June 2026 product roundup and described as read and search of guides and assignments, with no write tools.
Cotlet provides a hosted MCP server and REST API for WorkRamp: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=workramp, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    workramp_read, workramp_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/workramp, each operation at its own route, e.g. POST /api/v1/workramp/trainings/{training_id}/learners/remind
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_trainings, list_learners, list_groups, list_assignments, get_learner_transcript, get_reminder_settings, list_automations, assign_training, remind_learners, change_due_date, unassign_learner, set_reminder_cadence, run_automation
Confirm      assign_training, remind_learners, unassign_learner, set_reminder_cadence, run_automation (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/workramp-api-mcp-server.md

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

## What can an AI agent do in WorkRamp?

Cotlet is best for L&D and compliance admins who want their AI agent to chase overdue learners, move due dates and report completion without running or fixing a server.

- **[Remind overdue learners](https://cotlet.dev/integrations/workramp-api-mcp-server/remind-overdue-learners.md)** (runs: daily): "Find everyone overdue on Security Awareness 2026 in the Sales group, send them a reminder asking to finish by Friday, and notify their managers." → `list_trainings`, `list_assignments`, `remind_learners`
- **[Extend due dates for a group](https://cotlet.dev/integrations/workramp-api-mcp-server/extend-due-dates.md)**: "Move the due date of Security Awareness 2026 to 30 November for everyone in the Support group who has not finished it." → `list_trainings`, `list_assignments`, `change_due_date`
- **[Weekly training completion report](https://cotlet.dev/integrations/workramp-api-mcp-server/weekly-completion-report.md)** (runs: weekly): "Every Monday, list each group's open and overdue assignments on Security Awareness 2026 and name the three most overdue learners." → `list_trainings`, `list_assignments`, `list_groups`
- **Assign training to new hires** (runs: weekly): "Assign the Onboarding path to everyone who joined this week, due in 14 days, and skip anyone who already has it." → `list_learners`, `list_trainings`, `assign_training`
- **Tune reminder cadence before a deadline**: "Show the reminder cadence in Settings > Emails and set 4 due date reminders for the audit training in the last two weeks." → `get_reminder_settings`, `set_reminder_cadence`

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

Yes. Cotlet does not replace your automation platform: it gives it a WorkRamp 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 remind overdue 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/workramp/trainings. | 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/workramp/trainings with your API key. | cron or GitHub Actions. |

## Tools

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

### list_trainings

List guides, paths, challenges and SCORM courses in your WorkRamp. Access: read. REST: `GET /api/v1/workramp/trainings`. MCP: `workramp_read → list_trainings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | no | Content type: guide, path, challenge or scorm. Omit for all. |
| `query` | string | no | Part of the title. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the title, type and ID of each training, 30 to a page, with next_cursor while more remain. The training_id is what the assignment tools take. Any admin account can read the list.

Example response:

```json
{
  "trainings": [
    {
      "training_id": "trn_7a21c4",
      "title": "Security Awareness 2026",
      "type": "guide",
      "has_pass_mark": true
    },
    {
      "training_id": "trn_92be10",
      "title": "Onboarding",
      "type": "path",
      "has_pass_mark": false
    }
  ],
  "next_cursor": null
}
```

### list_learners

List learners with their groups and the date they were added. Access: read. REST: `GET /api/v1/workramp/learners`. MCP: `workramp_read → list_learners`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | no | Group name. |
| `joined_since` | string | no | ISO date; only learners added on or after it. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the name, email, groups and manager of each learner, 30 to a page. The learner_id feeds the assignment tools. The filters work within each page, so follow next_cursor until the dates fall outside your window.

Example response:

```json
{
  "learners": [
    {
      "learner_id": "usr_31f0a2",
      "name": "Tom Becker",
      "email": "tom@example.com",
      "groups": [
        "Sales"
      ],
      "manager": "Maya Chen",
      "added_at": "2026-10-19"
    }
  ],
  "next_cursor": null
}
```

### list_groups

List the learner groups of your WorkRamp. Access: read. REST: `GET /api/v1/workramp/groups`. MCP: `workramp_read → list_groups`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each group name with its member count. Group names are what the group filter of list_learners and list_assignments takes.

Example response:

```json
{
  "groups": [
    {
      "name": "Sales",
      "members": 12
    },
    {
      "name": "Support",
      "members": 20
    }
  ],
  "next_cursor": null
}
```

### list_assignments

List the assignments of one training with learner, status and due date. Access: read. REST: `GET /api/v1/workramp/trainings/{training_id}/assignments`. MCP: `workramp_read → list_assignments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | yes | Training ID from list_trainings. |
| `status` | string | no | Status as the Status filter of the assignments table shows it. |
| `group` | string | no | Group name. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns one row per learner, as the assignments table on the training shows it: status, due date and the date assigned. 30 to a page, with next_cursor while more remain. The status and group filters work like the table filters. Learners who were unassigned do not appear.

Example response:

```json
{
  "training": "Security Awareness 2026",
  "assignments": [
    {
      "learner_id": "usr_31f0a2",
      "name": "Tom Becker",
      "group": "Sales",
      "status": "Overdue",
      "due_date": "2026-10-13"
    },
    {
      "learner_id": "usr_8b44e9",
      "name": "Jake Ortiz",
      "group": "Sales",
      "status": "Overdue",
      "due_date": "2026-10-20"
    },
    {
      "learner_id": "usr_5c07d1",
      "name": "Anna Lopez",
      "group": "Sales",
      "status": "Completed",
      "due_date": "2026-10-25"
    }
  ],
  "next_cursor": null
}
```

### get_learner_transcript

Read one learner's assignment history, as the transcript in My Team shows it. Access: read. REST: `GET /api/v1/workramp/learners/{learner_id}/transcript`. MCP: `workramp_read → get_learner_transcript`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `learner_id` | string | yes | Learner ID from list_learners. |

Returns the performance summary and the assignment history of the learner: training, status and due date. It reads only; the CSV export is the same data. The account needs to see that learner, as an admin or as their manager.

Example response:

```json
{
  "learner": "Tom Becker",
  "summary": {
    "assigned": 3,
    "completed": 2
  },
  "history": [
    {
      "training": "Security Awareness 2026",
      "status": "Overdue",
      "due_date": "2026-10-13"
    },
    {
      "training": "Onboarding",
      "status": "Completed",
      "due_date": "2026-09-30"
    }
  ]
}
```

### get_reminder_settings

Read the due date and overdue reminder cadence from Settings > Emails. Access: read. REST: `GET /api/v1/workramp/reminder-settings`. MCP: `workramp_read → get_reminder_settings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | no | Training ID to read its own override; omit for the account settings. |

Returns the days of each due date reminder and each overdue reminder. WorkRamp allows up to 4 of each. With training_id it returns the override on that content when one is set, otherwise the account settings.

Example response:

```json
{
  "scope": "account",
  "due_date_reminders_days_before": [
    7,
    3,
    1
  ],
  "overdue_reminders_days_after": [
    1,
    7
  ],
  "send_to_manager": false
}
```

### list_automations

List automations from Settings > Automations with trigger, status and enrolled users. Access: read. REST: `GET /api/v1/workramp/automations`. MCP: `workramp_read → list_automations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the name, trigger, state and number of enrolled users of each automation. Paused automations do not advance users. Automations run about every 20 to 30 minutes, so a new match can take that long to show.

Example response:

```json
{
  "automations": [
    {
      "automation_id": "aut_41d9",
      "name": "New hire onboarding",
      "trigger": "New user created",
      "state": "Active",
      "enrolled": 7
    }
  ],
  "next_cursor": null
}
```

### assign_training

Assign a guide, path, challenge or SCORM course to learners or a group. Access: write, asks the user first. REST: `POST /api/v1/workramp/trainings/{training_id}/assign`. MCP: `workramp_write → assign_training`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | yes | Training ID from list_trainings. |
| `learner_ids` | string[] | no | Learner IDs. Give this or group. |
| `group` | string | no | Group name. Give this or learner_ids. |
| `due_date` | string | no | ISO date. Optional for guides, SCORM courses and paths. |
| `assign_at` | string | no | ISO date and time to schedule the assignment; omit to assign now. |

Assigns the training the way the Assign button does and returns the assignment count. Learners already assigned are skipped. A scheduled assignment shows under Scheduled Assignments in the 3-dot menu. Learners are notified when they get their first piece of content. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "training": "Onboarding",
  "assigned": 2,
  "skipped": 0,
  "due_date": "2026-11-05",
  "scheduled_for": null
}
```

### remind_learners

Send a manual reminder about a training to chosen learners. Access: write, asks the user first. REST: `POST /api/v1/workramp/trainings/{training_id}/learners/remind`. MCP: `workramp_write → remind_learners`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | yes | Training ID from list_trainings. |
| `learner_ids` | string[] | yes | Learner IDs from list_learners or list_assignments. |
| `message` | string | no | Optional message added to the reminder. |
| `notify_managers` | boolean | no | Also send a Manager Escalation email to their managers. |

Does what Actions > Remind does: WorkRamp emails learners who have not completed or passed the assignment. Learners who finished are skipped and listed. The email cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "training": "Security Awareness 2026",
  "reminded": 2,
  "skipped": [],
  "managers_notified": true
}
```

### change_due_date

Set a new due date on the assignments of chosen learners. Access: write. REST: `PATCH /api/v1/workramp/trainings/{training_id}/due-date`. MCP: `workramp_write → change_due_date`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | yes | Training ID from list_trainings. |
| `learner_ids` | string[] | yes | Learner IDs from list_learners or list_assignments. |
| `due_date` | string | yes | New due date as an ISO date. |

Edits the due date of each learner row, as the drop-down arrow in the assignments table does, and returns the old and new dates. It reaches nobody directly and one more call restores the old date, so it does not wait for your OK. WorkRamp sends its reminders from the new date.

Example response:

```json
{
  "training": "Security Awareness 2026",
  "changed": [
    {
      "learner_id": "usr_31f0a2",
      "from": "2026-10-13",
      "to": "2026-11-30"
    },
    {
      "learner_id": "usr_8b44e9",
      "from": "2026-10-20",
      "to": "2026-11-30"
    }
  ]
}
```

### unassign_learner

Remove a training assignment from learners. Access: write, asks the user first. REST: `POST /api/v1/workramp/trainings/{training_id}/learner/unassign`. MCP: `workramp_write → unassign_learner`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | yes | Training ID from list_trainings. |
| `learner_ids` | string[] | yes | Learner IDs from list_learners or list_assignments. |

Does what Unassign in the row menu does. WorkRamp deletes the record on the backend and it is gone from reporting. A guide, challenge or SCORM course inside a path cannot be unassigned alone; unassign the path. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "training": "Onboarding",
  "unassigned": 1
}
```

### set_reminder_cadence

Change the due date and overdue reminder cadence for the account or one training. Access: write, asks the user first. REST: `PUT /api/v1/workramp/reminder-cadence`. MCP: `workramp_write → set_reminder_cadence`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `training_id` | string | no | Set the override for this training; omit for the account settings. |
| `due_date_reminders_days_before` | integer[] | no | Up to 4 days before the due date. |
| `overdue_reminders_days_after` | integer[] | no | Up to 4 days after the due date. |

Writes the cadence of Settings > Emails, or the Notifications override on one content page. An account change applies to every assignment with a due date, so many learners get emails on the new schedule. WorkRamp sends them around 2pm UTC. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "scope": "training",
  "training": "Security Awareness 2026",
  "due_date_reminders_days_before": [
    14,
    7,
    3,
    1
  ],
  "overdue_reminders_days_after": [
    1,
    7
  ]
}
```

### run_automation

Run an automation now for the users who already match it. Access: write, asks the user first. REST: `POST /api/v1/workramp/automations/{automation_id}/run`. MCP: `workramp_write → run_automation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `automation_id` | string | yes | Automation ID from list_automations. |

Does what Run Now in the action menu does. It can enroll many users at once, so check the filters in list_automations first. An automation with New Matches only covers users who qualify after it was activated; Run Now includes past matches. A run that is already going is blocked. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "automation_id": "aut_41d9",
  "name": "New hire onboarding",
  "started": true
}
```

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

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

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

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

```
Find everyone overdue on Security Awareness 2026 in the Sales group, send them a reminder asking to finish by Friday, and notify their managers.
```

### Call WorkRamp 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/workramp 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/workramp/trainings/trn_7a21c4/learners/remind \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"learner_ids":["usr_31f0a2","usr_8b44e9"],"message":"Please finish Security Awareness 2026 by Friday.","notify_managers":true}'
```

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

```
{
  "training": "Security Awareness 2026",
  "reminded": 2,
  "skipped": [],
  "managers_notified": true
}
```

## Why use Cotlet for WorkRamp?

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

## Is it safe to connect WorkRamp to Cotlet?

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

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

## Is there a WorkRamp MCP server on GitHub?

Yes. A community WorkRamp MCP server exists on GitHub, maintained by one person. You install it yourself, give it an API token, and fix it when it breaks. It talks to the private REST API, so it needs API access from WorkRamp first. Cotlet works in your own WorkRamp account instead and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask WorkRamp for API access, clone the repo, install it, paste an Admin token, add it to each MCP client | Sign up, sign in to WorkRamp once, add one MCP server or API key |
| When WorkRamp 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 WorkRamp access | An API token in a file on your computer, with full Admin access | Your own Cloud Browser session in the EU, encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Calls fail if the token owner stops being an active Admin | Your Cloud Browser keeps you signed in; if WorkRamp 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 WorkRamp 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 WorkRamp API cost?

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

**Do I need to be technical?**

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

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

WorkRamp 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).

**Which WorkRamp role does my agent need?**

Your role decides, because Cotlet works in your own account. Settings > Automations is managed by Admins, and WorkRamp API tokens are generated only for Admin users. A manager in My Team can remind only their direct reports, so use an Admin account for group-wide jobs.

**Does it cover WorkRamp Academies?**

The tools cover the Admin Console for employee learning: guides, paths, groups and Settings. Academies for external learners are a separate product with their own automations and are not covered.

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

No. Every call to assign_training, remind_learners, unassign_learner, set_reminder_cadence or run_automation waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. change_due_date runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the WorkRamp 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/workramp 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.