CIEL Lab MCP App Phase 1: Read and create worklists

[filiperochalopes]

User story

As an MCP App user, I want to review concept results and create worklists from the browser app so I can turn search results into curated worklists.

Use case

A user opens the MCP App, reviews a concept preview, selects the relevant items, and creates a worklist from the browser session.

Requirements

• Support concept search and preview in the MCP App.
• Support loading a worklist into the MCP App view.
• Support previewing a proposed worklist before persistence.
• Support creating a worklist from the browser session.
• Keep worklist creation gated to the session-based browser flow.
• Ensure the LLM can build previews but cannot persist a worklist directly.
• Require every worklist item to have a resolved concept id before creation.

Acceptance criteria

• Given a user performs a search or opens a worklist, when the MCP App loads the data, then the results are rendered in the shared view state.
• Given a proposed worklist is generated, when it is shown to the user, then it is preview-only and does not persist anything.
• Given the user clicks Create Worklist in the browser app, when the request is submitted, then the worklist is created through the session-gated path.
• Given the LLM is interacting with the MCP App, when it prepares worklist content, then it cannot create the worklist on its own.
• Given an item does not have a resolved concept id, when worklist creation is attempted, then the item is rejected or reported as unresolved.

More details (collapsible)

Scope reference

This ticket covers the implemented Phase 1 surface of the MCP App:

• concept search and preview
• worklist loading
• preview-only worklist proposal
• browser session-gated creation

It corresponds to the current read/create worklist flow described in the MCP App README.

[ocl-automation]

Automated Triage — 2026-06-22

Dimension	Score
Complexity	4
Scope	4
Clarity	3
Dependency	2
Risk	3

Decision: decision/planning-needed
Type: type/feature
Signals: signal/large-scope

Multiple components needed (search, preview, worklist management) with significant design decisions for UI/UX patterns. Scope spans frontend, backend, and data layers. Requirements are clear but implementation details and acceptance criteria are incomplete (truncated with '...').

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-4 (openrouter).