How updates work
The Brixies configuration uses @brixies-mcp/server@latest with --prefer-online.
When your assistant starts the Brixies MCP process, npx checks npm for the release published under the latest tag and downloads it if needed.
An already running MCP process keeps using its current version until you restart it.
Opening a new chat alone may not restart Brixies MCP. Restart the MCP connection or fully quit and reopen your assistant.
Updating Brixies MCP does not require generating a new API key. Keep your existing key if it is still active.
Update your connection
- Make sure your computer is connected to the internet.
- Finish any Brixies operation currently in progress.
- Restart the Brixies MCP connection, or fully quit and reopen your assistant.
- Open a new chat.
- Run the connection test below.
Repeat this for each assistant or computer where you use Brixies MCP.
You do not need to edit your configuration for each release or download the package manually.
If your assistant shows an update notice
Brixies MCP can include an update notice in a tool response when a newer version is recommended. Your assistant may then explain that an update is available.
The notice means the running version is older than the recommended version. It does not mean the update has already been installed.
- Finish any Brixies operation currently in progress.
- Restart the Brixies MCP connection, or fully quit and reopen your assistant.
- Open a new chat and test the connection.
Test your connection
After restarting your assistant, open a new chat and send this prompt:
Send this prompt in the new chat:
Use only the connected Brixies MCP tools to retrieve my account preferences and tell me which framework is currently selected. Only mention the ACSS version if it applies.
Do not open a browser, control my computer, sign in to the website, or make direct API requests outside the MCP tools. Do not ask me to paste my API key into the chat. Do not generate a page.
If the Brixies MCP tools are unavailable or the request fails, stop and explain the connection issue. Do not use another method or rely on previous conversation history.
The connection is working when your assistant retrieves your preferences through a Brixies MCP tool and reports your selected framework.
This test only needs Brixies MCP tools. Decline browser or computer-control requests. Approving a Brixies MCP tool is fine.
This test confirms that the connection works. It does not, by itself, confirm the exact package version running.
If the update does not work
| Problem | What to check |
|---|---|
| The update notice appears again | Make sure you restarted the MCP process, not just the chat. If it persists after a full restart, contact support. |
| The package cannot be downloaded | Check your internet connection and whether your network allows access to npm. |
| Your key is rejected | Check that your key is still active. Updating the package does not renew an expired key or restore a revoked one. |
| One assistant works but another does not | Restart and test each assistant’s Brixies connection separately. |
For connection instructions, see your assistant’s guide:
If the problem continues, contact support with the error message and the name of your assistant. Remove your API key and personal information before sharing screenshots or configuration details.