What problem does it solve? Teams using ContextHub need a reliable way to store and manage documents (mission docs, project docs, SOPs, artifacts) so they are properly indexed and searchable, instead of bypassing the metadata pipeline by writing raw files to S3 or misusing memos. ## Core Features & Use Cases - Document CRUD via MCP tools: Create, read, list, and delete documents of any content type (mission, project, sop, artifact, context, session) using ch_write_context, ch_read_context, ch_list_context, and ch_delete_context. - Automatic metadata and indexing: Writes run a metadata sidecar, Obsidian frontmatter injection, and Bedrock KB indexing so documents are searchable and correctly tagged. - Use Case: Attach an implementation plan to a mission by calling ch_write_context with content_type="mission" and a path like {mission_id}/docs/plan.md, then verify it landed with ch_list_context. ## Quick Start Ask the agent to save the current plan as a document on your mission in ContextHub and then list the mission's docs to confirm it was stored.