OpenSuiteMCP

Docs/Upgrades

Keeping OpenSuiteMCP up to date

After go-live on your infra, you choose when to take app updates. Prefer GitHub release tags over tracking main. This page is the forwardable runbook for IT.

Flow

Checkout a GitHub release tag, sync Oracle skills, migrate the database, then rebuild and restart the app.
  1. GitHub release tag
  2. git fetch / checkout
  3. pnpm skills:sync
  4. pnpm db:migrate
  5. rebuild · restart

Before you upgrade

  1. Pick a tag from GitHub Releases. Prefer tags over main.
  2. Read the CHANGELOG and release notes for breaking changes.
  3. Backup Postgres and your env files (.env.local, docker/.env).
  4. Optional but recommended: promote the tag on a non-prod clone first, then production.

Upgrade steps

From your app checkout (adjust the tag):

git fetch --tags origin
git checkout v3.1.0   # or the tag you chose
pnpm install
pnpm skills:sync
pnpm db:migrate
# rebuild / restart your process (pnpm build && pnpm start, or your Compose image)

If you deploy from a private branch, merge or rebase that tag into the branch your pipeline builds, then run the same install → sync → migrate → rebuild sequence in CI or on the host.

Smoke check

  • Sign in
  • NetSuite status chip shows connected
  • Run a simple SuiteQL (or other MCP tool) in chat
  • Skills panel lists the Oracle pack after sync

What does not need an app release

  • Oracle SuiteCloud Agent Skills — pnpm skills:sync (or weekly cron / production entrypoint)
  • Companion prompts — load live from your NetSuite account

What stays yours

  • LLM API keys
  • NetSuite Integration / DCR client and redirect URI
  • Postgres data (chats, settings, encrypted keys)
  • Auth and infrastructure secrets

Need help?

Hands-on upgrade or enterprise support for this product is available from Unstacked Apps (support@unstackedapps.com). Third parties may not charge to implement or commercially support this codebase — see Who may run this.

Related