# Uscreen API and MCP server

> Yes, in part: Uscreen has a Publisher API for stores on UscreenPlus that manages customers, access, subscriptions, groups and invoices and only reads videos, collections and live events (checked 11 Oct 2026). Its official Uscreen MCP (beta, for stores with developer or API access) reads analytics, members and the catalog and edits titles, tags, SEO, thumbnails and publish status, but lists no way to upload videos, build collections, create live events or coupons, or post in the community.

Video membership platform for creators: sell subscriptions, courses and live streams from your own branded site and apps, with a community.

## What is the Uscreen API?

Cotlet's Uscreen API exposes 15 endpoints for your own Uscreen account: list videos, get video, list collections, get collection, list live events, get content analytics, list community channels, upload video, update video, publish or schedule video, create collection, set collection playlist, create live event, create coupon and create community post. The list_videos endpoint returns videos in your library with status, categories and release date. Each endpoint takes simple JSON inputs like limit, search or cursor 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 (7 read, 8 write)
- **Updated:** 2026-10-11

Yes, in part: Uscreen has a Publisher API for stores on UscreenPlus that manages customers, access, subscriptions, groups and invoices and only reads videos, collections and live events (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Uscreen with 15 endpoints (7 read, 8 write): your AI agent signs in as you and does the work.

## Does Uscreen have an official API?

Yes, in part: Uscreen has a Publisher API for stores on UscreenPlus that manages customers, access, subscriptions, groups and invoices and only reads videos, collections and live events (checked 11 Oct 2026). Its official Uscreen MCP (beta, for stores with developer or API access) reads analytics, members and the catalog and edits titles, tags, SEO, thumbnails and publish status, but lists no way to upload videos, build collections, create live events or coupons, or post in the community.

| Task | Uscreen official | Cotlet |
|---|---|---|
| Upload a video | No: The MCP can attach a file and replace a thumbnail, not upload a video | Yes |
| Create a collection and set its playlist | No: The API and the MCP only read collections | Yes |
| Schedule a video release | Partly: The MCP publishes or unpublishes content, no release date is listed | Yes |
| Edit titles, descriptions, tags and SEO | Partly: Uscreen MCP beta, stores with developer access | Yes |
| Top videos and watch time | Partly: Uscreen MCP beta reads content analytics, stores with developer access | Yes |
| Create a live event | No: The API and the MCP only read live events | Yes |
| Create a coupon | No | Yes |
| Post in your community | No | Yes |

Sources: [Uscreen Help Center: Uscreen MCP](https://help.uscreen.tv/en/articles/15643974-uscreen-mcp), [Uscreen Help Center: Uscreen API](https://help.uscreen.tv/en/articles/4576093-uscreen-api), [Uscreen pricing: API access is a Custom plan feature](https://www.uscreen.tv/pricing/), [Uscreen on Zapier: 5 triggers, 2 actions](https://zapier.com/apps/uscreen/integrations)

## For AI agents

```text
Yes, in part: Uscreen has a Publisher API for stores on UscreenPlus that manages customers, access, subscriptions, groups and invoices and only reads videos, collections and live events (checked 11 Oct 2026). Its official Uscreen MCP (beta, for stores with developer or API access) reads analytics, members and the catalog and edits titles, tags, SEO, thumbnails and publish status, but lists no way to upload videos, build collections, create live events or coupons, or post in the community.
Cotlet provides a hosted MCP server and REST API for Uscreen: 15 tools (7 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=uscreen; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/uscreen
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_videos, get_video, list_collections, get_collection, list_live_events, get_content_analytics, list_community_channels, upload_video, update_video, publish_video, create_collection, set_collection_playlist, create_live_event, create_coupon, create_community_post
Confirm      publish_video, create_live_event, create_coupon, create_community_post (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/uscreen-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=uscreen (Uscreen is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Uscreen 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 Uscreen server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Uscreen 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 Uscreen's terms; Cotlet is not affiliated with Uscreen.
```

## What can an AI agent do in Uscreen?

Cotlet is best for course and membership creators who upload, schedule and promote content in Uscreen without running or fixing a server.

- **[Build a course collection with week dividers and drip](https://cotlet.dev/integrations/uscreen-api-mcp-server/build-course-collection)**: "Build a Mobility Basics course from my uploaded Mobility lessons: one divider per week, two lessons a week, and each week dripping 7 days after the one before." → `list_videos`, `list_collections`, `get_collection`, `create_collection`, `set_collection_playlist`
- **[Schedule a batch of video releases](https://cotlet.dev/integrations/uscreen-api-mcp-server/schedule-video-releases)** (runs: weekly): "Schedule the six unpublished Strength Block videos for every Monday at 7:00 starting 2 November, keep them visible as upcoming in the catalog and email members on each release." → `list_videos`, `get_video`, `update_video`, `publish_video`
- **[Schedule recurring live streams](https://cotlet.dev/integrations/uscreen-api-mcp-server/schedule-recurring-live-streams)** (runs: weekly): "Create the Thursday 18:00 Q&A live stream for the next four weeks over RTMP, with live chat and preregistration on, and send me the stream URL and key for each date." → `list_live_events`, `create_live_event`
- **Create a promo coupon**: "Make a 30% coupon SPRING30 for the yearly plan, first payment only, 200 uses, ending April 30." → `create_coupon`
- **Report top videos and watch time** (runs: weekly): "Which 3 videos got the most views in October, with watch time and completion rate?" → `get_content_analytics`, `get_video`
- **Post a community announcement**: "Post in the announcements channel that tonight's class moves to 19:00." → `list_community_channels`, `create_community_post`

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

Yes. Cotlet does not replace your automation platform: it gives it a Uscreen 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 schedule a batch of video releases, 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/uscreen/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/uscreen/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/uscreen/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/uscreen/{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 Uscreen.

### list_videos

Videos in your library with status, categories and release date. Access: read. REST: `POST /api/v1/uscreen/list_videos`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | published, unpublished or scheduled. Empty: all. |
| `search` | string | no | Match on title. |
| `limit` | integer | no | Maximum videos to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns videos with their publication status, categories and, for scheduled videos, the release date. A video that is still processing is marked as such. Uscreen processes a new upload for 10 minutes to 72 hours. Videos without a category are listed but stay out of the catalog.

Example response:

```json
{
  "videos": [
    {
      "video_id": "2390417",
      "title": "Mobility Basics 1: Ankles",
      "status": "unpublished",
      "category_ids": [
        "48211"
      ],
      "processing": false
    },
    {
      "video_id": "2390418",
      "title": "Mobility Basics 2: Hips",
      "status": "scheduled",
      "release_at": "2026-11-02T07:00:00-05:00",
      "category_ids": [
        "48211"
      ],
      "processing": false
    }
  ],
  "next_cursor": null
}
```

### get_video

One video: title, description, tags, categories, publication status and the collections it is in. Access: read. REST: `POST /api/v1/uscreen/get_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from list_videos. |

Returns the details shown on the video page in Uscreen. If the video is scheduled, it includes the release date and whether it shows as Coming Soon. It also lists the collections that contain the video, because one video can sit in several.

Example response:

```json
{
  "video_id": "2390417",
  "title": "Mobility Basics 1: Ankles",
  "description": "A 12 minute ankle mobility routine.",
  "status": "unpublished",
  "category_ids": [
    "48211"
  ],
  "tags": [
    "mobility",
    "beginner"
  ],
  "collection_ids": [
    "118204"
  ]
}
```

### list_collections

Collections with status, categories and number of videos. Access: read. REST: `POST /api/v1/uscreen/list_collections`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Match on title. |
| `limit` | integer | no | Maximum collections to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each collection with its publication status, categories and video count. A collection appears in the catalog only when it is published and has a category.

Example response:

```json
{
  "collections": [
    {
      "collection_id": "118204",
      "title": "Mobility Basics",
      "status": "unpublished",
      "category_ids": [
        "48211"
      ],
      "video_count": 2
    }
  ],
  "next_cursor": null
}
```

### get_collection

A collection with its playlist in order: videos, dividers and drip days. Access: read. REST: `POST /api/v1/uscreen/get_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |

Returns the playlist in the order viewers see it, with section dividers and the drip delay of each video. It also returns the collection access, gated or free, because drip only works on gated collections.

Example response:

```json
{
  "collection_id": "118204",
  "title": "Mobility Basics",
  "status": "unpublished",
  "access": "gated",
  "items": [
    {
      "divider": "Week 1"
    },
    {
      "video_id": "2390417",
      "title": "Mobility Basics 1: Ankles",
      "drip_days": 0
    },
    {
      "divider": "Week 2"
    },
    {
      "video_id": "2390418",
      "title": "Mobility Basics 2: Hips",
      "drip_days": 7
    }
  ]
}
```

### list_live_events

Live events with start time, streaming method and status. Access: read. REST: `POST /api/v1/uscreen/list_live_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Match on title. |
| `limit` | integer | no | Maximum events to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each live event with its start time, streaming method (Live Studio, RTMP or Zoom), publication status and whether preregistration is on. It never returns a stream key; create_live_event does that once.

Example response:

```json
{
  "events": [
    {
      "event_id": "77310",
      "title": "Thursday Q&A",
      "start_at": "2026-11-05T18:00:00-05:00",
      "method": "rtmp",
      "status": "published",
      "preregistration": true
    }
  ],
  "next_cursor": null
}
```

### get_content_analytics

Views, watch time and completion for videos, live events or collections in a period. Access: read. REST: `POST /api/v1/uscreen/get_content_analytics`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report` | enum | yes | videos, live_events or collections. |
| `from` | date | yes | First day of the period. |
| `to` | date | yes | Last day of the period. |
| `limit` | integer | no | Items to return, most views first. |

Returns the totals for the period and one row per item, most views first, matching the Content Analytics reports in Uscreen. Video rows include viewers, watch time and completion rate. Live event rows include preregistered, attendees and replays. Offline viewing is not tracked by Uscreen, so it is not counted.

Example response:

```json
{
  "report": "videos",
  "from": "2026-10-01",
  "to": "2026-10-31",
  "totals": {
    "views": 1840,
    "viewers": 612
  },
  "rows": [
    {
      "video_id": "2390417",
      "title": "Mobility Basics 1: Ankles",
      "views": 412,
      "viewers": 301,
      "total_watch_time": "71h 20m",
      "completion_rate": "64%"
    },
    {
      "video_id": "2390418",
      "title": "Mobility Basics 2: Hips",
      "views": 366,
      "viewers": 280,
      "total_watch_time": "58h 05m",
      "completion_rate": "59%"
    },
    {
      "video_id": "2390422",
      "title": "Warm-up Flow",
      "views": 301,
      "viewers": 254,
      "total_watch_time": "40h 10m",
      "completion_rate": "71%"
    }
  ]
}
```

### list_community_channels

Channels of your community with ID, name and whether they are public or private. Access: read. REST: `POST /api/v1/uscreen/list_community_channels`.

No parameters.

Returns every channel the signed-in admin can see, including private ones. Channel names are lowercase, with hyphens or underscores instead of spaces. The default general channel is always public.

Example response:

```json
{
  "channels": [
    {
      "channel_id": "ch_general",
      "name": "general",
      "visibility": "public"
    },
    {
      "channel_id": "ch_announcements",
      "name": "announcements",
      "visibility": "public"
    }
  ]
}
```

### upload_video

Upload a video file from a URL. It is saved unpublished and processed by Uscreen. Access: write. REST: `POST /api/v1/uscreen/upload_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `file_url` | string | yes | Public or signed URL of an MP4 file, H.264, 16:9 recommended. |
| `title` | string | yes | Video title. |
| `description` | string | no | Shown on the video page. |
| `category_ids` | string[] | no | Categories it appears under. Without one it stays out of the catalog. |

Cotlet downloads the file and uploads it to Content > Videos, then sets the video to Unpublished. Uscreen then transcodes it, which takes 10 minutes to 72 hours depending on size, bit rate and format; the response says processing until it is ready. Files over 8 Mbps or outside MP4 with H.264 can cause playback problems or slow processing. It reaches no one, because the video stays unpublished until publish_video, so it runs without asking.

Example response:

```json
{
  "video_id": "2390417",
  "title": "Mobility Basics 1: Ankles",
  "status": "unpublished",
  "processing": true,
  "category_ids": [
    "48211"
  ]
}
```

### update_video

Change the title, description, tags or categories of a video. Access: write. REST: `POST /api/v1/uscreen/update_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from list_videos. |
| `fields` | object | yes | Any of title, description, tags, category_ids. |

Changes only the fields you send and returns the previous values, so one more call restores them. Tags replace the whole tag list. A published video shows the new text to members at once. It runs without asking because it sends nothing to anyone and one call undoes it.

Example response:

```json
{
  "video_id": "2390417",
  "updated": [
    "title",
    "tags"
  ],
  "previous": {
    "title": "Ankles",
    "tags": [
      "mobility"
    ]
  }
}
```

### publish_video

Publish a video now or schedule its release, optionally emailing members. Access: write, asks the user first. REST: `POST /api/v1/uscreen/publish_video`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `video_id` | string | yes | Video ID from list_videos. |
| `release_at` | datetime | no | ISO 8601 with offset. Empty: publish now. |
| `send_email` | boolean | no | Email all members with access when it goes live. Default: false. |
| `show_coming_soon` | boolean | no | Show it as Coming Soon in the catalog until release. Default: true. |

Sets Visibility to Published, or to Scheduled when release_at is given. Uscreen releases at the time in your store time zone (Settings > General), so Cotlet converts the offset you send. The video needs a category to appear in the catalog, and it stays out of the catalog until Uscreen finishes processing it. With send_email, the broadcast reaches every member with access. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "video_id": "2390417",
  "status": "scheduled",
  "release_at": "2026-11-02T07:00:00-05:00",
  "show_coming_soon": true,
  "send_email": true
}
```

### create_collection

New collection from uploaded videos, saved unpublished. Access: write. REST: `POST /api/v1/uscreen/create_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Collection title. |
| `description` | string | no | Shown on the collection home page. |
| `video_ids` | string[] | no | Videos to add, in order. They must already be uploaded. |
| `category_ids` | string[] | no | Categories it appears under. Without one it stays out of the catalog. |

Creates the collection in Content > Collections and adds the videos to its playlist. It stays unpublished, so it reaches no one, and it runs without asking; publish it in Uscreen when it is ready. Uscreen advises keeping a collection under 50 videos. Pricing and access keep their defaults, so check them before you publish.

Example response:

```json
{
  "collection_id": "118204",
  "title": "Mobility Basics",
  "status": "unpublished",
  "video_count": 2,
  "category_ids": [
    "48211"
  ]
}
```

### set_collection_playlist

Replace the playlist of a collection: video order, dividers and drip days. Access: write. REST: `POST /api/v1/uscreen/set_collection_playlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |
| `items` | object[] | yes | Ordered list of { video_id, drip_days } or { divider: "Week 1" }. drip_days needs Gated access. |

Replaces the whole playlist with the order you send and returns the previous one, so one more call restores it. Drip delays are days after a viewer first opens the collection, and Uscreen unlocks each video about every 2 hours after that delay. It is rejected if drip_days is set on a collection with free access. It runs without asking because members only see a change once the collection is published.

Example response:

```json
{
  "collection_id": "118204",
  "title": "Mobility Basics",
  "status": "unpublished",
  "access": "gated",
  "playlist_items": 4,
  "videos": 2,
  "dividers": 2
}
```

### create_live_event

Create a live event; for RTMP it returns the stream URL and stream key. Access: write, asks the user first. REST: `POST /api/v1/uscreen/create_live_event`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Event title. |
| `start_at` | datetime | yes | ISO 8601 with offset. |
| `method` | enum | yes | live_studio, rtmp or zoom. |
| `description` | string | no | Shown on the event page. |
| `category_ids` | string[] | no | Categories it appears under. Without one it stays out of the catalog. |
| `preregistration` | boolean | no | Let viewers register before it starts. Default: false. |
| `live_chat` | boolean | no | Turn on live chat. Default: false. |
| `publish` | boolean | no | Set Visibility to Published. Default: false, saved unpublished. |

Creates the event in Content > Live Streaming. For rtmp the response includes the stream URL and the stream key once; paste both into OBS or similar software, and keep the key private. Live Studio and RTMP events count against your plan's live streaming hours. Purchase and access options stay at their defaults, so check them before the event. Published events are visible to members, and with preregistration on, the event shows a countdown. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "event_id": "77310",
  "title": "Thursday Q&A",
  "start_at": "2026-11-05T18:00:00-05:00",
  "method": "rtmp",
  "status": "published",
  "preregistration": true,
  "live_chat": true,
  "stream_url": "rtmp://live.example.com/app",
  "stream_key": "sk_example_4f9a21"
}
```

### create_coupon

New coupon code with a discount, target, limits and expiry. Access: write, asks the user first. REST: `POST /api/v1/uscreen/create_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `code` | string | yes | Letters and numbers only, no spaces. |
| `discount_type` | enum | yes | fixed or percentage. |
| `value` | number | yes | Percent off, or the fixed amount in the currency the coupon is denominated in. |
| `applies_to` | enum | yes | all_products, subscription, bundles or content. |
| `offer_ids` | string[] | no | Plans, bundles or content it applies to. Not used with all_products. |
| `duration` | enum | no | Subscription coupons only: once, forever or repeating. Default: once. |
| `duration_periods` | integer | no | Billing periods, when duration is repeating. |
| `expires_on` | date | no | Last day the code can be redeemed. |
| `redemption_limit` | integer | no | Most users who can redeem it. |

Creates the coupon in Marketing > Coupons. The code and the discount cannot be changed afterwards; a wrong code means deleting the coupon and creating a new one. The expiry only stops new redemptions and leaves discounts already applied. It changes what members pay, so it asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "coupon_id": "55102",
  "code": "SPRING30",
  "discount": "30% off",
  "applies_to": "subscription",
  "duration": "once",
  "expires_on": "2027-04-30",
  "redemption_limit": 200,
  "status": "active"
}
```

### create_community_post

Post as you in a community channel, now or at a set time. Access: write, asks the user first. REST: `POST /api/v1/uscreen/create_community_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `channel_id` | string | yes | Channel ID from list_community_channels. |
| `body` | string | yes | Post text. |
| `image_url` | string | no | Attach one image by URL: jpeg, png, webp or gif. |
| `publish_at` | datetime | no | ISO 8601 with offset. Empty: post now. |

Posts from your admin account in the channel you name, now or scheduled. Members who can see the channel see it in the feed. Large images can take a while and may time out after about a minute. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "post_id": "p_90417",
  "channel_id": "ch_announcements",
  "status": "published"
}
```

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

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

### Connect Uscreen to your agent.

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

2. **Sign in to Uscreen once** Open the connect page from the console and sign in to Uscreen 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 Uscreen 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.

```
Build a Mobility Basics course from my uploaded Mobility lessons: one divider per week, two lessons a week, and each week dripping 7 days after the one before.
```

### Call Uscreen 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/uscreen/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/uscreen/publish_video \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"video_id":"2390417","release_at":"2026-11-02T07:00:00-05:00","send_email":true,"show_coming_soon":true}'
```

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

```
{
  "video_id": "2390417",
  "status": "scheduled",
  "release_at": "2026-11-02T07:00:00-05:00",
  "show_coming_soon": true,
  "send_email": true
}
```

## Why use Cotlet for Uscreen?

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

## Is there a Uscreen MCP server on GitHub?

Uscreen runs its own hosted MCP server in beta for stores with developer access. It is strong on analytics, members and metadata edits, and it lists no way to create content.

|  | Uscreen MCP | Cotlet |
|---|---|---|
| Setup | Store owner copies the MCP URL from Settings, then each person approves access with OAuth | Request access, sign in to Uscreen once, add one MCP server or API key |
| Plans | Stores with developer or API access | Works from your admin login; features your Uscreen plan lacks stay unavailable |
| Creating content | Edits existing videos, collections and live events; no upload, collections, live events or coupons | Uploads videos, builds collections, schedules releases and live events, creates coupons and community posts |
| Members and billing | Looks up members, grants access, tags and invites customers | Not covered: Cotlet handles content, coupons and community |
| Your Uscreen session | OAuth scopes the store owner grants | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When Uscreen changes | Maintained by Uscreen, still in beta | Our team tests it daily and fixes it for you; failed calls are free |
| Price | Included with the plan that has developer access | 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 Uscreen 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 Uscreen API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Uscreen 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 Uscreen 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 Uscreen 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 Uscreen tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Uscreen 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.
- **Uscreen's terms:** You use your own Uscreen account and stay responsible for following Uscreen's terms. Cotlet is independent and not affiliated with Uscreen. [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 Uscreen. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Uscreen 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 Uscreen session would leave my computer.**

Cotlet keeps your Uscreen 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 UscreenPlus or API access to use Cotlet with Uscreen?**

No. Cotlet signs in to your admin like you do, so it does not need the API key or Uscreen MCP access. Your plan still decides which features exist; for example, Uscreen lists API access as a Custom plan feature on its pricing page.

**How long until an uploaded video can be published?**

Uscreen processes uploads for 10 minutes to 72 hours, depending on file size, bit rate and format, and notifies you when the video is ready to publish (Uscreen Help Center, Upload a video).

**Can I change a coupon after creating it?**

The code and the discount amount cannot be changed. Delete the coupon in Uscreen and create a new one (Uscreen Help Center, Coupons overview).

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

No. Every call to publish_video, create_live_event, create_coupon or create_community_post waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. upload_video, update_video, create_collection, set_collection_playlist runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Uscreen 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/uscreen/{tool} from the HTTP Request node.