streamelements-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for tool calls; without it a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
StreamElements through Cotlet.dev. Call streamelements_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| streamelements_guideA | How to work in StreamElements (list and edit chat commands): its screens and the sign-in link. Call this first. |
| streamelements_statusB | Check that your Cotlet.dev account and StreamElements are ready: account, credits and StreamElements connection. |
| streamelements_openB | Open a StreamElements page in your signed-in Cloud Browser (default https://streamelements.com) to work with list and edit chat commands. |
| streamelements_readB | Read the current StreamElements page: its text and numbered buttons, links and fields. |
| streamelements_clickC | Click a numbered element on the current StreamElements page. |
| streamelements_typeB | Type text into a numbered field on the current StreamElements page. |
| streamelements_closeA | Close the StreamElements browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct browser-automation action: open, read, click, type, close, plus guide and status. The boundaries between guide (instructions) and status (readiness check) are clear enough, though both are meta-tools that could initially be confused. Open versus read is also distinguishable because one navigates and the other extracts content.
All tools follow the same streamelements_<verb> snake_case pattern. The prefix is consistent and the verbs are simple and readable. There is no mixing of camelCase or conflicting conventions.
Seven tools is a well-scoped set for a browser-automation workflow focused on StreamElements chat-command management. Each tool has a clear role, and none appears redundant or purely decorative.
The surface covers the core lifecycle: sign-in guidance, readiness check, opening a page, reading it, interacting via click and type, and closing the session. Minor gaps exist around navigation history or waiting for dynamic updates, but the essential list-and-edit workflow is covered.