Creators & communities
Substack
Posts, Notes, messages, subscribers and stats for your publication.
50 endpoints
StreamElements's API covers commands, timers, tips and points, but it takes a secret JWT or OAuth client and code you write and host. Sign in to StreamElements once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with StreamElements.
| What you need | StreamElements's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Use without an API key or code | No | Partly | Yes, 14 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when StreamElements changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 17, 2026. Sources: StreamElements developers: API Reference · StreamElements API docs (OpenAPI spec, GitHub) · StreamElements API docs: Personal Access with a JWT · StreamElements Documentation: Developers
AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.
Add Cotlet to your agent once. StreamElements and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/streamelements with its own method and path, such as POST /api/v1/streamelements/commands, with the same API key. Our open-source repo has ready scripts to start from.
14 tools on your own StreamElements account. Agents call them as operations of the MCP tools streamelements_read and streamelements_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_commands | Chat commands of your channel with reply, aliases, level, cooldowns, cost and whether they are on. | read |
| list_timers | Chat timers with their messages, online interval, chat lines and whether they are on. | read |
| list_store_items | Stream Store items with type, cost in points, quantity, cooldowns and whether they are on. | read |
| list_redemptions | Store redemptions with item, viewer, cost and what the viewer filled in on the Requirements page. | read |
| list_tips | Tips your channel received, with amount, currency, tipper, message and time. Read only. | read |
| get_points_leaderboard | Viewers ranked by loyalty points or watch time, with each balance. | read |
| list_song_requests | The Media Request queue: song, who asked, length and whether it was tipped. | read |
| create_command | Add a chat command with a reply, who may use it, cooldowns and response type. | writeasks first |
| update_command | Change the reply, level, cooldowns, cost, response type or on/off state of a command. | writeasks first |
| update_timer | Change the messages, online interval, chat lines or on/off state of a chat timer. | writeasks first |
| update_store_item | Change the name, description, cost, quantity, cooldowns or on/off state of a Stream Store item. | writeasks first |
| resolve_redemption | Approve or decline a store redemption that waits for your decision. | writeasks first |
| adjust_points | Add loyalty points to a viewer, or take points away with a negative amount. | writeasks first |
| remove_song_request | Remove one song from the Media Request queue. | writeasks first |
Scroll the table for all 14 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while StreamElements is enabled for agents, so 20 calls a day come to 550 credits.
| 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.
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.
Sign up free, open StreamElements under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to StreamElements yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so StreamElements sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: create_command, update_command, update_timer, update_store_item, resolve_redemption, adjust_points, remove_song_request wait for your OK by default. You can switch that off per tool for scheduled runs.
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.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when StreamElements changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
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.
No. Cotlet is independent and not affiliated with StreamElements.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy