Connection problems

Brixies tools are unavailable

If your assistant cannot find or use the Brixies MCP tools:

1. Check that you added the Brixies configuration to the correct file for your assistant.
2. Make sure you saved the file and replaced YOUR_BRIXIES_API_KEY with your active key.
3. Confirm that the Brixies server is enabled or approved where your assistant requires it.
4. Restart the MCP connection, or fully quit and reopen your assistant.
5. Start a new chat and test the connection.

Use your assistant’s setup guide to check the file location and configuration:

• Claude Desktop
• Claude Code
• Codex
• Cursor

The MCP process cannot start

Brixies MCP requires Node.js 22 or later on the computer running the MCP process.

Open a terminal and run:

node --version

The result should show version 22 or later.

Then run:

npx --version

This should return a version number. It does not need to match the Node.js version.

If either command is unavailable, install Node.js and reopen your terminal and assistant. See Requirements for installation guidance.

If both commands work but the connection still fails, check the assistant’s MCP error details:

Error or symptom	What to check
The command cannot be found	The assistant may not have access to the same command path as your terminal. Fully restart the assistant and check its setup guide.
The package cannot be downloaded	Check your internet connection and whether access to npm is blocked.
Requests to Brixies fail or time out	Check your internet connection and whether the Brixies API is reachable from your network.

The configuration has an error

Copy the configuration for your assistant from Account -> API key, under Connect your assistant.

Assistant	Configuration format
Claude Desktop	JSON
Claude Code	JSON
Codex	TOML
Cursor	JSON

When editing the file:

• Preserve quotation marks, brackets and line breaks.
• Keep your other MCP servers and settings.
• Update the existing Brixies entry instead of adding a duplicate.
• Replace YOUR_BRIXIES_API_KEY with your active key.
• Save the file with the correct filename and extension.

Restart the MCP connection after saving your changes.

Your assistant tries to use a browser instead

The connection test should use the connected Brixies MCP tools.

If your assistant asks to open the website, control your computer or receive your API key in the chat, decline that request and use the test prompt below.

Approving a request to use a Brixies MCP tool is fine.

Test the connection

Restart the Brixies MCP connection, or fully quit and reopen your assistant. Start a new chat and send this prompt:

If your assistant successfully retrieves your preferences through a Brixies MCP tool, the connection is working.

If a Brixies tool reports an API key or membership error, follow API key and membership errors.

An update notice keeps appearing

Make sure you restarted the Brixies MCP process, not just the chat.

The configuration provided by Brixies uses @latest and --prefer-online to check for the current release when the process starts.

Follow Update Brixies MCP, then test the connection again.

Still need help?

Include the following information when contacting support:

• Your assistant and its version.
• Your operating system.
• The exact error message.
• Whether node --version and npx --version work, and the versions they return.
• The setup steps you completed and what you already tried.

Contact support