v0.3.5

v0.3.5

v0.3.4 exposed a major UX gap for global npm installs: users had no clear place to put their .env file. The MCP server only loaded from process.cwd(), while the bundled .env.example lived deep inside the npm install path.

This release fixes that.

What's new

• Added brainrouter-mcp init

  brainrouter-mcp init

  Creates ~/.config/brainrouter/server.env from the bundled example file (chmod 0600). Won’t overwrite existing configs.

• New env loading priority:

  1. $BRAINROUTER_ENV_FILE
  2. ~/.config/brainrouter/server.env
  3. ./.env

• Server now prints which env file was loaded:

  env: loaded 17 vars from ~/.config/brainrouter/server.env

• README rewritten for actual npm users

  • Proper global install flow
  • $PATH usage
  • sudo guidance for system Node installs

• SETUP.md split into:

  • Install from npm
  • Clone and build for development

Recommended install flow

npm install -g @kinqs/brainrouter-cli @kinqs/brainrouter-mcp-server

brainrouter-mcp init
$EDITOR ~/.config/brainrouter/server.env

# Terminal 1
brainrouter-mcp --http --port 3747

# Terminal 2
brainrouter config && brainrouter login
brainrouter

Compatibility

• Existing monorepo .env setups still work
• All 109 CLI tests still passing

Diff

v0.3.4...v0.3.5

Full Changelog: v0.3.4...v0.3.5