ConnectionsMCP

Connections

MCP

PzzaCode speaks MCP: connect Claude, Codex, Cursor, Windsurf, Zed or OpenCode and give them real tools for sessions, files, devices and the app window.

Settings · Connections
How to
  1. Open Connections. Find it in Settings.
  2. Allow app control. Turn Allow app window control on if you want agents to control this window - it does not disable session, file or device tools.
  3. Wire a client. Use Add next to a client to write its configuration automatically.
  4. Remote machines. Copy the configuration into that machine’s MCP settings instead.
Model Context Protocol

PzzaCode runs a local MCP server so agents can work with the same things you see in the app. Once a client is wired in, its agent can list and open sessions, read and write files over the same connection the terminal uses, inspect devices and ports, and - only if you allow it - drive the app window itself.

What the server exposes

The toolset is grouped by what it touches. These are the real tool names your agent sees:

Sessions
list_sessions, list_windows, scan_device, session_path, create_session (optionally bound to a Claude or Codex account) and kill_session.
Devices
device_info, device_ports, ssh_hosts, capabilities, doctor and install_agent - the last one installs the agent on another machine over SSH you already have access to.
Ports & forwarding
list_ports, forwarding_status and set_forwarding - so an agent can see what is listening and turn forwarding on or off.
Accounts & spend
list_accounts, get_usage (5-hour and weekly windows per account) and get_spend (today, yesterday, trailing window).
Files
list_dir, read_file and write_file - scoped to the home tree, over the session’s connection.
Git protection
git_protect, git_commit and git_create_pull_request - commits and PRs only go through after the same secret scan the app uses.
App window (opt-in)
app_list_clients plus the UI commands behind it - create sessions, drive terminals, use the editor, manage workspaces and notifications. Every UI command requires an explicit client ID, and the whole group stays off until you allow it.
Security model

The server talks to the device agent over its loopback API, so nothing is exposed to the network. File tools refuse SSH, GPG and cloud keys as well as agent credential files, and they cannot leave the home tree. App window control is a separate, explicit switch - agents only touch the UI when you turn it on.

Client setup

Add writes the entry into a supported client for you; the copy button hands you the same configuration for a machine that is not the current one. The installed entry points at ~/.config/pzza/mcp.json, which is the file the app registers.

After changing the config, restart the client so it picks up the new server. The same panel shows the server path and each framework it has been installed into, so you can confirm what is wired up.

Was this page helpful?