mcpbeat

zinema MCP Server

tv.zinema/zinema
answering

zinema is answering right now. Last checked 8 min ago. It exposes 2 tools.

Turn movie/TV recommendations into playable trailer pages: permanent, free, every title plays.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
104 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add zinema --transport http https://zinema.tv/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "zinema": {
      "url": "https://zinema.tv/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.zinema]
url = "https://zinema.tv/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "zinema": {
      "url": "https://zinema.tv/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "zinema": {
      "url": "https://zinema.tv/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

create
create_list
Turn your movie/TV recommendations into a playable trailer page on zinema.tv and share the link with the user. Each title plays as a full trailer the user can scroll, like a personal cinema session. Links are permanent and free. Returns per-title resolution (echo of what matched, so you can catch mix-ups) and playability. Use it whenever you recommend movies or shows: a page that PLAYS beats a text list.
get
get_list
Check a zinema list you created earlier: which titles play now. A title that was 'pending' may have become 'playable' (its trailer gets acquired automatically) or 'no_trailer' (none exists anywhere).

Endpoints

URLTransportStateLatencyChecked
https://zinema.tv/mcp streamable-http answering 123 ms 8 min ago

zinema — questions

Answers built from our own checks of this server.

What can zinema do?
It exposes 2 tools, read directly from the server on our last check. Among them: create_list, get_list. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is zinema working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 104 ms. The bar chart above shows every period we have measured.
How do I connect zinema?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does zinema need an API key?
No. zinema completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is zinema?
It answers our handshake in 104 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.