MCP server

Bytestream ships a Model Context Protocol (MCP) server at mcp/server.mjs. It is a thin, read-only wrapper over the public catalog API: every tool maps to one op= endpoint, and the same guarantee applies — stream URLs never leave the API. Channels come back with a watch_path that opens the player on bytestream.tv instead.

Connect it

The server speaks JSON-RPC over stdio (newline-delimited or Content-Length-framed — both work). It needs Node 20+ and nothing else; no keys, no database.

Claude Code
Any MCP client (.mcp.json)

claude mcp add bytestream -- node /path/to/atlas/mcp/server.mjs

{
  "mcpServers": {
    "bytestream": {
      "command": "node",
      "args": ["/path/to/atlas/mcp/server.mjs"]
    }
  }
}

By default it talks to production. Point it elsewhere with:

BYTESTREAM_API=http://localhost:3000 node mcp/server.mjs

Tools

Tool	What it answers
`bytestream_search`	Text search over live channels, with country / language / category / region filters
`bytestream_get_channel`	One channel by catalog id, with its `watch_path`
`bytestream_list`	The same filters as search, no text query
`bytestream_categories`	Category keys with channel counts
`bytestream_countries`	Country codes with channel counts
`bytestream_regions`	Continent codes with channel counts
`bytestream_now`	What’s on right now (guide rows), filterable
`bytestream_programmes`	One channel’s schedule with full programme detail, starting from what’s airing
`bytestream_group`	Matching channels grouped by category, country, or region
`bytestream_recommend`	Channels similar to a given channel, ranked by the catalog’s own similarity table
`bytestream_trending`	Channels trending over the last 7 days (watches, likes, and saves, weighted)

Behavior notes

NSFW is hidden unless a tool call passes nsfw: true — the same off-by-default rule as the app.
Channel ids are catalog ids; feed the ids bytestream_search returns into bytestream_get_channel, bytestream_programmes, and bytestream_recommend.
bytestream_trending returns an empty list until signed-in viewers generate watch/like/save signals — see Recommendations for how those flow.
Programme detail is only as rich as the broadcaster published; most fields are absent on most rows, by honesty rather than by bug.

Get started

How it works

Contribute

Connect it

Tools

Behavior notes

​Connect it

​Tools

​Behavior notes

Connect it

Tools

Behavior notes