io.gingerlive/mcp·Marketing

GingerLive

GingerLive livestream ad formats, network reach stats, campaign case studies, and streamer program.

Stars
0
Version
0.3.0
License
MIT
Review
Passed
Language
TypeScript
Last commit
6d ago
Forks
0
Open issues
0
Registry update
Oct 2, 2026
advertisingai-agentscloudflare-workersinfluencer-marketingkicklivestream-advertisingmcpmcp-servermodel-context-protocoltwitch

Connect

remote
Terminal
$claude mcp add --transport http mcp https://mcp.gingerlive.io/mcp

Headers

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 3h ago.

tools
6 tools scanned
metadata
scanned

No findings.

Tools

6
  • get_company_overview

    Returns GingerLive's company profile: what the livestream advertising platform does, supported streaming platforms (Twitch, Kick, YouTube Live, TikTok LIVE), reference clients, 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_stats

    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_formats

    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_studies

    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_study

    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_info

    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.

GingerLive MCP Server

The official Model Context Protocol server for GingerLive, the livestream advertising platform that connects brands with 1,000+ streamers on Twitch, Kick, YouTube Live and TikTok Live.

Connect it to Claude, ChatGPT, Cursor or any MCP client and your assistant can answer questions about livestream advertising using GingerLive's own up-to-date data: ad formats, network reach, campaign case studies and the streamer monetization program.

What it can do

Tools

ToolReturns
get_company_overviewWhat GingerLive is: positioning, streaming platforms, network stats, third-party measurement partners, contact links
get_network_statsNetwork reach and performance: streamer count, annual unique reach, monthly hours watched, ad view-through rate
list_ad_formatsThe livestream ad formats offered to brands, with descriptions and format badges (e.g. unskippable, adblock-safe)
list_case_studiesCampaign case studies, each with a short excerpt and link
get_case_studyThe full write-up of one case study, by slug
get_streamer_program_infoHow streamers join and earn: cost, how it works, supported platforms, sign-up link

Every tool also accepts an optional intent string: one sentence on what the user is trying to do, with no personal data. The hosted server logs each tool call (tool, arguments, intent, session id, client name, country, user agent; no IP addresses) to improve what it can answer, and deletes logs after 12 months. See gingerlive.io/privacy.

Resources

  • gingerlive://company: company facts (JSON)
  • gingerlive://guides: resource guides on livestream advertising (JSON)
  • https://gingerlive.io/llms.txt: the canonical llms.txt, fetched live

Prompts

  • plan_livestream_campaign: scope a livestream ad campaign for a brand (optional goal, budget)
  • get_started_as_streamer: help a streamer evaluate and join the program (optional platform)

Connect

Claude (claude.ai / Desktop): Settings → Connectors → Add custom connector → https://mcp.gingerlive.io/mcp

Claude Code:

claude mcp add --transport http gingerlive https://mcp.gingerlive.io/mcp

Cursor, VS Code and other clients (mcp.json):

{
  "mcpServers": {
    "gingerlive": { "url": "https://mcp.gingerlive.io/mcp" }
  }
}

Run it locally over stdio (same tools, no network needed except the live llms.txt resource):

git clone https://github.com/gingerlive-io/gingerlive-mcp && cd gingerlive-mcp && npm install
{
  "mcpServers": {
    "gingerlive": { "command": "npx", "args": ["tsx", "/path/to/gingerlive-mcp/src/stdio.ts"] }
  }
}

Or with Docker: docker build -t gingerlive-mcp . && docker run -i --rm gingerlive-mcp

Then ask things like "What livestream ad formats does GingerLive offer?", "Show me GingerLive's campaign case studies" or "How can I monetize my Kick stream?"

How it works

Tools, resources and prompts are registered once in src/server.ts and served two ways: src/index.ts (the hosted Cloudflare Worker) and src/stdio.ts (a local stdio process). The Worker is stateless: each request gets a fresh server on the official MCP TypeScript SDK's web-standard Streamable HTTP transport, with no Durable Objects or other per-session storage. Every answer comes from src/data/agent-data.json, a static snapshot generated from the same source as gingerlive.io/llms.txt, so the server only ever returns information that is already public on gingerlive.io.

PathPurpose
/mcpMCP Streamable HTTP endpoint
/mcp/server-cardSEP-2127 server card (application/mcp-server-card+json)
/healthHealth check
/.well-known/mcpSEP-1960 manifest
/.well-known/mcp.jsonRegistry server card

Run it yourself

npm install
npm run stdio    # local stdio server
npm run dev      # local Worker at http://localhost:8787/mcp
npm run deploy   # to your own Cloudflare account (change the route in wrangler.jsonc first)

Usage logging needs a D1 database on your account: npx wrangler d1 create <name>, put its name and id in wrangler.jsonc, then npx wrangler d1 migrations apply <name> --remote. For local dev, apply with --local. The stdio server does not log.

Inspect it with the MCP Inspector:

npx @modelcontextprotocol/inspector

About GingerLive

GingerLive is a livestream advertising platform. Its Streamsense AI places non-intrusive, unskippable ads at the right live moment, so streamers earn from their content and brands reach Gen Z at scale.

License

MIT © Gingerlive Bilişim Teknolojileri A.Ş.

From the server's repository — third-party content, read it before running anything it suggests.

More in Marketing

Listing from the official MCP Registry · repository facts from GitHub, 2d ago.