Connecting Claude, ChatGPT and others (MCP)

Part 1: Using BuildColab from Claude, ChatGPT and other AI tools

If your team already works in Claude, ChatGPT or another AI tool, you can connect it to BuildColab. The tool then gets the same BuildColab tools BORO uses: it can list your projects, read BoQs, offers, contracts, payment applications, the schedule, files, task boards and meetings, search this User Guide and your saved memories, and, if your company has write access, change data.

Read-only or read and write

How to connect an AI tool to BuildColab

1. Sign in to BuildColab in your browser and select, in the sidebar, the company you want the tool to work with. The connection is tied to the company selected at this moment.
2. In your AI tool, add a custom connector (in some tools called "MCP server" or "remote MCP") and enter the BuildColab MCP server address. BuildColab support gives you the address; it ends with /mcp. Follow your tool's help for where to add connectors.
3. The tool opens the BuildColab consent page Connect to BuildColab in your browser. This page is in English only. It says "{tool} is requesting access to your BuildColab account via MCP." and what the tool will be able to do: for a read-only company, "It will be able to read the data your account can access in your current company (projects, BOQs, the User Guide, and saved memories). It cannot make changes."; for a company with write access, "It will be able to read and change the data your account can access in your current company, with your permissions: BOQs, prices, templates, the schedule, files, contracts, offers and payment applications." followed by the warning "Its changes happen immediately: BuildColab will not ask you to approve each one, and some of them notify other companies (for example, submitting an offer or a payment application). Only connect a tool you trust to act for you."
4. Click Approve to connect ("Authorizing…" shows briefly), or Deny to refuse.
5. You are returned to the AI tool. Its BuildColab tools are now available; ask it, for example, "List my BuildColab projects".

What a connected tool can and cannot do

• It acts as you: your permissions, your plan, the company chosen at connection. It never sees other companies' internal data.
• Tools your company set to Blocked in BORO Settings → Tools are not available to it. Read tools set to With approval are hidden from it, because MCP has no approval card.
• Background tasks, opening screens in BuildColab, and the external connections and apps of BORO are not available over MCP.
• Write access is checked on every call. If BuildColab switches it off, the next write is refused. If it is switched on, the tool sees the write tools after it reconnects or reloads its tools.
• If you leave the company or lose access, the tool gets "This account no longer has access to the connected company."

Cost and limits

• Each tool call costs a small fixed amount of credits from the company wallet (by default 0.01 credits). The AI tool's own usage is paid to its provider, not to BuildColab.
• The company's Requests per minute (per user) limit in BORO Settings → Governance also applies: "Rate limit reached: at most {n} MCP calls per minute. Please wait a moment."
• With an empty wallet calls are refused with "Your BORO credit balance is empty."; with BORO switched off in Governance, with "The AI assistant is disabled for this company."
• Every call is listed in BORO Settings → Governance → Action log with the badge MCP.

How to disconnect an AI tool

1. Open the BORO panel → Settings → MCP access (MCP достъп). The list Connected AI tools (MCP) shows your connected tools ("No connected tools." when there are none).
2. Click Revoke access (Прекрати достъп) next to the tool. Its access ends at once. To use it again, connect it again.

1. MCP access in the left menu of BORO Settings.
2. The list Connected AI tools (MCP); here no tool is connected yet ("No connected tools."). A connected tool is listed with its name and a Revoke access (Прекрати достъп) button that disconnects it at once.

Part 2: Connecting outside services to BORO

BORO can use tools from other services: read your Gmail or Google Drive, look up a supplier's price list, create a page in Notion. A connected service's tools join BORO's tools. Calls to them need approval by default, and what they return is treated as information, not as instructions to BORO.

How to connect a recommended service

1. Open BORO Settings → External connections (Външни връзки). The section Recommended connections (Препоръчани връзки) lists Gmail, Google Drive, Atlassian, monday.com, Notion, Stripe, PayPal and Canva.
2. Click Connect (Свържи). The service's own sign-in and consent page opens in a pop-up. Allow access there.
3. The connection shows Connected (Свързано). Requires setup (Изисква настройка) means "An administrator must configure an OAuth client (Google Cloud) for this connection."; contact BuildColab. "Connection failed. Please try again." means the sign-in did not finish.
4. When a connection expires, it shows Reconnect (Свържи отново); click it and sign in again.

1. External connections in the left menu of BORO Settings.
2. The section External connections (MCP) with the list Recommended connections; further down, Other MCP server with Add connection.
3. A personal connection marked Personal (Личен).
4. Connect (Свържи) for a recommended service.

How to add another MCP server

1. In External connections, under Other MCP server (Друг MCP сървър), click Add connection (Добави връзка).
2. Fill in Name (Име), URL (URL адрес, for example https://…/mcp) and, if the server needs one, Token (optional) (Токен (по избор)): "Bearer token if the server requires one".
3. Click Save. The connection appears as a card with its tools.
4. Click Test (Тествай) to check it: "Connection successful" (Успешна връзка) or the error.

A company can have at most 10 such connections. The token is stored and never shown again.

Managing a connection

• Approval (Одобрение): "Require approval for every call to this server". On by default; switch it off only for a server you trust.
• Disable / Enable: pause the connection without deleting it; BORO stops seeing its tools.
• The bin deletes the connection at once, without a further question.
• In BORO Settings → Tools, each connection is its own section where you can set No approval, With approval or Blocked per tool.
• During a conversation, Add (+) in the message field → External connections shows a switch per connection ("{n} of {total} active in this conversation") so you can pause one without leaving the chat; Manage connections opens the settings page.

Apps

Where your BuildColab environment offers it, External connections starts with a section Apps (Приложения): "Connect the apps your team uses — BORO can then read from them and act in them on your behalf." Use Search apps… to find an app, click Connect and sign in to it in the pop-up; it then appears under Connected apps (Свързани приложения), where Disconnect (Прекъсни връзката) removes it. The switch Allow apps for the company (Разреши приложенията за компанията) turns all such apps off or on for everyone in the company; when it is off you see "Apps via Pipedream are switched off for your company."

Common questions

Related

• What BORO can do
• Settings, models and credits
• Approvals and background tasks
• AI features: search, artifacts, diagrams