Tell an AI agent to build you a TV channel

Connect in three minutes

1. Get a key. Create one at my-tv-channel.com/agent-keys/, or in the iOS or macOS app under Profile → Agent Access. Any subscription tier works. The key is shown exactly once, so paste it somewhere safe before you close the page.

2. Add the server. Streamable HTTP, stateless, no session id to track.

Claude Code

claude mcp add --transport http my-tv-channel \
  https://my-tv-channel.com/mcp \
  --header "Authorization: Bearer mytv_sk_YOUR_KEY"

Claude Desktop, or any client using mcpServers JSON

{
  "mcpServers": {
    "my-tv-channel": {
      "type": "http",
      "url": "https://my-tv-channel.com/mcp",
      "headers": {
        "Authorization": "Bearer mytv_sk_YOUR_KEY"
      }
    }
  }
}

Anything else

Plain JSON-RPC 2.0 over HTTP POST. No SDK required:

curl -s -X POST https://my-tv-channel.com/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

initialize and tools/list answer without a key, so a client can inspect the server before credentials are configured. tools/call needs one.

Things to say once it is connected

These work as written. The arrow shows what the agent actually calls.

The 19 tools

Every tool ships MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so a client can decide for itself what to run unattended. “Destructive” here means it changes or removes something you can see — none of it is unrecoverable. Archiving keeps the handle and the videos; deleting a video is a soft delete.

Two things that surprise people

You cannot upload local files over MCP

MCP tool arguments are JSON; there is no multipart channel. import_video_from_url is therefore the ingestion path for an agent, and the video has to be reachable at a direct, public, unauthenticated URL — not a web page, not something behind a login. If your files are on your laptop, upload them through the app and let the agent take it from there.

Weights only air when the schedule is generated

A channel builds its schedule the instant it crosses the launch threshold. Weights set after that are stored but do not change what is on air until a regeneration. Either set each video’s weight as you import it, or call regenerate_schedule when you are done.

No MCP? Drive the REST API

Everything the MCP server does, it does by forwarding to a REST endpoint that already implements it, passing your Authorization header straight through. Auth, ownership, quota and tier gating all live in the REST layer, so the two surfaces cannot drift apart. You can skip MCP entirely.

curl -s -H "Authorization: Bearer $KEY" \
  https://my-tv-channel.com/api/mytvchannel/users/status.php

Written for a machine to read, in rough order of how much you will want them:

• /llms.txt — the short index; start here
• /llms-full.txt — every endpoint, its parameters and its traps, on one page
• /openapi.yaml — OpenAPI 3.1, 23 operations, if your client consumes a schema
• /api/mytvchannel/docs/AGENTS.md — the long-form agent guide, with a worked golden path from nothing to a live channel
• /api/mytvchannel/mcp/README.md — MCP setup and the tool catalogue

Where it is listed

Questions

Further reading

MCP in media, video and streaming: what exists, and the gap nobody has filled — a survey of every MCP server in the media stack as of August 2026, why they all stop at the clip rather than the channel, and the four things that make durable broadcast state harder to hand an agent than a render.

Start with a key

It takes about a minute, and the demo channel is proof the rest works.

Create an API key