Process MCP tools

Process tools control Solo-managed process entries: commands, terminals, agents, and stopped entries.

Tools#

• list_processes — List process entries in the effective project scope, including commands, terminals, agents, and stopped entries.
• get_process_status — Read detailed status for one process.
• rename_process — Rename a process in the Solo UI.
• select_process — Select a process in the Solo UI so its terminal surface is attached and rendered.
• start_process — Start one existing Solo process entry. This can start a stored command, terminal, or agent. Use spawn_process(kind="terminal") to create a new terminal. Prefer spawn_agent to create a new agent; spawn_process(kind="agent") remains the generic fallback. Only command processes must be trusted in the Solo UI before MCP can start them.
• stop_process — Gracefully stop one running process.
• restart_process — Restart one existing Solo process entry. This can restart a stored command, terminal, or agent. Use spawn_process(kind="terminal") to create a new terminal. Prefer spawn_agent to create a new agent; spawn_process(kind="agent") remains the generic fallback. Only command processes must be trusted in the Solo UI before MCP can restart them.
• send_input — Send terminal text or raw control bytes to a running process. Optional wait_ms can return the rendered tail in the same response.
• close_process — Remove one stored Solo terminal or Solo agent from the project. Use stop_process or restart_process for command processes.

Notes#

Command trust still matters. MCP can start or restart trusted command processes, but untrusted command entries must be reviewed in the Solo UI first.

If close_process targets the MCP caller's own Solo process, pass confirm_self_close: true only when the user explicitly asked that process to close itself.

For a new process, use spawn_process(kind="terminal") for a terminal or prefer spawn_agent for an agent. The generic spawn_process(kind="agent") path remains available. See Agent and terminal tools.