Install your first pack

What is a pack?

A pack is an installable bundle of nodes for [fix]net. It can contain:

• Plugins — code that runs on your machine and powers new node kinds.
• MCP servers — external tool bridges the engine can talk to.
• Graphs — pre-built node arrangements you can fork and run.

One install wires all three together. You don't configure anything by hand.

Before you start

You need the [fix]net desktop app installed. If you don't have it yet, get the app first.

Finding a pack

The store's Browse and Search pages let you filter by category, level, and publisher. Pack cards show the name, a short description, and the average rating. Click any card to open the detail page.

The detail page has:

• A scorecard — current version, license, required app version, price.
• A changelog — what changed in the latest version, split into added / changed / bugfixes.
• A version history — every published version, each immutable once released.
• A README — the author's extended description and usage notes.

Installing

When you've found a pack you want, click Open in [fix]net app on the detail page. This fires a fixnet:// deeplink that opens the app directly to the pack's install confirmation screen.

The app:

1. Downloads the pack archive.
2. Verifies the cryptographic signature.
3. Mounts the pack — plugins, MCP servers, and graphs become available immediately.

No terminal, no copy-paste, no drift between what the store shows and what installs.

What happens next

After install, the pack's nodes appear in your node library. Contributed graphs appear under "Installed packs" in the hub. You can start from a contributed graph, fork it, and extend it without touching the original.

If you need to uninstall or pin to an older version, open the pack's settings inside the app.

Related reading

• Understand versions and updates →
• How versioning works in the store (blog)