@gonicore/mcp-setup

Auto-configurator for GoniCore Claude Desktop MCP integration.

This package updates Claude Desktop's claude_desktop_config.json and injects (or updates) the gonicore-backend server entry with the correct supergateway SSE command and API key header.

What it does

• Detects OS-specific Claude Desktop config location:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\\Claude\\claude_desktop_config.json
  • Linux: $XDG_CONFIG_HOME/Claude/claude_desktop_config.json (or ~/.config/Claude/claude_desktop_config.json)
• Creates config directory/file if missing
• Safely parses existing JSON
• Upserts mcpServers.gonicore-backend

CLI arguments

• --url (required): backend base URL (for example http://localhost:3001)
• --key (required): API key (goni_...)

Example:

npx @gonicore/mcp-setup --url http://localhost:3001 --key goni_xxxxxxxxxxxxxxxxx

Success output:

Successfully configured Claude Desktop. Please restart Claude Desktop.

Local development usage (before publish)

From repository root:

node packages/mcp-setup/index.js --url http://localhost:3001 --key goni_xxxxxxxxxxxxxxxxx

Publish guide (npm)

1. Authenticate:

npm login

2. Verify package metadata in packages/mcp-setup/package.json:

   • name
   • version
   • bin

3. Publish from package directory:

cd packages/mcp-setup
npm publish --access public

4. Bump version before each new release:

npm version patch

Post-publish verification

Run on a clean machine:

npx @gonicore/mcp-setup --url http://localhost:3001 --key goni_test_key

Then open Claude Desktop config and confirm mcpServers.gonicore-backend is present and correct.

Notes

• Use API keys (goni_...), not JWT tokens.
• Restart Claude Desktop after running setup.
• If backend URL or key changes, run setup again to overwrite with fresh values.