Opens in a new tab

Brixies MCP is here! Find layouts with your AI assistant. Learn more

Cursor

Add Brixies MCP to Cursor and check that the connection works.

Before you start

Make sure you have:

  • Cursor installed and working on your computer.
  • Node.js 22 or later and a working npx command.
  • A Brixies account with an active annual plan or lifetime access (LTD).
  • An active Brixies API key.

See Requirements if you still need to prepare your computer, or Get your API key to generate your key.

This guide connects Brixies to Cursor running locally on your computer.

Copy your configuration

  1. Open Account → API key.
  2. Find Connect your assistant. If the section is collapsed, click Show setup.
  3. Select Cursor.
  4. Choose Paste config.
  5. Click Copy configuration.

The configuration includes the package command and the Brixies API URL. Your key is represented by the placeholder YOUR_BRIXIES_API_KEY.

Add Brixies to Cursor

  1. Open your personal Cursor MCP configuration file in a text editor. Its location is listed below.
  2. Add the Brixies configuration:
    • If the file is new or empty, paste the configuration you copied.
    • If it already contains MCP servers, add the brixies entry inside the existing mcpServers object. Preserve the other entries.
  3. If a brixies entry already exists, update it instead of adding another.
  4. Replace YOUR_BRIXIES_API_KEY with your actual key, keeping the surrounding quotation marks.
  5. Save the file.

Configuration file location

Operating systemLocation
macOS or Linux~/.cursor/mcp.json
Windows%USERPROFILE%.cursormcp.json

Find the configuration folder

The .cursor folder may be hidden or difficult to locate. You can open it directly using its path.

On macOS:

  1. Open Finder.
  2. Press Cmd + Shift + G.
  3. Enter ~/.cursor/ and press Return.
  4. Open mcp.json in a text editor.

To show or hide hidden files in Finder, press Cmd + Shift + . (period).

On Windows:

  1. Open File Explorer with Windows + E.
  2. Click the address bar.
  3. Enter %USERPROFILE%.cursor and press Enter.
  4. Open mcp.json in a text editor.

If the file does not exist, create the .cursor folder in your user home directory and a plain-text file named mcp.json inside it.

This personal configuration makes Brixies available across your local Cursor projects.

Keep your key private. Enter it directly in the local configuration file. Do not paste it into the chat or share the file while it contains your key.

Need help editing the file?

You can use Copy a prompt in the Brixies setup section to ask Cursor to prepare the configuration.

Review the proposed changes and let it leave YOUR_BRIXIES_API_KEY as a placeholder. Then enter your real key directly in the local file.

If Cursor cannot edit the file, ask it to explain the changes so you can make them yourself.

Restart Cursor

  1. Save your configuration changes.
  2. Fully quit Cursor and reopen it.
  3. Open a new Agent chat.

The first launch may take a little longer while npx downloads the Brixies MCP package. You do not need an npm account or a manual installation of index.js.

Check the server

  1. Open Customize → MCPs.
  2. Find brixies.
  3. Make sure the server is enabled and its tools are available.

If Cursor reports a connection error, resolve it before continuing with the test.

Test your connection

Send this prompt in the new Agent chat:

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.

If Cursor asks for permission to use a Brixies MCP tool, review and approve that tool request.

The connection is working when Cursor 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.

A reply based only on earlier conversation history does not verify the connection.

If the connection does not work

ProblemWhat to check
Brixies tools are unavailableConfirm that you saved your personal MCP configuration, restarted Cursor and enabled the Brixies server.
Cursor reports a configuration errorCheck the JSON syntax, including quotation marks, commas and braces.
The MCP process cannot startCheck that Node.js 22 or later is installed and that npx --version works in your terminal.
Your key is rejectedMake sure you replaced the placeholder with your current active key. If you regenerated it, update the configuration.
Brixies reports a membership issueCheck your plan in Account → Billing.

If you need support, share the error message with your API key and personal information removed.

You’re connected

You can now ask Cursor to search the Brixies library and help you choose layouts.

To start with the copy-link workflow, try:

Example prompt

Find Brixies layouts for a dental clinic landing page using my framework preference. Include a hero, services, testimonials and a contact section. Show me your proposed selection before generating a copy link.

How to update Brixies MCP

On this page

Type at least 2 characters to search.