Connect Kirocast to the agent I am using now, so you can help me record and edit product videos on my Mac.

I authorize adding or updating only the local Kirocast MCP entry for this agent. Back up the existing configuration first and preserve all other settings and MCP servers. Do not configure other agents.

Read the current instructions:
- https://kirocast.com/manual/connect-your-agent
- https://kirocast.com/manual/other-mcp-clients
- https://kirocast.com/manual/agent-access
- https://kirocast.com/manual/mcp-tools
- https://kirocast.com/manual/narration

1. Check that this Mac has Apple silicon (uname -m prints arm64) and runs macOS 15 or later, and identify the agent you are running in. Kirocast is a native Mac app built for Apple silicon; on an Intel Mac, tell me so and stop. A remote or Linux environment cannot capture my Mac through this local MCP connection.
2. Locate Kirocast.app and verify that Contents/MacOS/kirocast-mcp exists and is executable. The usual command is /Applications/Kirocast.app/Contents/MacOS/kirocast-mcp. Use the actual installed path if different. If Kirocast is missing, direct me to https://kirocast.com/download to install the official app, then continue when it is installed. There is no separate Kirocast CLI to download or shell installer to invent.
3. Inspect this agent's current MCP configuration and use its documented format. Add a server named kirocast with the helper's absolute path as its command, with no arguments or API key. For Codex, this is [mcp_servers.kirocast] in ~/.codex/config.toml. Claude Code uses the mcpServers object in ~/.claude.json; Claude Desktop uses ~/Library/Application Support/Claude/claude_desktop_config.json. For other clients, follow their current MCP configuration instructions. If you cannot edit the configuration, explain the specific blocker and guide me through Agent Settings → Set Up Claude, Set Up Codex, or Copy Config.
4. Report the configuration path you changed and whether a new session or client restart is needed. Do not claim a connection is verified until you can call its tools. If only launch_kirocast is available, call it and refresh the tools; if the client cannot refresh, start a new session with Kirocast open.
5. Let me approve Kirocast's first connection prompt myself. Let me grant macOS Screen Recording and, for clicks and typing, Accessibility to the installed copy of Kirocast. Never try to bypass these prompts. Verify with recording_status and report capture and pointer readiness without starting a recording.

Once connected, discover Kirocast's tool schemas rather than guessing arguments. Use its MCP tools for capture, screen input, project editing, captions and export. Kirocast writes local files; it does not host or upload a share link. Export requires a Kirocast license. My existing agent and model handle the reasoning; Kirocast does not provide a model subscription.

For a video task, confirm the target app, steps and intended output if they are missing. Use screenshot to inspect the screen and recording_status to choose the capture target. Leave pace_to_actions on for a walkthrough, but turn it off when capturing continuous animation or loading progress. If I have requested a recording, carry out that request. If I have only requested setup, do not record yet.

After the take, use describe_project and read_rendered_frame to review the edit. Add zooms, focus annotations, privacy masks and captions where appropriate. narrate writes caption lines without sound. For a spoken voice-over, generate_narration reads a script with an ElevenLabs voice on the key I connected in Settings › Voice. It spends my ElevenLabs credits, so it works only after I allow this agent in Settings › AI agents, up to the per-take limit I set; check list_voices first. Make cuts before generating, write the whole script, then call it once. Transcription runs on the Mac; ask before the first speech-model download (about 600 MB) or replacing an existing transcript. Preserve the original and use an editable version. Do not delete projects, overwrite hand edits, submit forms, publish or upload files without my authorization.

Return the actual project and exported file paths, including events and transcript files when available. If export is license-blocked, explain that result and keep the saved project. Never invent a video, a successful export or a share URL.

My task: connect Kirocast, verify the connection without recording, then ask which video I want to make.