Connect Claude Code to KoalaFix.

There are two ways in. The plugin is quickest: it connects KoalaFix and turns on automatic memory, with one sign-in. The claude mcp add command connects the tools only.

With the plugin

In Claude Code, run:

/plugin marketplace add KoalaFix/koalafix-connect
/plugin install koalafix-auto@koalafix-connect

From a shell, the same is claude plugin marketplace add KoalaFix/koalafix-connect, then claude plugin install koalafix-auto@koalafix-connect. The plugin needs Node.js 22 or later.

When your next session starts, Claude shows you a link and a code. Approve it once in your browser. That one sign-in covers the KoalaFix tools too, from the session after; to use them straight away, open /mcp, pick koalafix and choose Reconnect.

With one command, tools only

claude mcp add --transport http koalafix https://mcp.koalafix.com/mcp

Then run /mcp, pick koalafix and sign in in your browser. Claude uses KoalaFix when it decides to; add the plugin later to make it happen every session.

Check it works

Run /mcp and look for koalafix in the list, connected. Then ask Claude what KoalaFix knows about the project you’re in.

If it doesn’t work

• koalafix shows as failed in /mcp. The saved sign-in was refused, usually because you left the workspace or a token was revoked. Run koalafix login, or delete ~/.kalibrate/credentials.json and start a new session.
• /mcp asks you to sign in although you have the plugin. You installed the koalafix plugin on its own before. Run claude plugin uninstall koalafix-auto@koalafix-connect, then claude plugin uninstall koalafix@koalafix-connect, then claude plugin install koalafix-auto@koalafix-connect.
• No team brief at session start. Check that node --version shows 22 or later. The hooks give up quietly on any problem rather than get in your way.

Related

• Turn on automatic memory
• Connect with a token instead of signing in
• Disconnect an assistant
• What KoalaFix adds to CLAUDE.md and auto memory