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

# StreamElements API and MCP server

> StreamElements has a full REST API (kappa v2) with a documented OAuth2 flow, but no official MCP server (checked 17 Oct 2026). Its developer docs list the HTTP API, WebSockets and custom widgets. For your own channel the API takes a secret JWT you copy from the dashboard; for other channels it takes an OAuth client you receive from StreamElements.

Creator platform for live streamers: a chat bot with commands and timers, tipping, a loyalty store paid in points, overlays and alerts, and a song request queue.

## What is the StreamElements API?

Cotlet's StreamElements API exposes 14 endpoints for your own StreamElements account: list commands, list timers, list store items, list redemptions, list tips, get points leaderboard, list song requests, create command, update command, update timer, update store item, resolve redemption, adjust points and remove song request. The list_commands endpoint returns chat commands of your channel with reply, aliases, level, cooldowns, cost and whether they are on. Each endpoint takes simple JSON inputs like enabled, cursor or limit and works both as an operation of the streamelements_read or streamelements_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-20

StreamElements has a full REST API (kappa v2) with a documented OAuth2 flow, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for StreamElements with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does StreamElements have an official API?

StreamElements has a full REST API (kappa v2) with a documented OAuth2 flow, but no official MCP server (checked 17 Oct 2026). Its developer docs list the HTTP API, WebSockets and custom widgets. For your own channel the API takes a secret JWT you copy from the dashboard; for other channels it takes an OAuth client you receive from StreamElements.

| Task | StreamElements official | Cotlet |
|---|---|---|
| List chat commands | Yes: API: GET /bot/commands/{channel}; OAuth scope bot:read | Yes |
| Create or edit a chat command | Yes: API: POST and PUT on /bot/commands; OAuth scope bot:write | Yes |
| Edit a chat timer | Yes: API: PUT /bot/timers/{channel}/{timerId}; OAuth scope bot:write | Yes |
| List and edit store items | Partly: API has the endpoints, but the spec shows an empty request body for creating and updating items | Yes |
| Approve or decline store redemptions | Partly: API: PUT /store/{channel}/redemptions/{redemptionId}, body not documented | Yes |
| Review tips | Yes: API: GET /tips/{channel}, sort and filter by username; OAuth scope tips:read | Yes |
| Adjust a viewer's loyalty points and read the leaderboard | Yes: API: PUT /points/{channel}/{user}/{amount}; OAuth scope loyalty:write | Yes |
| Read and remove song requests | Yes: API: /songrequest/{channel}/queue; no matching OAuth scope in the list | Yes |

