Setting up the MCP in your editor

There are two ways to connect, depending on the tool. The Claude web and desktop app uses OAuth — you sign in through the browser and never handle a key. Everything else uses the BYQ address plus your MCP 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.

‍

Claude (web & desktop app)

No key, no config file. There are two routes, and the first is the easiest:

• From the connector directory. BYQ Supply is listed in Claude's connector directory. Open the toolbox in the Claude sidebar, go to Customize → Connectors, click +, then Browse connectors, find BYQ Supply and hit Connect. Sign in with your BYQ account and you're done.
• As a custom connector. Go to Settings → Connectors → Add custom connector, set the name to [class]BYQ Supply[/class] and the remote MCP server URL to [class]https://app.byq.supply/api/mcp[/class], then save. Claude opens a browser window for you to sign in and authorize. Leave the OAuth Client ID and Secret fields blank — they aren't needed.

Either route works on Claude web, desktop, and mobile. On Team and Enterprise plans an owner adds it once for the organisation, and members then connect with their own BYQ account.

‍

Claude Code

Claude Code is the terminal CLI and does use a key. 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, merge [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"
      }
    }
  }
}

‍

Codex

Codex keeps its servers in a TOML file. Open [class]~/.codex/config.toml[/class], add the block below, then restart Codex. The CLI, the IDE extension, and the desktop app all read this same file, so you only do it once.

‍

[mcp_servers.byq-supply]
url = "https://app.byq.supply/api/mcp"
http_headers = { Authorization = "Bearer YOUR_API_KEY" }

‍

Lovable

Lovable doesn't use a config file — you add the server in the interface. Open Settings → MCP and add a new server with:

• Server URL — [class]https://app.byq.supply/api/mcp[/class]
• API Key — your BYQ key, pasted on its own (Lovable adds the [class]Bearer[/class] part for you)

Save, and Lovable connects to BYQ for that project.

‍

Other AI tools

Any tool that can call a remote MCP server over HTTP 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.

‍

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.
• You're on Free. The MCP needs an active Pro or Ultra plan — without one there's no key to generate and the connection won't authorize.

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