Connect your assistant. Keep the approval.
Portlift’s MCP server uses stdio and starts read-only. Your assistant can inspect the library and prepare previews without applying them.
Start with read-only access
Install Portlift, then configure a stdio server in your MCP client. Use the executable path printed by the installer if portlift is not on the client’s PATH.
{
"command": "portlift",
"args": ["mcp"]
}Clients use different configuration wrappers. These are the command and arguments for the Portlift server entry.
Available read-only tools
list_agentsandlist_adapters: inspect the library and platform catalog.scan_agentsandinspect_agent: discover and inspect agents.compare_versions: compare saved snapshots.preview_migrationandpreview_restore: review file changes without applying them.
Enable writes with explicit approval
Change the server arguments to ["mcp", "--allow-writes"] only when you want to permit approval requests.
- The assistant prepares a preview and receives an approval ID.
- Open the same library in Portlift and review the request under Saved Agents.
- Approve or reject that exact request. Approval expires after ten minutes.
- The assistant calls
apply_approved_preview. Each approval can be used once.
A changed file or expired preview requires a fresh request. Keep the MCP server running during the approval flow.
Use the same local library
Configure the same PORTLIFT_DATA_DIR for both processes, or use the arguments below with your actual absolute path:
["--home", "/absolute/path/to/library", "mcp"]Run the dashboard with portlift --home /absolute/path/to/library ui. If a request is missing, check the library path, server session, and expiry.