Connect your agent

Zylcut has an MCP server built in, so any AI agent that supports MCP can use its tools to cut, caption, check and export your videos. Agents connect through a small command Zylcut puts on your computer, zylcut. It starts Zylcut when the agent needs it and handles the access key itself, so nothing you paste holds a key or a password.

There are three ways to connect, from easiest to most hands-on:

One click in Zylcut, for the agents Zylcut knows.
Paste a message into your agent, and it sets itself up.
Set it up by hand, with the exact config for each agent.

One click in Zylcut

Install Zylcut, open it and sign in.
Open Settings (⌘, on macOS, Ctrl+, on Windows and Linux) and go to Agents.
Press Connect next to your agent. Zylcut lists the agents it finds on this computer: Claude Code, Claude Desktop, OpenCode, Codex, Cursor, VS Code, Gemini CLI, Windsurf and Antigravity.
Restart the agent, or reload its window, so it loads Zylcut. Then check that it works.

There is no key to copy. Connecting also copies Zylcut’s editing skills to Claude Code, Codex and OpenCode.

Under each agent’s Connect button, Set Up Manually shows the exact config Connect writes and the file it goes in, with the path on your computer already filled in. Other Agents, at the end of the list, has the message below with your path filled in, for any agent Zylcut does not list.

Paste into your agent

Copy this message into your agent’s chat: Antigravity, Copilot Chat in VS Code (in Agent mode), Cursor, Claude Code or any other agent that can edit files. The agent adds Zylcut to its own MCP settings and tells you how to reload it.

Add the Zylcut MCP server to your own MCP configuration, at user (global) level so it works in every project.

It is a local stdio server:
- name: zylcut
- command: the full path of the zylcut command that the Zylcut app installs:
  - macOS and Linux: ~/.local/bin/zylcut, written out in full, for example /Users/NAME/.local/bin/zylcut on macOS or /home/NAME/.local/bin/zylcut on Linux
  - Windows: %LOCALAPPDATA%\Zylcut\bin\zylcut.cmd, written out in full, for example C:\Users\NAME\AppData\Local\Zylcut\bin\zylcut.cmd
- args: ["mcp"]

First check that this file exists. If it does not, stop and tell me to open the Zylcut app once, since the app creates the command when it starts.
It needs no URL, environment variables or API key: the command authenticates with the Zylcut app on this computer itself, and starts the app if it is not running.
Write the full path, not ~ or a bare zylcut: apps started from the Dock or Start menu may not have that folder on PATH, and most MCP configs do not expand ~.
Keep every other server and setting in the file as it is.

Then tell me which file you changed and how to reload you so the server loads. After the reload, call the zylcut whoami tool to check the connection.

Where the zylcut command is

Every config on this page runs the same command, with the argument mcp:

System	Command
macOS	`/Users/YOU/.local/bin/zylcut`
Linux	`/home/YOU/.local/bin/zylcut`
Windows	`C:\Users\YOU\AppData\Local\Zylcut\bin\zylcut.cmd`

YOU is your user name on the computer. Zylcut writes this file each time it starts, pointing at the app you installed, so it stays right after an update or a move.

Configs use the full path, never a bare zylcut: an app you open from the Dock, the Start menu or a launcher does not read your terminal’s PATH, so it would not find the command. In the snippets below, replace YOU with your user name, or copy the snippet from Zylcut’s Settings > Agents > Set Up Manually, where it is already filled in. The terminal commands use ~ or $env:LOCALAPPDATA, which your shell fills in.

Set up each agent by hand

Add the zylcut entry next to any servers already in the file, keep the rest as it is, save, and restart the agent.

Antigravity

Antigravity reads its MCP servers from mcp_config.json in .gemini/config in your home folder. To open it from Antigravity, open the … menu at the top of the agent panel, choose MCP Servers, then Manage MCP Servers, then View raw config.