Sources: [StreamElements developers: API Reference](https://dev.streamelements.com/docs/api-docs/bcd899e16ac9a-se-api-docs), [StreamElements API docs (OpenAPI spec, GitHub)](https://github.com/StreamElements/api-docs/blob/main/api.yaml), [StreamElements API docs: Personal Access with a JWT](https://github.com/StreamElements/api-docs/blob/main/docs/Personal%20Access.md), [StreamElements Documentation: Developers](https://docs.streamelements.com/developers)

## For AI agents

```text
StreamElements has a full REST API (kappa v2) with a documented OAuth2 flow, but no official MCP server (checked 17 Oct 2026). Its developer docs list the HTTP API, WebSockets and custom widgets. For your own channel the API takes a secret JWT you copy from the dashboard; for other channels it takes an OAuth client you receive from StreamElements.
Cotlet provides a hosted MCP server and REST API for StreamElements: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=streamelements, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    streamelements_read, streamelements_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/streamelements, each operation at its own route, e.g. POST /api/v1/streamelements/commands
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_commands, list_timers, list_store_items, list_redemptions, list_tips, get_points_leaderboard, list_song_requests, create_command, update_command, update_timer, update_store_item, resolve_redemption, adjust_points, remove_song_request
Confirm      create_command, update_command, update_timer, update_store_item, resolve_redemption, adjust_points, remove_song_request (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/streamelements-api-mcp-server.md

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

## What can an AI agent do in StreamElements?

Cotlet is best for streamers and channel managers who are not developers and want their AI agent to keep commands, timers, the store and points up to date without running or fixing a server.

- **[Refresh chat commands every week](https://cotlet.dev/integrations/streamelements-api-mcp-server/update-chat-commands.md)** (runs: weekly): "Every Monday, update !schedule with this week's stream times and point !socials at my new link. Show me the old and new reply for each command, and create any command that is missing." → `list_commands`, `update_command`, `create_command`
- **[Approve or decline store redemptions](https://cotlet.dev/integrations/streamelements-api-mcp-server/manage-store-redemptions.md)** (runs: daily): "Go through the pending Stream Store redemptions. Approve the ones where the viewer filled in the requirement, decline the rest, and list anything unclear for me." → `list_redemptions`, `list_store_items`, `resolve_redemption`
- **[Reward top tippers with loyalty points](https://cotlet.dev/integrations/streamelements-api-mcp-server/reward-top-tippers-with-points.md)** (runs: weekly): "Every Sunday, find my three biggest tippers of the week, give each 500 bonus loyalty points and tell me the new balances." → `list_tips`, `get_points_leaderboard`, `adjust_points`
- **Rotate chat timers for a new stream schedule** (runs: weekly): "Switch off my "Charity stream" timer, switch on "New game week", and set its message and online interval to 15 minutes." → `list_timers`, `update_timer`
- **Clear unwanted song requests** (runs: daily): "Look at the media request queue and remove songs longer than my limit or already played this week. Tell me what you removed." → `list_song_requests`, `remove_song_request`

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

Yes. Cotlet does not replace your automation platform: it gives it a StreamElements 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 refresh chat commands every week, 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/streamelements/commands. | 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/streamelements/commands with your API key. | cron or GitHub Actions. |

## Tools

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

### list_commands

Chat commands of your channel with reply, aliases, level, cooldowns, cost and whether they are on. Access: read. REST: `GET /api/v1/streamelements/commands`. MCP: `streamelements_read → list_commands`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Only commands whose name or reply contains this text. |
| `enabled` | boolean | no | Only commands that are on (true) or off (false). |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the custom commands of your channel, ordered by name, with the reply text, aliases, who may use it, global and user cooldowns in seconds, point cost and response type. Search matches the command name and the reply text. Pass command_id to update_command.

Example response:

```json
{
  "commands": [
    {
      "command_id": "c_4b19e0",
      "trigger": "!schedule",
      "aliases": [
        "!stream"
      ],
      "reply": "Streams this week: Mon-Fri 19:00 CET.",
      "level": "Everyone",
      "cooldown": {
        "global": 5,
        "user": 15
      },
      "cost": 0,
      "response_type": "say",
      "enabled": true
    }
  ],
  "next_cursor": null
}
```

### list_timers

Chat timers with their messages, online interval, chat lines and whether they are on. Access: read. REST: `GET /api/v1/streamelements/timers`. MCP: `streamelements_read → list_timers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `enabled` | boolean | no | Only timers that are on (true) or off (false). |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the chat timers of your channel. A timer can hold several messages that it cycles through. Online interval is in minutes while the stream is live, and chat lines is the least number of chat messages in the last 5 minutes that lets the timer fire. Pass timer_id to update_timer.

Example response:

```json
{
  "timers": [
    {
      "timer_id": "t_20c7aa",
      "name": "Charity stream",
      "messages": [
        "Charity stream on Saturday! Details in !schedule"
      ],
      "online_interval_minutes": 30,
      "chat_lines": 5,
      "enabled": true
    }
  ],
  "next_cursor": null
}
```

### list_store_items

Stream Store items with type, cost in points, quantity, cooldowns and whether they are on. Access: read. REST: `GET /api/v1/streamelements/store-items`. MCP: `streamelements_read → list_store_items`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | no | stream_perk, sound_effect or access_code_list. Default: all. |
| `enabled` | boolean | no | Only items that are on (true) or off (false). |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the items of your Stream Store. Type is Stream Perk, Sound Effect or Access-Code List. Cost is in your loyalty points. Quantity is what is left to redeem. Pass item_id to update_store_item. Needs the Loyalty System, which YouTube accounts do not have.

Example response:

```json
{
  "items": [
    {
      "item_id": "i_5c0bb2",
      "name": "Sound: Air Horn",
      "type": "Sound Effect",
      "cost": 100,
      "quantity": "unlimited",
      "cooldown": {
        "global": 0,
        "user": 300
      },
      "enabled": true
    }
  ],
  "next_cursor": null
}
```

### list_redemptions

Store redemptions with item, viewer, cost and what the viewer filled in on the Requirements page. Access: read. REST: `GET /api/v1/streamelements/redemptions`. MCP: `streamelements_read → list_redemptions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | pending, approved or declined. Default: pending. |
| `item` | string | no | Only redemptions of this item name. |
| `viewer` | string | no | Only redemptions by this username. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns store redemptions, filtered by item, viewer or status, like the Redemptions page. Details holds the answers a viewer gave to the item's Requirements page. History reaches back up to a year. Pass redemption_id to resolve_redemption.

Example response:

```json
{
  "redemptions": [
    {
      "redemption_id": "rd_91a0f3",
      "item": "Pick my next game",
      "viewer": "luka_dev",
      "cost": 1500,
      "details": "Hollow Knight",
      "status": "pending",
      "redeemed_at": "2026-10-16T19:42:00Z"
    }
  ],
  "next_cursor": null
}
```

### list_tips

Tips your channel received, with amount, currency, tipper, message and time. Read only. Access: read. REST: `GET /api/v1/streamelements/tips`. MCP: `streamelements_read → list_tips`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `since` | datetime | no | Only tips after this time. |
| `until` | datetime | no | Only tips before this time. |
| `username` | string | no | Only tips from this username. |
| `sort` | enum | no | newest, oldest, amount_desc or amount_asc. Default: newest. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tips newest first by default, one row per tip. Sort by time or by amount, and filter by username or a date range. Currency is the one set in your Tipping settings. The tool only reads: it moves no money and does not change tip moderation.

Example response:

```json
{
  "tips": [
    {
      "tip_id": "tp_77d1c2",
      "username": "mika_r",
      "amount": 25,
      "currency": "USD",
      "message": "Great stream, keep it up!",
      "created_at": "2026-10-14T20:11:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_points_leaderboard

Viewers ranked by loyalty points or watch time, with each balance. Access: read. REST: `GET /api/v1/streamelements/points-leaderboard`. MCP: `streamelements_read → get_points_leaderboard`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `view` | enum | no | current, all_time or watch_time. Default: current. |
| `username` | string | no | Only this viewer. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the leaderboard for your loyalty currency. View is Current (points from watching and chat mini-games), All-Time (points from watch time only) or Watch Time (minutes watched). Pass username to look up one viewer, for example before adjust_points. Needs the Loyalty System.

Example response:

```json
{
  "view": "current",
  "entries": [
    {
      "rank": 1,
      "username": "mika_r",
      "points": 1840,
      "watch_time_minutes": 5120
    },
    {
      "rank": 2,
      "username": "luka_dev",
      "points": 775,
      "watch_time_minutes": 2980
    }
  ],
  "next_cursor": null
}
```

### list_song_requests

The Media Request queue: song, who asked, length and whether it was tipped. Access: read. REST: `GET /api/v1/streamelements/song-requests`. MCP: `streamelements_read → list_song_requests`.

No parameters.

Returns the queue in play order, with the song, the viewer who requested it, its length and whether it was a tipped or a free request. Pass song_id to remove_song_request. Media Request needs the Loyalty System, which YouTube accounts do not have.

Example response:

```json
{
  "queue": [
    {
      "song_id": "sg_8d210e",
      "title": "Lo-fi study beats",
      "requested_by": "tess_g",
      "length_seconds": 214,
      "tipped": false
    }
  ]
}
```

### create_command

Add a chat command with a reply, who may use it, cooldowns and response type. Access: write, asks the user first. REST: `POST /api/v1/streamelements/commands`. MCP: `streamelements_write → create_command`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `trigger` | string | yes | Command name with the prefix, e.g. '!discord'. |
| `reply` | string | yes | Text the bot answers with. Variables like $(user) work. |
| `level` | enum | no | Everyone, Subscriber, Regular, VIP, Moderator or Super Moderator. Default: Everyone. |
| `response_type` | enum | no | say, mention, reply or whisper. Default: say. |
| `cooldown_global` | integer | no | Seconds between any two uses. |
| `cooldown_user` | integer | no | Seconds the same viewer must wait. |
| `cost` | integer | no | Loyalty points charged per use. Needs the Loyalty System. |

Creates a custom command in your channel. Variables such as $(user) work in the reply, as in the dashboard. The command answers in your chat as soon as it is on, so viewers see it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "command_id": "c_9e41b7",
  "trigger": "!discord",
  "reply": "Join us on Discord: discord.example/lab",
  "level": "Everyone",
  "response_type": "say",
  "enabled": true
}
```

### update_command

Change the reply, level, cooldowns, cost, response type or on/off state of a command. Access: write, asks the user first. REST: `PATCH /api/v1/streamelements/commands/{command_id}`. MCP: `streamelements_write → update_command`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `command_id` | string | yes | Command ID from list_commands. |
| `reply` | string | no | New reply text. |
| `level` | enum | no | Everyone, Subscriber, Regular, VIP, Moderator or Super Moderator. |
| `response_type` | enum | no | say, mention, reply or whisper. |
| `cooldown_global` | integer | no | Seconds between any two uses. |
| `cooldown_user` | integer | no | Seconds the same viewer must wait. |
| `cost` | integer | no | Loyalty points charged per use. |
| `enabled` | boolean | no | false turns the command off. |

Changes only the fields you send; the rest stays as it is. Returns the command as saved. The new reply goes out in your chat the next time a viewer uses the command. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "command_id": "c_4b19e0",
  "trigger": "!schedule",
  "reply": "Streams this week: Tue and Thu 19:00 CET, Sat 16:00 CET.",
  "level": "Everyone",
  "response_type": "say",
  "enabled": true
}
```

### update_timer

Change the messages, online interval, chat lines or on/off state of a chat timer. Access: write, asks the user first. REST: `PATCH /api/v1/streamelements/timers/{timer_id}`. MCP: `streamelements_write → update_timer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `timer_id` | string | yes | Timer ID from list_timers. |
| `messages` | array | no | New list of messages the timer cycles through. |
| `online_interval_minutes` | integer | no | Minutes between posts while the stream is live. |
| `chat_lines` | integer | no | Least chat messages in the last 5 minutes before the timer posts. |
| `enabled` | boolean | no | false turns the timer off. |

Changes only the fields you send. Messages replaces the whole list, and the timer cycles through it. A timer that is on posts in your chat while you are live, so viewers see it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "timer_id": "t_20c7aa",
  "name": "Charity stream",
  "messages": [
    "Charity stream on Saturday! Details in !schedule"
  ],
  "online_interval_minutes": 15,
  "chat_lines": 5,
  "enabled": false
}
```

### update_store_item

Change the name, description, cost, quantity, cooldowns or on/off state of a Stream Store item. Access: write, asks the user first. REST: `PATCH /api/v1/streamelements/items/{item_id}/store-item`. MCP: `streamelements_write → update_store_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Item ID from list_store_items. |
| `name` | string | no | New item name. Viewers type it after !redeem, and it is case-sensitive. |
| `description` | string | no | New description. |
| `cost` | integer | no | Cost in loyalty points. |
| `quantity` | integer | no | How many can be redeemed. |
| `cooldown_global` | integer | no | Seconds between any two redemptions. |
| `cooldown_user` | integer | no | Seconds the same viewer must wait. |
| `enabled` | boolean | no | false hides the item from redemption. |

Changes only the fields you send and returns the item as saved. A new cost applies to the next redemption, so viewers pay it in loyalty points. Item content such as the sound file or video is not changed by this tool. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "item_id": "i_5c0bb2",
  "name": "Sound: Air Horn",
  "type": "Sound Effect",
  "cost": 150,
  "quantity": "unlimited",
  "cooldown": {
    "global": 0,
    "user": 300
  },
  "enabled": true
}
```

### resolve_redemption

Approve or decline a store redemption that waits for your decision. Access: write, asks the user first. REST: `POST /api/v1/streamelements/redemptions/{redemption_id}/resolve`. MCP: `streamelements_write → resolve_redemption`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `redemption_id` | string | yes | Redemption ID from list_redemptions. |
| `action` | enum | yes | approve or decline. |

Approves or declines one redemption, as the buttons on the Redemptions page do. Which items wait for a decision follows your Stream Store settings. The viewer sees the result. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "redemption_id": "rd_91a0f3",
  "item": "Pick my next game",
  "viewer": "luka_dev",
  "status": "approved"
}
```

### adjust_points

Add loyalty points to a viewer, or take points away with a negative amount. Access: write, asks the user first. REST: `POST /api/v1/streamelements/points/adjust`. MCP: `streamelements_write → adjust_points`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `username` | string | yes | Viewer username, as on the leaderboard. |
| `amount` | integer | yes | Points to add. Negative removes points. |

Adds the amount to the viewer's current balance, like Give Points on the Leaderboard tab, and returns the new balance. A negative amount removes points. A viewer can hold at most 2,147,483,647 points. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "username": "mika_r",
  "added": 500,
  "points": 2340
}
```

### remove_song_request

Remove one song from the Media Request queue. Access: write, asks the user first. REST: `DELETE /api/v1/streamelements/songs/{song_id}/request`. MCP: `streamelements_write → remove_song_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `song_id` | string | yes | Song ID from list_song_requests. |

Removes one song from the queue. The viewer who asked for it sees it gone, and re-adding it takes a new request. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "song_id": "sg_8d210e",
  "removed": true
}
```

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

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

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

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

```
Every Monday, update !schedule with this week's stream times and point !socials at my new link. Show me the old and new reply for each command, and create any command that is missing.
```

### Call StreamElements 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/streamelements 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/streamelements/commands \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"trigger":"!discord","reply":"Join us on Discord: discord.example/lab","level":"Everyone"}'
```

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

```
{
  "command_id": "c_9e41b7",
  "trigger": "!discord",
  "reply": "Join us on Discord: discord.example/lab",
  "level": "Everyone",
  "response_type": "say",
  "enabled": true
}
```

## Why use Cotlet for StreamElements?

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

## Is it safe to connect StreamElements to Cotlet?

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

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

## Is there a StreamElements MCP server on GitHub?

Yes. Community StreamElements MCP servers exist on GitHub, usually maintained by one person. They wrap the REST API: you install one on your own computer, paste in your secret JWT, and fix it yourself when the API or its docs change. Cotlet hosts the same kind of server for you, with no token to copy, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, copy your JWT from the dashboard, add the server to each MCP client | Sign up, sign in to StreamElements once, add one MCP server or API key |
| When StreamElements changes | It breaks until you or the maintainer fix it; the API spec itself leaves some request bodies empty | Our team tests it daily and fixes it for you; failed calls are free |
| Your StreamElements access | A secret JWT in a file on your computer; the docs warn never to share it | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you copy a new token by hand | Your Cloud Browser keeps you signed in; if StreamElements 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 StreamElements 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 StreamElements API cost?

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

**Do I need to be technical?**

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

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

StreamElements offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a developer token or an OAuth app?**

No. Cotlet signs in to your StreamElements account in your Cloud Browser, so you never copy your secret JWT, which the official docs say never to share, and you need no OAuth client. The official API needs one of the two.

**Does it work on a YouTube channel?**

Commands and timers do. The store, giveaways, loyalty points and Media Request are tied to the Loyalty System, which StreamElements says is not available on YouTube accounts, so those tools return nothing there.

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

No. Every call to create_command, update_command, update_timer, update_store_item, resolve_redemption, adjust_points or remove_song_request waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the StreamElements 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/streamelements 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.