Client Connection & User Guide

The MCP endpoint is:

https://bdx-mcp.buildinglogix.net/mcp

claude mcp add --transport http bdxpy https://bdx-mcp.buildinglogix.net/mcp

Settings -> Connectors -> Add custom connector
https://bdx-mcp.buildinglogix.net/mcp

Settings -> Features -> MCP -> Add new MCP server
Name: bdxpy
Type: sse or http
Server URL: https://bdx-mcp.buildinglogix.net/mcp

// Or in .cursor/mcp.json:
{
  "mcpServers": {
    "bdxpy": {
      "url": "https://bdx-mcp.buildinglogix.net/mcp"
    }
  }
}

Settings -> Connectors -> Create -> "Connect to MCP server"
MCP Server URL: https://bdx-mcp.buildinglogix.net/mcp
Authentication: OAuth
Registration method: Dynamic Client Registration

code --add-mcp '{"name":"bdxpy","url":"https://bdx-mcp.buildinglogix.net/mcp"}'
or: Settings -> Copilot -> MCP servers -> Add server

opencode mcp add    # interactive: name bdxpy, type remote, URL below

// Or in ~/.config/opencode/opencode.json (global) or ./opencode.json (per project):
{
  "mcp": {
    "bdxpy": {
      "type": "remote",
      "url": "https://bdx-mcp.buildinglogix.net/mcp",
      "enabled": true
    }
  }
}

opencode mcp auth bdxpy    # opens a browser to sign in

gemini mcp add bdxpy https://bdx-mcp.buildinglogix.net/mcp

copilotstudio.microsoft.com -> New agent
Actions -> Add an action -> Connect to an existing MCP server
MCP server URL: https://bdx-mcp.buildinglogix.net/mcp
Transport: Streamable HTTP
Authentication: OAuth 2.0

Type these into your AI client in plain English — swap the bracketed parts for your own building and equipment names. You never need to know a tool name or a BDX path.

Most problems after a working setup are one of these. Symptoms are written the way you would see them, not the way we log them.

The client says I need to sign in again, or shows the connector as disconnected.

Why: Normal token expiry. Your access is short-lived by design and the client renews it by sending you back through the same magic-link sign-in.

Try: Reconnect from inside the AI client, not from this page. It opens a browser tab, you enter the same work email, and the connector goes back to Connected. Nothing needs to be re-added.

My BuildingLogiX admin just added a site or fixed my access, but the AI still says I do not have it.

Why: Permission and credential lookups are cached in memory for up to a minute so every tool call is not a database round trip.

Try: Wait about a minute and ask again. If it is still wrong after that, it is not the cache — tell your BLX contact.

It answers, but says it cannot find any equipment — or returns far less than I know is there.

Why: Equipment listings are served from a cached inventory of your site. If that cache has never been built, or was only refreshed for part of the site, whole buildings can be missing.

Try: Ask the AI to refresh the site inventory, then retry. If it still comes back short, contact BuildingLogiX — a full refresh may need to be run for you.

It says my site name or slug is not recognized.

Why: Sites are addressed by their slug, which is not always the display name.

Try: Ask “what BDX sites do I have access to?” and use the slug it returns, exactly — they are lower-case and hyphenated, like atlanta-hq.

Listing buildings and equipment works, but anything asking for trends or history fails.We fix this

Why: Your site's BDX URL is configured as http rather than https. BDX redirects the trending endpoint to https, and that redirect turns the request into one the trend API rejects. Discovery calls survive it; trend calls do not.

Try: This is a server-side setting we own. Send your BLX contact the time you tried and what you asked — the fix is a one-line change on your site record.

The AI says my site is only on a local network.

Why: This is by design: your site was set up as local-only because its BDX server is reachable only from your own network, so this service never connects to it and stores no credentials for it.

Try: Let the AI help you write BDXpy scripts that run on your computer, with your BDX address and login in a local .env file. If the server should be reachable from the cloud, contact BuildingLogiX and we can switch the site over.

The timestamps are off by several hours.We fix this

Why: Everything is returned in your site's own local time, not UTC. If the times look shifted by a fixed number of hours, the timezone recorded for that site is wrong.

Try: Tell your BLX contact which site and how far off it is. The timezone is a field on the site record and takes a moment to correct.

ChatGPT will not let me add the connector at all.

Why: Custom MCP connectors sit behind developer mode, which is only available on some ChatGPT tiers. Free accounts cannot add one.

Try: Use a paid ChatGPT tier with developer mode enabled, or connect a different client — Claude, Cursor, Copilot and Gemini all work and are listed above.

ChatGPT is connected, but ignores questions about buildings and answers generically without using tools.

Why: ChatGPT requires custom connectors to be actively enabled for each conversation. In a new chat, the connector may not be selected.

Try: In the ChatGPT message composer, click the + or tool/attachment icon and ensure your BuildingLogiX connector is toggled on for that chat session.

Cursor, Claude, or VS Code shows 'Connection error' or fails during sign-in.

Why: Your browser may have blocked the authorization popup window, or you entered an email address that does not match the one invited by BuildingLogiX.

Try: Check your browser address bar for blocked popups and allow them. Make sure you enter the exact work email address that received the BuildingLogiX invite.

It worked yesterday and today the AI does not seem to have the tools.

Why: The client caches the tool list from when the connector was added. If the connector errored while it was refreshing, some clients silently drop the tools rather than showing a failure.

Try: Remove the connector in your AI client and add it again with the same URL. Your access and history are unaffected — the connector entry is just a pointer.