{
  "mcpServers": {
    "zylcut": {
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "/home/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

Or add it with the Antigravity CLI, agy:

agy mcp add zylcut ~/.local/bin/zylcut mcp

agy mcp add zylcut "$env:LOCALAPPDATA\Zylcut\bin\zylcut.cmd" mcp

agy mcp add zylcut ~/.local/bin/zylcut mcp

Restart Antigravity. agy mcp list shows the server.

VS Code with GitHub Copilot

Copilot’s Agent mode uses the MCP servers in your user mcp.json. To open it, run MCP: Open User Configuration from the Command Palette (⇧⌘P on macOS, Ctrl+Shift+P on Windows and Linux). VS Code’s list of servers is called servers, and each needs "type": "stdio".

{
  "servers": {
    "zylcut": {
      "type": "stdio",
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

{
  "servers": {
    "zylcut": {
      "type": "stdio",
      "command": "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"]
    }
  }
}

{
  "servers": {
    "zylcut": {
      "type": "stdio",
      "command": "/home/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

On macOS and Linux you can add it from a terminal instead; the shell fills in your home folder:

code --add-mcp "{\"name\":\"zylcut\",\"type\":\"stdio\",\"command\":\"$HOME/.local/bin/zylcut\",\"args\":[\"mcp\"]}"

Then open Copilot Chat, switch it to Agent, and open the tools button: Zylcut’s tools are listed under zylcut. If VS Code shows the server as stopped, choose Start above its entry in mcp.json.

Cursor

Cursor reads ~/.cursor/mcp.json. To open it, go to Cursor Settings > MCP and add a new global MCP server. Cursor fills in ${userHome} itself, so this snippet works as it is, with no user name to replace:

{
  "mcpServers": {
    "zylcut": {
      "command": "${userHome}/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "${userHome}\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "${userHome}/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

Save the file; Cursor shows zylcut in its MCP list with a green dot when it is running.

Claude Code

Run this in a terminal. --scope user makes Zylcut available in every folder:

claude mcp add --scope user zylcut -- ~/.local/bin/zylcut mcp

claude mcp add --scope user zylcut "$env:LOCALAPPDATA\Zylcut\bin\zylcut.cmd" mcp

claude mcp add --scope user zylcut -- ~/.local/bin/zylcut mcp

claude mcp list should then show zylcut: ... - ✔ Connected. In a running session, /mcp lists it.

Claude Desktop

Open Settings > Developer > Edit Config in Claude Desktop, which opens claude_desktop_config.json:

{
  "mcpServers": {
    "zylcut": {
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "/home/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

Quit Claude Desktop completely (not just its window) and open it again.

Codex

Codex keeps its servers in config.toml in .codex in your home folder. The CLI, the Codex app and its IDE extension all read it. tool_timeout_sec gives long tools, such as an export, up to 15 minutes:

[mcp_servers.zylcut]
command = "/Users/YOU/.local/bin/zylcut"
args = ["mcp"]
tool_timeout_sec = 900

[mcp_servers.zylcut]
command = "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd"
args = ["mcp"]
tool_timeout_sec = 900

[mcp_servers.zylcut]
command = "/home/YOU/.local/bin/zylcut"
args = ["mcp"]
tool_timeout_sec = 900

Or add it from a terminal with codex mcp add zylcut ~/.local/bin/zylcut mcp (on Windows, codex mcp add zylcut "$env:LOCALAPPDATA\Zylcut\bin\zylcut.cmd" mcp), then add the tool_timeout_sec line to the table it writes. codex mcp list shows the server.

Gemini CLI

Gemini CLI reads settings.json in .gemini in your home folder:

{
  "mcpServers": {
    "zylcut": {
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"],
      "timeout": 900000
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"],
      "timeout": 900000
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "/home/YOU/.local/bin/zylcut",
      "args": ["mcp"],
      "timeout": 900000
    }
  }
}

Or run gemini mcp add -s user zylcut ~/.local/bin/zylcut mcp. In a session, /mcp lists the server.

Windsurf

Open Cascade’s MCP menu (the hammer icon) and choose to configure or open the MCP config file. If it opens a different file from the one below, paste the entry there:

{
  "mcpServers": {
    "zylcut": {
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd",
      "args": ["mcp"]
    }
  }
}

{
  "mcpServers": {
    "zylcut": {
      "command": "/home/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

Then press refresh in Cascade’s MCP panel.

OpenCode

OpenCode 2 keeps local servers under mcp.servers, each with its command and arguments in one list:

{
  "mcp": {
    "servers": {
      "zylcut": {
        "type": "local",
        "command": ["/Users/YOU/.local/bin/zylcut", "mcp"],
        "timeout": 900000
      }
    }
  }
}

{
  "mcp": {
    "servers": {
      "zylcut": {
        "type": "local",
        "command": ["C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd", "mcp"],
        "timeout": 900000
      }
    }
  }
}

{
  "mcp": {
    "servers": {
      "zylcut": {
        "type": "local",
        "command": ["/home/YOU/.local/bin/zylcut", "mcp"],
        "timeout": 900000
      }
    }
  }
}

Or run opencode mcp add --global zylcut -- ~/.local/bin/zylcut mcp. If the file is opencode.jsonc, use that one.

Other agents

Most other MCP clients take the same entry as Claude Desktop: a name, a command and its args. The list may be called mcpServers, servers or mcp, so put the entry where the client’s other servers are, or paste the message into the agent and let it work that out.

{
  "mcpServers": {
    "zylcut": {
      "command": "/Users/YOU/.local/bin/zylcut",
      "args": ["mcp"]
    }
  }
}

Use the path for your system from the table above.

Clients that only connect over HTTP

Zylcut also serves MCP over Streamable HTTP at http://127.0.0.1:3290/mcp, on your computer only. Every request must send the header Authorization: Bearer <key>, with the key from the mcp-token file in Zylcut’s data folder:

System	Key file
macOS	`~/Library/Application Support/Zylcut/mcp-token`
Windows	`%APPDATA%\Zylcut\mcp-token`
Linux	`~/.config/Zylcut/mcp-token`

Settings > Agents > Other Agents shows the address and the key file. Treat the key like a password: anything that has it can drive Zylcut, so keep it out of shared or synced files, and use the zylcut command instead whenever the client can run a command. To change the key, quit Zylcut, delete the file and open Zylcut again (it makes a new key), then update the client.

Check that it works

Restart the agent so it loads the new server. In VS Code, run Developer: Reload Window; quit and reopen Antigravity, Cursor, Windsurf and Claude Desktop; start a new session in a terminal agent.
Ask the agent: “Call the zylcut whoami tool.” It answers with your Zylcut account, the app’s version and your projects folder. “List my Zylcut projects” works too.
In a terminal, claude mcp list, codex mcp list, gemini mcp list and agy mcp list show the server.

Sign-in and keys

No key in your config. The zylcut command reads the key Zylcut keeps on your computer each time it connects, so the configs on this page hold no key or token, and there is nothing to leak.
Sign in to Zylcut. The tools need you signed in to Zylcut with a free zylcut.com account. If whoami shows "user": null and "access": "signed-out", or another tool says an account is needed, open Zylcut and sign in (Settings > Account). It is free, with no card.
Only on your computer. The server listens on 127.0.0.1, so nothing outside your computer can reach it.

Troubleshooting

The agent does not list Zylcut

Restart the agent completely, not just the chat.
Make sure you edited the file the agent reads: open it from the agent’s own menu, as described in its section above. For Antigravity that is ~/.gemini/config/mcp_config.json.
Check that the file is valid JSON (or TOML for Codex): one outer { }, the zylcut entry inside the existing list of servers, commas between entries, and no comma after the last one.

“command not found”, ENOENT or the server fails to start

The command must be a full path to a file that exists. Check it: on macOS and Linux run ls -l ~/.local/bin/zylcut; on Windows run Test-Path "$env:LOCALAPPDATA\Zylcut\bin\zylcut.cmd" in PowerShell.
If the file is missing, Zylcut is not installed or has never been opened. Install it and open it once, or press Connect for any agent in Settings > Agents.
Never use a bare zylcut or a path starting with ~ in a config file: most agents do not expand them.

Zylcut was moved, updated or reinstalled

The zylcut command points at the app you installed, and Zylcut rewrites it every time it starts. After moving or reinstalling the app (or with a new AppImage on Linux), open Zylcut once and restart the agent.

Windows paths

Inside JSON and TOML strings every backslash is doubled: "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd".
Keep the whole path in one string, even when your user name has a space in it.
If an agent cannot start a .cmd file, have Windows’ command prompt start it: set "command": "cmd" and "args": ["/c", "C:\\Users\\YOU\\AppData\\Local\\Zylcut\\bin\\zylcut.cmd", "mcp"].

The tools say an account is needed

Open Zylcut and sign in with your free zylcut.com account. See Sign-in and keys.

Zylcut refused the key

Another copy of Zylcut, running with a different profile, is using the port. Quit the other copy and try again.

Still stuck

Use Help > Report a Problem… in Zylcut, or write to support@zylcut.com.