ZIVO in AI assistants
ZIVO runs a remote MCP server, so an AI assistant can ask ZIVO where a game is on and get the same sourced answer the site gives, rather than an answer the model made up.
By ZIVO Sports · Last updated October 10, 2026
The server
ZIVO's MCP server lives at https://www.zivosports.tv/api/mcp. It speaks the Model Context Protocol over streamable HTTP, so any assistant that supports remote MCP servers can connect to it. There's nothing to install.
You can use it without an account. Searching games and getting watch options are public. Signing in to ZIVO through the assistant adds your saved teams, services, country, and spoiler setting, and lets the assistant set reminders you ask for.
What an assistant can do with it
The server exposes five tools:
- Find games by team, league, live status, and a time window in your time zone. Public.
- Get watch options for a game: the sourced routes, the region each applies to, how confident ZIVO is, and where the answer is uncertain. Public. Pass a country for a regional answer.
- Get game context, with scores and other spoilers removed when your spoiler setting is on. Requires sign-in.
- Read your saved teams, services, spoiler setting, and country. Requires sign-in.
- Set a reminder for a game, only when you ask for one. Requires sign-in.
Connect from Claude
In Claude, open Settings, then Connectors, and add a custom connector with the URL https://www.zivosports.tv/api/mcp. Claude can use the public tools right away. Choose Connect, or ask for something that needs your account, to sign in to ZIVO and approve access.
In Claude Code, run: claude mcp add --transport http zivo https://www.zivosports.tv/api/mcp
Connect from ChatGPT
In ChatGPT's settings, add a custom app (connector) with the same URL, https://www.zivosports.tv/api/mcp. Depending on your plan, ChatGPT may ask you to turn on developer mode before you can add a custom app. Choose Connect to sign in to ZIVO when you want your preferences and reminders available.
Other MCP clients
Any client that supports remote MCP servers can use the same URL. Signing in uses OAuth 2.1 with dynamic client registration and PKCE, so the client doesn't need a client ID, secret, or custom header.
What signing in shares
When you connect your ZIVO account, ZIVO shows the permissions the assistant is asking for and you approve or deny them: reading spoiler-aware game details, reading your saved preferences, and creating reminders you ask for. The assistant can't change your other settings or see your password.
A service you've saved in ZIVO only means you told ZIVO you use it. ZIVO never tells the assistant that you're subscribed to a service, because it can't know that. You can disconnect ZIVO at any time from your assistant's connector settings.
ZIVO receives only the inputs the assistant sends for each tool call, such as a team search or a game, and logs those calls for analytics. It never receives the rest of your conversation. What the assistant does with ZIVO's answers is governed by that assistant's own privacy policy; ZIVO's handling of your data is described in the privacy policy.
What stays the same
The assistant gets the same answer the site shows. Availability is still resolved at country level, a route that depends on a finer market is still labeled market-dependent, and ZIVO still doesn't host or stream video. The server tells assistants to treat ZIVO's results as the source of truth and never to invent availability, scores, or links.