Setting up the MCP in your editor

Every tool connects to the same BYQ server, and you give each one the same two things: the BYQ address and your key. The setup page builds a ready-made snippet for your editor with both already filled in, so most of the time you're just copying and pasting. The examples below show what you're pasting and where it goes.

‍

Claude Code

Run one command in your terminal — not inside a Claude Code session. It registers BYQ globally, so it's available in every project afterward:

‍

claude mcp add --transport http byq-supply https://app.byq.supply/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

‍

To check it worked, run [class]claude mcp list[/class] — you should see [class]byq-supply[/class] in the list. Restart any open session to pick it up.

‍

Cursor

Cursor keeps its MCP servers in a JSON file. Open [class]~/.cursor/mcp.json[/class] for all projects, or [class].cursor/mcp.json[/class] inside a single project. If the file doesn't exist yet, create it with the block below. If it already has other servers, paste [class]byq-supply[/class] inside the existing [class]mcpServers[/class] block — pasting it at the top level won't work. Then restart Cursor.

‍

{
  "mcpServers": {
    "byq-supply": {
      "url": "https://app.byq.supply/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

‍

Lovable

Lovable doesn't use a config file — you add the server in the interface. Open your project settings and go to Settings → MCP (the MCP or integrations section), then add a new server with:

• Server URL — [class]https://app.byq.supply/api/mcp[/class]
• API Key — your BYQ key

Save, and Lovable connects to BYQ for that project.

‍

Other AI tools

Any tool that supports a remote MCP server will work. The pattern is always the same: the BYQ address [class]https://app.byq.supply/api/mcp[/class] plus an [class]Authorization: Bearer[/class] header carrying your key. Look for an option to add a custom or remote MCP server in your tool's settings, and follow the snippet on the setup page if your tool is listed there.

‍

Confirming it works

The quickest test is to ask your AI to do something BYQ-specific — for example, "search BYQ for a pricing section." If it returns results, you're connected. If it says it can't, the server isn't registered yet, and it's almost always one of these:

• You didn't restart the tool. Most tools only load MCP servers at startup, so restart and try again.
• The key is off. A truncated or mistyped key is the most common cause — regenerate it and re-paste the full snippet.
• The address is off. Copy [class]https://app.byq.supply/api/mcp[/class] exactly; a missing piece will stop the connection.

Once your AI can see BYQ, you're ready to start pulling from the library. The next chapter covers what it can now do.