 is a named, user-owned group of documents and assets. Collections cut across folders — anything addressable by a 

 URI can belong to a Collection, regardless of where it lives in the user's folder hierarchy. Use them to group "the reading list for this project," "the assets the marketing Charm should know about," or any other ad-hoc set.

The Collection server lets an external application create Collections, manage membership, and reorder content.

 for editing per-item metadata used by the Docs and Homepage Collection uses.

 URIs, not content. To act on a member, hand the URI to a tool on the 

If a member URI no longer resolves (the underlying document was deleted), 

 still returns the URI — the dangling reference is yours to handle.

 — Where Collection members actually live.

 — Charms whose context dependents may come out of Collections.

Create and manage named groups of documents and assets that cut across folders.

Tool	What It Does
`list_collections`	List the user's Collections
`get_collection`	A Collection plus its documents and assets (as `charmiq://` URIs)
`create_collection`	Create a new Collection
`update_collection`	Update name, description, or ordered flag
`delete_collection`	Delete the Collection (members are not deleted)
`add_to_collection`	Add a document or asset by `charmiq://` URI
`remove_from_collection`	Remove a member
`reorder_collection`	Reorder members in an ordered Collection

Collection MCP Server

Tools

Membership Rules

Ordered vs. Unordered

VFS Integration

Patterns

Next Steps