Kick Channels, Streams, and Clips MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_kick_channels_streamsA | Read public Kick.com data. For each channel name or link: followers, verified mark, bio, social links, recent categories, and live status, with optional past broadcasts and clips. Also searches channels by word and reads the live directory, most viewers first, filtered by category and language. |
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 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping operations. Its description clearly covers all supported read operations for Kick channels, streams, clips, search, and live directory.
The single tool follows a readable snake_case verb_noun style: get_kick_channels_streams. With only one tool there are no naming inconsistencies across the set.
A single tool is too thin for a server whose apparent scope spans channel lookup, channel search, live directory browsing, past broadcasts, and clips. These could reasonably be separate operations or at least a small set of tools.
The tool covers a broad read-only surface: channel metadata, live status, categories, past broadcasts, clips, search, and directory filtering. Minor gaps may exist around individual clip detail or more granular stream endpoints, but core read workflows appear covered.