How modules work

Placard is a core place library plus optional modules for specialized workflows (pick wheels, custom tools, …). Modules do not fork the core.

Layers

Modules (Pick, your uploads, …)
        ↓  hostFetch + /api/m/<id>
Core HTTP API + MCP transport
        ↓
Places, lists, tags, media, auth
LayerOwns
CoreAccounts, library, search, enrichment, MCP transport + core tools, shell UI
ModulesSpecialized pages, /api/m/<id>/* HTTP, optional MCP tools

Install modes

ModeWhoHow
BundledOfficial pluginsPinned builds of Pick, Board, Day Out, Menus, and Decide Together ship inactive; an administrator activates them in Marketplace
UploadYou / third partiesPrebuilt zip → Settings → Module marketplace
GitHubYou / third partiesPublic repo URL → latest GitHub Release asset (.placard-module or .zip)

GitHub installs always take the latest Release. The worker checks for newer releases on a configurable interval (default 24h; 0 disables). Admins can also Check now / Update in Marketplace. Private repos are not supported.

There is no “paste a package into MCP.” MCP discovers tools from loaded modules after install and user MCP prefs. See mcp.md.

Rules that keep the product stable

  1. Modules call host APIs (hostFetch) — they do not open core SQL.
  2. Module-private data lives under ctx.dataDir on the modules volume, separate from replaceable installed code.
  3. One implementation behind HTTP and MCP whenever both exist.
  4. Admins can disable or uninstall a module without wiping the place library.
  5. Users can hide a module from nav and turn off its MCP tools independently.

Authoring