GingerLive MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_company_overviewA | Returns GingerLive's company profile: what the livestream advertising platform does, supported streaming platforms (Twitch, Kick, YouTube Live, TikTok LIVE), headline network stats, third-party measurement partners and contact links. Use first for general "what is GingerLive" questions; use get_network_stats for just the reach numbers, list_ad_formats for formats, get_streamer_program_info for the creator side. Read-only; data is a static snapshot of gingerlive.io's public facts. |
| get_network_statsA | Returns GingerLive's network reach and performance figures: streamer count, annual unique reach, monthly hours of livestreams watched and ad view-through rate. Use when a user asks about scale or performance benchmarks; use list_case_studies for campaign-specific results. Read-only; figures are GingerLive's published network numbers. |
| list_ad_formatsA | Lists the livestream ad formats GingerLive sells to brands (e.g. picture-in-picture, banners, rich media, pinned chat drops, streamer announcements), each with a short description, plus format badges such as unskippable and adblock-safe. Use when planning or comparing ad formats; use get_company_overview for the company itself. Read-only. |
| list_case_studiesA | Lists GingerLive campaign case studies with slug, title, short excerpt and URL. Use to find proof points or results for a brand, category or format, then call get_case_study with a slug for the full write-up. Read-only. |
| get_case_studyA | Returns one GingerLive campaign case study: title, date, URL and the full markdown write-up (brand, approach and results). Requires a slug from list_case_studies; an unknown slug returns the list of valid slugs. Read-only. |
| get_streamer_program_infoA | Returns how livestreamers join and earn with GingerLive: cost (free for streamers), how the in-stream ad program works, supported platforms and the sign-up link. Use for creator or streamer monetization questions; for brand-side questions use get_company_overview or list_ad_formats instead. Read-only; public program information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_livestream_campaign | Guide the assistant to scope a GingerLive livestream advertising campaign for a brand, using this server's tools. |
| get_started_as_streamer | Guide the assistant to help a livestreamer evaluate and join GingerLive's monetization program. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| company | |
| guides | |
| llms-txt |
TDQS
Scored across 6 tools
Each tool targets a distinct resource: company profile, network stats, ad formats, case study list/retrieval, and streamer program. Descriptions explicitly cross-reference alternatives to prevent overlap. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern (get_*, list_*), with clear and predictable naming. No mixing of conventions.
Six tools is well-scoped for a static informational server about a single company. Each tool covers a distinct information need without redundancy.
The surface covers the full public information surface: company overview, stats, ad formats, case studies (list + detail), and streamer program. All tools are read-only by design as a static snapshot, so no create/update/delete operations are expected or missing.