Your catalog. Inside every AI agent.
Arlo's MCP server lets Claude, ChatGPT, Cursor, Siri, and any MCP-aware assistant query your library directly — using the open protocol Anthropic published and the industry adopted in 2024. No custom plugin. No middleware. One endpoint — https://api.arlotv.ai/mcp/v1 — authenticated with your API key.
The USB-C port for AI agents.
Model Context Protocol (MCP) is an open standard that lets AI models read from external data sources in real time. Before MCP, every AI app needed bespoke integration code for every data source — a quadratic mess. After MCP, any agent can connect to any MCP server and discover what it can do.
Arlo runs as an MCP server. Your catalog — every title, every vibe vector, every availability link — is exposed as a structured tool surface. When a user asks Claude "what's a quiet Sunday-morning documentary?", Claude can call Arlo's recommend_for_mood tool, read your titles back, and return them in its answer.
Three minutes from key to first answer.
headers block is required — put your X-API-Key there; requests without a key are rejected.{
"mcpServers": {
"arlo": {
"url": "https://api.arlotv.ai/mcp/v1",
"headers": { "X-API-Key": "YOUR_API_KEY" }
}
}
}https://api.arlotv.ai/mcp/v1, transport Streamable HTTP, and an X-API-Key header. ChatGPT and other MCP-aware hosts work the same way — point them at the endpoint.mcp SDK (Python / TypeScript) with Streamable HTTP. Quick liveness check below; actual tool calls need the MCP handshake, which clients do automatically. (Legacy SSE clients only: https://api.arlotv.ai/sse.)curl https://api.arlotv.ai/mcp/health
# → {"status":"ok"}What agents can do.
Every Arlo MCP server exposes the same set of tools, scoped to whatever the API key has access to. No undocumented endpoints — every tool is discoverable via standard MCP introspection. The friendly names below are live aliases; each maps to a canonical tool name (shown beneath) that works identically.
What it looks like.
End-user prompt to an AI agent. The agent invokes Arlo's MCP server behind the scenes; the user sees only the answer.
Your catalog needs a key.
Anything that touches your catalog authenticates with the X-API-Key header (or Authorization: Bearer) tied to your organization. Your key scopes every tool to your catalog and meters usage on your org:
Arlo also runs a free, keyless tier for public discovery— what to watch, where to watch it, what's popular, what's coming. It is neutral and cross-service, it never reaches a partner catalog, and it is how an assistant cites Arlo without anyone signing up. Connect it in a minute →
Over-limit calls return 429 with a Retry-After header; X-RateLimit-* headers ride on every response.