# Teachable API and MCP server

> Teachable has a public API, but only on the Growth plan and up, and it reads courses and lecture content and manages users, enrollments, pricing plans and transactions (checked 11 Oct 2026). Lesson editing, coupons, emails to students and comments are not in it.

Platform for creating and selling online courses, coaching and digital downloads from your own school.

## What is the Teachable API?

Cotlet's Teachable API exposes 15 endpoints for your own Teachable account: list courses, get curriculum, get lesson, list students, list comments, list coupons, create lesson, update lesson, publish lesson, create coupon, archive coupon, enroll student, send email, reply to comment and moderate comment. The list_courses endpoint returns courses in your school with name, published state and URL. Each endpoint takes simple JSON inputs like course_id, lesson_id or body_markdown and works both as an MCP tool for agents and as a REST call for scripts.

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

Teachable has a public API, but only on the Growth plan and up, and it reads courses and lecture content and manages users, enrollments, pricing plans and transactions (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Teachable with 15 endpoints (6 read, 9 write): your AI agent signs in as you and does the work.

## Does Teachable have an official API?

Teachable has a public API, but only on the Growth plan and up, and it reads courses and lecture content and manages users, enrollments, pricing plans and transactions (checked 11 Oct 2026). Lesson editing, coupons, emails to students and comments are not in it.

| Task | Teachable official | Cotlet |
|---|---|---|
| List courses and read lesson content | Partly: Growth plan and up, read only | Yes |
| List the students of a course | Partly: Growth plan and up | Yes |
| Enroll a student in a course | Partly: Growth plan and up; Zapier has an Enroll User in Course action | Yes |
| Create, edit and publish lessons | No: The API reads a lecture and marks it complete for a student | Yes |
| Create and archive coupons | No | Yes |
| Email the students of a course | No | Yes |
| Approve, deny and reply to comments | No: Zapier has a New Comment trigger only | Yes |

Sources: [Teachable API quickstart (Growth plan or higher, API key)](https://docs.teachable.com/docs/quickstart-guide), [Teachable API reference index](https://docs.teachable.com/llms.txt), [Teachable MCP, experimental (help center)](https://support.teachable.com/en/articles/12703527-teachable-mcp), [Teachable on Zapier: 20 triggers, 4 actions, 1 search](https://zapier.com/apps/teachable/integrations), [Teachable Help: Course Comments (moderation, Pending Approval)](https://support.teachable.com/en/articles/11682464-course-comments), [Teachable Help: Price your products (coupons)](https://support.teachable.com/en/articles/15627279-price-your-products)

## For AI agents

```text
Teachable has a public API, but only on the Growth plan and up, and it reads courses and lecture content and manages users, enrollments, pricing plans and transactions (checked 11 Oct 2026). Lesson editing, coupons, emails to students and comments are not in it.
Cotlet provides a hosted MCP server and REST API for Teachable: 15 tools (6 read, 9 write).
Access       Request access at https://cotlet.dev/app/signup?app=teachable; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/teachable
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_courses, get_curriculum, get_lesson, list_students, list_comments, list_coupons, create_lesson, update_lesson, publish_lesson, create_coupon, archive_coupon, enroll_student, send_email, reply_to_comment, moderate_comment
Confirm      update_lesson, publish_lesson, create_coupon, archive_coupon, enroll_student, send_email, reply_to_comment, moderate_comment (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/teachable-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=teachable (Teachable is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Teachable once in a browser. 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 Teachable 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 Teachable 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.
Session: the user signs in to Teachable in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Teachable's terms; Cotlet is not affiliated with Teachable.
```

## What can an AI agent do in Teachable?

Cotlet is best for Teachable course creators who run their school without a developer and want their AI agent to edit lessons, create coupons, email students and answer comments without running or fixing a server.

- **[Create coupon codes for a sale](https://cotlet.dev/integrations/teachable-api-mcp-server/create-discount-coupons)**: "Make a 30% coupon BLACKFRIDAY26 for all courses, 100 uses, ending 1 December. Check first that the code is free." → `list_coupons`, `create_coupon`, `archive_coupon`
- **Email all students of a course**: "Email everyone in the Python course that the live Q&A moved to Thursday." → `list_courses`, `send_email`
- **[Moderate and answer lesson comments](https://cotlet.dev/integrations/teachable-api-mcp-server/moderate-lesson-comments)** (runs: daily): "Go through the Pending Approval comments in all my courses: approve real questions, deny spam, and draft an answer to each question from the lesson." → `list_comments`, `get_curriculum`, `get_lesson`, `moderate_comment`, `reply_to_comment`
- **[Update lessons from Markdown files](https://cotlet.dev/integrations/teachable-api-mcp-server/update-lessons-from-markdown)**: "Compare my Python course with the Markdown files in ./scripts, update the lessons that changed, and ask me before touching published ones." → `list_courses`, `get_curriculum`, `get_lesson`, `update_lesson`, `create_lesson`, `publish_lesson`
- **Enroll students from a CSV**: "Add the 12 new hires from team.csv to the Onboarding course." → `list_courses`, `enroll_student`

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

Yes. Cotlet does not replace your automation platform: it gives it a Teachable 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 moderate and answer lesson comments, 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 to https://cotlet.dev/api/v1/teachable/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/teachable/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/teachable/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/teachable/{tool} with your API key. | cron or GitHub Actions. |

## Tools

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

### list_courses

Courses in your school with name, published state and URL. Access: read. REST: `POST /api/v1/teachable/list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `published` | boolean | no | Only published courses. Default: all. |

Returns every course in your school, in the order the Courses page shows them. Use course_id from each item in the other tools. Set published to see only the courses students can enroll in.

Example response:

```json
{
  "courses": [
    {
      "course_id": "1204512",
      "name": "Python for Beginners",
      "published": true,
      "url": "https://yourschool.teachable.com/p/python-for-beginners"
    },
    {
      "course_id": "1260077",
      "name": "Team Onboarding",
      "published": false,
      "url": "https://yourschool.teachable.com/p/team-onboarding"
    }
  ]
}
```

### get_curriculum

Sections and lessons of a course, in order, with published and public preview flags. Access: read. REST: `POST /api/v1/teachable/get_curriculum`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |

Returns the Curriculum tab of one course: sections in order, and the lessons inside each section in order. Each lesson has a published flag and a public preview flag. Use lesson_id with get_lesson, update_lesson and publish_lesson.

Example response:

```json
{
  "course_id": "1204512",
  "sections": [
    {
      "section_id": "9120331",
      "name": "Basics",
      "lessons": [
        {
          "lesson_id": "35120871",
          "name": "Lesson 1: Welcome",
          "published": true,
          "public_preview": true
        },
        {
          "lesson_id": "35120874",
          "name": "Lesson 3: Functions",
          "published": true,
          "public_preview": false
        }
      ]
    }
  ]
}
```

### get_lesson

Lesson content as blocks: text as Markdown, plus the type of each video, PDF, audio, quiz and other block. Access: read. REST: `POST /api/v1/teachable/get_lesson`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `lesson_id` | string | yes | Lesson ID from get_curriculum. |

Returns the blocks of one lesson in the order the lesson editor shows them. Text & Image blocks come back as Markdown with a block_id. Other blocks (video, PDF viewer, audio, resource, quiz and so on) come back with their type and title only.

Example response:

```json
{
  "lesson_id": "35120874",
  "name": "Lesson 3: Functions",
  "published": true,
  "blocks": [
    {
      "block_id": "b_5521",
      "type": "text_and_image",
      "body_markdown": "# Functions\n\nA function groups steps you want to reuse."
    },
    {
      "block_id": "b_5522",
      "type": "video",
      "title": "Functions in 6 minutes"
    }
  ]
}
```

### list_students

Students with name, email and join date, or the students of one course. Access: read. REST: `POST /api/v1/teachable/list_students`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | no | Only students enrolled in this course. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists students of your school, newest first. Pass course_id to list only the students enrolled in one course. Pages hold up to 100 students; pass next_cursor back as cursor for the next page. Use the emails with send_email when you need part of a course.

Example response:

```json
{
  "students": [
    {
      "user_id": "70418822",
      "name": "Maria Kowal",
      "email": "maria.kowal@example.com",
      "joined_at": "2026-09-28T10:14:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_comments

Lesson comments across your school or one course, with author, lesson, status and unread flag. Access: read. REST: `POST /api/v1/teachable/list_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | no | Only comments in this course. Default: all courses. |
| `status` | enum | no | all, pending or denied. Default: all. |
| `unread_only` | boolean | no | Only comments you have not marked as read. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists comments the way Site, Comments does, newest first. Status pending returns the Pending Approval queue, which exists only when Comment moderation is on; denied returns comments you denied, which stay in your admin. Use comment_id with moderate_comment and reply_to_comment.

Example response:

```json
{
  "comments": [
    {
      "comment_id": "88120431",
      "course_id": "1204512",
      "lesson": "Lesson 3: Functions",
      "author": "Maria Kowal",
      "body": "Can a function return two values?",
      "status": "pending",
      "unread": true,
      "created_at": "2026-10-09T14:32:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_coupons

School and product coupons with code, discount, uses, expiry and status. Access: read. REST: `POST /api/v1/teachable/list_coupons`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `include_archived` | boolean | no | Also list archived coupons. Default: false. |

Returns the coupons from the Coupons page: school coupons (all products or one product type) and product coupons (one pricing plan). Archived coupons are left out unless you ask for them. Check the list before create_coupon so a code is not used twice.

Example response:

```json
{
  "coupons": [
    {
      "coupon_id": "3917702",
      "name": "Summer sale",
      "code": "SUMMER20",
      "discount": "20%",
      "applies_to": "all_products",
      "expires_at": "2026-09-01",
      "quantity": 500,
      "used": 212,
      "status": "archived"
    }
  ]
}
```

### create_lesson

New unpublished lesson at the end of a section, with text from Markdown. Access: write. REST: `POST /api/v1/teachable/create_lesson`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `section_id` | string | yes | Section ID from get_curriculum. |
| `title` | string | yes | Lesson name. |
| `body_markdown` | string | no | Text for a Text & Image block. Images by URL. |

Adds a lesson to a section, like New lesson in the Curriculum tab. New lessons start unpublished, so no student sees it until publish_lesson runs. That is why create_lesson runs without asking first.

Example response:

```json
{
  "lesson_id": "35120990",
  "name": "Lesson 4: Loops",
  "section_id": "9120331",
  "published": false
}
```

### update_lesson

Rename a lesson or replace the text of its Text & Image block. Other blocks stay as they are. Access: write, asks the user first. REST: `POST /api/v1/teachable/update_lesson`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `lesson_id` | string | yes | Lesson ID from get_curriculum. |
| `title` | string | no | New lesson name. |
| `body_markdown` | string | no | New text for the Text & Image block. |
| `block_id` | string | no | Text & Image block ID from get_lesson. Default: the first one. |

Renames a lesson and replaces the text of one Text & Image block; video, PDF, audio and quiz blocks are not touched. Teachable saves edits to a published lesson live at once, so students see the change right away. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lesson_id": "35120874",
  "name": "Lesson 3: Functions",
  "updated_block_id": "b_5521",
  "published": true,
  "updated_at": "2026-10-11T09:20:00+02:00"
}
```

### publish_lesson

Publish a lesson so enrolled students see it, or unpublish it. Access: write, asks the user first. REST: `POST /api/v1/teachable/publish_lesson`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `course_id` | string | yes | Course ID from list_courses. |
| `lesson_id` | string | yes | Lesson ID from get_curriculum. |
| `published` | boolean | no | false unpublishes. Default: true. |

Does what Publish and Unpublish do in the lesson editor. Unpublished lessons are hidden from students, and a section whose lessons are all unpublished is hidden too. The course itself must be published and enrollable on its Information tab. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lesson_id": "35120874",
  "published": true
}
```

### create_coupon

Coupon code for all products, one product type or one pricing plan. Access: write, asks the user first. REST: `POST /api/v1/teachable/create_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Internal name, for your own list. |
| `code` | string | yes | Letters and numbers only. |
| `discount_type` | enum | yes | percent or amount. |
| `discount` | integer | yes | Percent off, or the fixed amount off. |
| `applies_to` | enum | no | all_products, courses, coaching, digital_downloads, memberships, bundles or pricing_plan. Default: all_products. |
| `pricing_plan_id` | string | no | Required when applies_to is pricing_plan. |
| `expires_at` | date | no | Last day the code works. |
| `quantity` | integer | no | Number available, 1 to 10000. |

Creates a coupon on the Coupons page. The code holds letters and numbers only. Quantity is the number available, up to 10,000. Teachable does not sell a paid product below $1.00 USD. The code takes money off your sales. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "coupon_id": "3918274",
  "name": "Black Friday 2026",
  "code": "BLACKFRIDAY",
  "discount": "30%",
  "applies_to": "courses",
  "expires_at": "2026-12-01",
  "quantity": 100,
  "used": 0,
  "status": "active"
}
```

### archive_coupon

Unpublish a coupon so the code stops working. Archived codes can be used again. Access: write, asks the user first. REST: `POST /api/v1/teachable/archive_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `coupon_id` | string | yes | Coupon ID from list_coupons. |

Archives a coupon, which is how Teachable unpublishes one. Buyers who have the code can no longer use it. An archived code can be used for a new coupon later. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "coupon_id": "3917702",
  "code": "SUMMER20",
  "status": "archived"
}
```

### enroll_student

Enroll a student in a course for free, adding them to your school first if the email is new. Access: write, asks the user first. REST: `POST /api/v1/teachable/enroll_student`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email` | string | yes | Student email. |
| `course_id` | string | yes | Course ID from list_courses. |
| `name` | string | no | Full name, used when the student is new. |

Does what manual enrollment does in the Users menu: the student gets access to the course with no payment. A new email is added to your school first, because adding a student does not enroll them. Teachable sends no confirmation email for manual enrollments, and plan limits such as access duration or enrollment caps do not apply. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "user_id": "70418901",
  "email": "maria.kowal@example.com",
  "course_id": "1204512",
  "status": "enrolled",
  "user_created": true,
  "confirmation_email_sent": false
}
```

### send_email

Send an email from your school to chosen users, the students of a course or all users, as on the Emails, Compose page. Access: write, asks the user first. REST: `POST /api/v1/teachable/send_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `to` | enum | yes | users, course or all_users. |
| `user_emails` | string[] | no | Recipients when to is users. |
| `course_id` | string | no | Recipients when to is course. |
| `subject` | string | yes | Email subject. |
| `body_markdown` | string | yes | Email body. |

Sends a custom email from your school. Students who opted out of instructional and promotional emails in their profile do not receive it. To reach part of a course, take the emails from list_students and pass them in user_emails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "email_id": "em_4471",
  "to": "course",
  "course_id": "1204512",
  "subject": "Live Q&A moved to Thursday",
  "status": "sent",
  "sent_at": "2026-10-11T09:30:00+02:00"
}
```

### reply_to_comment

Reply to a lesson comment as the school owner. The reply is public to the course. Access: write, asks the user first. REST: `POST /api/v1/teachable/reply_to_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `comment_id` | string | yes | Comment ID from list_comments. |
| `body` | string | yes | Reply text. |

Posts a reply under one comment, as the Reply button does in your comment admin. Comments are public and cannot be made private, so the whole course sees the reply. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "reply_id": "88120502",
  "comment_id": "88120431",
  "status": "published"
}
```

### moderate_comment

Approve or deny a comment held in Pending Approval. Access: write, asks the user first. REST: `POST /api/v1/teachable/moderate_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `comment_id` | string | yes | Comment ID from list_comments. |
| `decision` | enum | yes | approve or deny. |

Does what Approve and Deny do on a pending comment. An approved comment appears on the lesson. A denied comment stays in your comment admin with a Denied tag and is hidden from students. Pending Approval exists only when Comment moderation is on. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "88120431",
  "status": "approved"
}
```

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

Connecting Teachable takes three steps: request access, sign in to Teachable once, then add one MCP server or call the REST API with the same key.

### Connect Teachable to your agent.

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

2. **Sign in to Teachable once** Open the connect page from the console and sign in to Teachable the way you always do. We keep the session, never your password, and you can revoke it anytime.

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 Teachable 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.

```
Make a 30% coupon BLACKFRIDAY26 for all courses, 100 uses, ending 1 December. Check first that the code is free.
```

### Call Teachable 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 a POST endpoint at /api/v1/teachable/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/teachable/create_coupon \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Black Friday 2026","code":"BLACKFRIDAY","discount_type":"percent","discount":30,"applies_to":"courses","expires_at":"2026-12-01","quantity":100}'
```

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

```
{
  "coupon_id": "3918274",
  "name": "Black Friday 2026",
  "code": "BLACKFRIDAY",
  "discount": "30%",
  "applies_to": "courses",
  "expires_at": "2026-12-01",
  "quantity": 100,
  "used": 0,
  "status": "active"
}
```

## Why use Cotlet for Teachable?

**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 Teachable yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

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

## Is there a Teachable MCP server on GitHub?

Yes. Open-source Teachable MCP servers exist on GitHub, usually maintained by one person, and most of them wrap the public API, so they need a Growth plan and cannot edit lessons, create coupons or send emails. You install one on your own computer and keep it running yourself; when something changes, you or the maintainer fix it. Teachable also has an experimental MCP of its own, which runs locally and works with Claude Desktop only. Cotlet hosts a server that works in your school as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone or install the package, add your API key to each MCP client | Request access, sign in to Teachable once, add one MCP server or API key |
| Plan needed | Growth plan or higher, for the API key | No API key: Cotlet signs in to your school like you do |
| What it can do | What the public API has: courses, lecture reads, users, enrollments, pricing plans, transactions | Lessons, coupons, emails to students and comments, plus courses and enrollments |
| When Teachable 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 login | API key in a config file on your computer, valid until you revoke it | Your session, encrypted in an EU vault, revoked in one click; if Teachable logs you out, your agent gets a link to sign in again |
| 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 with 5,000 credits, then credits per call |

### 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 Teachable 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Teachable API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Teachable API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

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

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Teachable yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Teachable tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Teachable in your dashboard: the session is deleted and access ends at once. 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.
- **Teachable's terms:** You use your own Teachable account and stay responsible for following Teachable's terms. Cotlet is independent and not affiliated with Teachable. [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?**

Request access and pick Teachable. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Teachable once in your browser 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 a hosted server safe? My Teachable session would leave my computer.**

Cotlet keeps your Teachable session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need the Growth plan or an API key?**

No. Cotlet signs in to your own school like you do, so it does not use the API key that Teachable's public API and its experimental MCP need on the Growth plan or higher. What you can change still follows what your account can do in the Teachable admin.

**Will students get an email when my agent enrolls them?**

No. Teachable sends no confirmation email for manual enrollments. If you want them to hear about it, send_email can write to them, and students who opted out of instructional and promotional emails do not receive it.

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

No. Every call to update_lesson, publish_lesson, create_coupon, archive_coupon, enroll_student, send_email, reply_to_comment or moderate_comment 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_lesson runs without asking, because it sends nothing to anyone and one call undoes it.

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

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/teachable/{tool} from the HTTP Request node.