Store

The store (also at /store) lists add-ons for the Ingot IDE and templates for Rex, the Zaprex cloud agent. Every item in it is real: it's built into Ingot, set up by Ingot, or run by Zaprex. The store shows no download counts and no ratings.

What's in the store

CategoryRuns inWhat it isExamples
ThemesIngotthe color themes built into IngotIngot Light, Ingot Dark, Ingot Ember
Habits packsIngotpatterns Habits watches for and turns into rulesCode style habits
Rules packsIngotready-made files for .ingot/rulesCode style rules
MCP serversIngotthe one-click servers of the Rules & MCP window (MCP)GitHub, Playwright, Postgres
Ingot extensionsIngotfeatures built into Ingot that you install (turn on) and uninstall from the store (Marketplace extensions)Agent Command Center
Rex templatesZaprexwork Rex runs for you in a cloud sandboxNightly test-and-fix, One-off task
Rex extensionsZaprexadd-ons for the Zaprex desktop appRex Crew
  • Tabs: All, Ingot and Zaprex. The All tab shows the Ingot store and the Zaprex store as two sections.
  • Categories: the chips under the tabs. On the browse view each category shows a few items; See all opens the full list.
  • Search matches names and descriptions. For MCP servers it also matches the catalog section, so databases finds Postgres, MongoDB, Redis and the rest.
  • Badges: Beta marks items that are still in beta (the Agent Command Center, and all Rex templates and extensions, like Zaprex itself). Paid plans marks items that need a paid plan; see pricing.
  • Filters live in the address, so you can share a link:
/marketplace?kind=ingot&category=mcp-servers&q=postgres

Install

Install opens a link that the app handles:

ItemLink
Ingot itemsingot://install/<type>/<id>, where <type> is theme, mcp, habits, rules or extension (for example ingot://install/extension/agent-command-center)
Rex templateszaprex://open?path=/app?template=<id>
Rex extensionszaprex://open?path=/app?extension=<id>

If nothing opens after a couple of seconds, the page offers Download Ingot, or Zaprex on the web for Rex templates and extensions.

If your version of Ingot doesn't open the item, follow Install by hand on the item page. Every item has these steps, and they work in every version.

The item page also shows the publisher, what's inside a pack (the patterns, or the full rules file), and for MCP servers the exact command Ingot runs and how the server signs in. MCP servers are made by third parties; Ingot lists them and sets them up.

Store API

The store is also public JSON, cached for a minute:

curl "https://<portal>/api/marketplace?kind=ingot&category=themes"
curl "https://<portal>/api/marketplace/ingot-ember"

q, category (themes, habits, rules, mcp-servers, ingot-extensions, rex-templates, rex-extensions) and kind (ingot or zaprex) are optional. An unknown value returns 400.

Publish to the store

Anyone can publish (Beta). Build a theme, rules pack, Habits pack, MCP server or Rex template with the ingot CLI, create a publish token under Dashboard › Publisher, and run ingot publish. Start with the creator guide; to publish on every version tag, see Publish from CI/CD.

Community extensions appear under From the community, in their category and in search, with a Community badge. Their page shows the publisher, the README, the version history and a Download .ingotx button; ids look like publisher.name (for example /marketplace/acme.react-rules). The store API returns them too, with a community object (version, versions, license, download path).

The rest of this section is for the Ingot and Zaprex teams, whose items are curated in the repository. To publish as the Ingot or Zaprex team:

  1. Ship the item first. A theme or MCP server must be in the Ingot release, and a Rex template must exist on the Zaprex server. The store never lists something that doesn't exist yet.
  2. Add an entry to registry.json in apps/portal/src/marketplace, in the order it should appear.
  3. Run the checks in apps/portal: npm run gate. The registry is validated when it loads, so a bad entry fails the tests and the build.
  4. Open a pull request. After the merge, the item has its own page at /marketplace/<id> and is in the sitemap.

Entry fields

FieldRequiredNotes
idyeslowercase words joined with -; the page address
productyesingot or zaprex
categoryyesthemes, habits, rules, mcp-servers or ingot-extensions for Ingot; rex-templates or rex-extensions for Zaprex
name, summary, descriptionyesthe summary is one line for the card
installRefyesthe id the app knows: theme id, MCP catalog id, extension listing id, template id
highlights, installStepsyeslists of short sentences
iconyes{ "type": "mark", "mark": "Ru", "color": "#1B2647" }, a theme swatch, or a first-party image
contents, contentsFilenowhat's inside a pack; with contentsFile, shown as that file
topic, setup, authMCP onlycatalog section, the command Ingot runs, sign-in, api-key or none
featured, betayestrue or false
planyesfree or paid
price, currencynoset together: 0 for a free item, more than 0 for a paid one, and an ISO code such as USD

Rules for listings

  • No made-up numbers. Entries can't carry download counts, ratings, reviews or stars; the registry check rejects them.
  • No third-party logos. Use a monogram tile in the brand color instead.
  • Say what it really does. Describe what the item does today, not plans.
{
  "id": "code-style-rules",
  "product": "ingot",
  "category": "rules",
  "name": "Code style rules",
  "installRef": "code-style",
  "summary": "The seven rules Habits writes for you, as one always-on rules file.",
  "description": "…",
  "highlights": ["A plain .mdc file in .ingot/rules, easy to edit"],
  "contents": ["---", "alwaysApply: true", "---", "- Use const or let, never var."],
  "contentsFile": ".ingot/rules/code-style.mdc",
  "icon": { "type": "mark", "mark": "Ru", "color": "#1B2647" },
  "installSteps": ["In your project, create .ingot/rules/code-style.mdc.", "Paste the file and save."],
  "featured": false,
  "beta": false,
  "plan": "free"
}