MCP prompts and resources

Beyond tools, Solo's MCP server exposes built-in prompts and readable resources. Prompts are short playbooks a client can pull into a conversation, and resources make scratchpads and todos readable as regular MCP resources.

Prompts

Clients discover prompts with the standard prompts/list and prompts/get requests. Solo ships three orchestration playbooks:

  • worker_bootstrap — Start a Solo worker session with durable coordination. Walks through checking identity with whoami, taking locks before shared edits, using key-value storage, scratchpads, and todos for durable state, and preferring wait_for_bound_port and timer tools over polling.
  • wait_for_bound_port — Wait for a Solo-managed process to expose a bound port. Covers calling wait_for_bound_port with a process_id or process_name, bounding the wait with timeout_ms, and reading the returned port snapshot.
  • timer_followup — Handle timer wake-ups delivered through the agent conversation. Covers reading the injected timer body, doing the follow-up task, checking shared coordination state, and cancelling timers that are no longer relevant.

Each prompt returns a single user message containing the playbook text. Agents that cannot browse prompts directly can ask for similar guidance with the help tool; see Setup and support tools.

Resources

When the scratchpad or todo feature tools are enabled, Solo lists project scratchpads and todos as MCP resources. Clients read them with the standard resources/list and resources/read requests. Resource URIs follow these templates:

solo://proj/{project_id}/scratchpad/{slug}--{scratchpad_id}
solo://proj/{project_id}/todo/{slug}--{todo_id}
  • Scratchpad resources return the scratchpad's Markdown content.
  • Todo resources return the todo rendered as Markdown, including its comments.
  • Resource listing is paginated with a cursor and skips archived scratchpads.
  • Scratchpad resources appear only when scratchpad tools are enabled, and todo resources only when todo tools are enabled.

Solo also advertises the scratchpad URI pattern as an MCP resource template when scratchpad tools are enabled, and advertises the todo URI pattern as a resource template when todo tools are enabled. Clients that support templates can construct a URI directly from a project ID and a scratchpad or todo ID. The same URIs double as Solo deep links; see Deep links.

Notes

Resources are read-only. To create or change scratchpads and todos, use the Scratchpad tools and Todo tools.

Are you an agent? Read this doc via API: /api/v1/docs/mcp-tools/prompts-and-resources