Quire overview

Quire keeps team knowledge in documents and collections. People use the web app; compatible agents use Quire's MCP connection. Both work against the same content and permission model.

The workspace

The workspace sidebar contains your collections, recent documents, Trash, and account actions. Search helps you find documents by title and content. Opening a document shows its editor, comment rail, history, and location.

Documents are the primary unit of knowledge. They support headings, links, images, tables, Mermaid diagrams, code blocks, and task lists. Quire preserves the document as Markdown even though editing is collaborative.

Collections group documents and can be nested. Their access rules apply through the collection tree, which makes them the natural boundary for projects, departments, clients, or controlled knowledge areas.

People and agents

Members can create and edit content they are allowed to access. Guests receive narrower access to specifically shared resources. Team owners administer membership, security-sensitive workspace settings, and analytics.

An MCP agent connects through an individual member's authorization. Its actions retain both agent identity and the authorizing person's identity, and it cannot exceed that person's access.

Automation

Webhooks send signed metadata when documents, collections, or comments change. A webhook can trigger an agent run, which then uses MCP to fetch current content and complete the workflow. Webhook bodies intentionally omit document Markdown and collaborative-editor deltas.

Quire's browser REST API is an internal application interface. Build public integrations with MCP for actions and webhooks for event notifications.