Project MCP tools

Project tools choose and inspect the effective project scope for later MCP calls, and can register or delete projects. Most Solo MCP tools resolve against this project.

Tools#

• list_projects — List Solo projects. An optional workspace_id filters to one workspace; omitting it keeps the global list and auto-selects when exactly one project exists.
• select_project — Set the default project scope for later MCP tools.
• get_project — Read metadata for the effective project scope.
• get_project_status — Read project metadata and current processes for the effective project scope.
• get_project_stats — Read CPU and memory usage for the effective project scope.
• create_project — Register or import an existing local directory as a Solo project without opening the app's onboarding UI. Optional name sets the stored project name, and optional workspace_id imports into a specific workspace.
• rename_project — Set or clear the display name for the effective project scope.
• delete_project — Delete the effective Solo project and tear down its Solo-owned state.

Deleting projects#

delete_project has explicit safety rails:

• confirm_delete: true is always required; the call fails without it.
• confirm_stop_running: true is additionally required when the project has running, starting, or stopping processes.
• prompt_template_policy controls what happens to project-scoped prompt templates: delete (the default) removes them, and convert_to_global moves them into the global template pool instead. See Prompt template tools.

Notes#

Use select_project when an external MCP client is not already associated with a Solo project. Solo-managed agents can use the project inferred from their process identity. Use whoami to confirm the effective project scope.

create_project requires a path that already exists on disk. If the canonical path is already registered, Solo returns the existing project and ignores the name and workspace_id parameters.

For organizing projects into workspaces, see Workspace tools.