MCP Server

MCP Server

Zegplayer ships a read-only Model Context Protocol server that lets your AI agents query your video transcripts and notes — without exposing local file paths and without the ability to modify anything.

Connecting

1. Pick your AI agent in the app (claude, codex, or opencode).
2. Click Connect MCP.

That registers the server with your chosen agent:

• claude / codex → via their mcp add CLI (server name zegplayer).
• opencode → written directly into ~/.config/opencode/opencode.jsonc under mcp.zegplayer.

The agent launches the bundled server (dist-mcp/server.js in a packaged build, run through Node) and can then read your data.

What the agent can do

The server runs read-only by default. Tools like list_projects return your videos and notes without leaking absolute file paths. Write tools exist but are gated behind an authoring profile and refuse to run unless explicitly enabled.

Environment contract

The main process passes the server its configuration via environment variables (renamed in the rebrand):

Variable	Purpose
ZEGPLAYER_DATA_DIR	Path to the SQLite data directory the server should read
ZEGPLAYER_MCP_PROFILE	read-only (default) or authoring
ZEGPLAYER_EXPORT_DIR	Approved export destination (authoring only)

If ZEGPLAYER_DATA_DIR is unset, the server falls back to the platform data directory (…/Zegplayer/).

Packaging note

The MCP server and its native dependencies are asarUnpack-ed (better-sqlite3, bindings, file-uri-to-path, dist-mcp). Missing any of these transitive native deps causes a packaged "Failed to connect" — they must all be unpacked.