This guide is for connecting your own AI assistant to Visibuild. If you’re a company admin or Auth Manager setting MCP up for your whole company, start with Visibuild MCP instead.
Before you start
Two things need to be in place before you connect:
1. MCP is enabled for your Visibuild company. It’s off by default – your company’s Auth Manager switches it on in Visibuild settings. If you’re not sure, check with them first.
2. Your AI assistant supports MCP and you’re on a qualifying plan. Free tiers generally can’t add custom connectors. Check the table below.
AI assistant | MCP support | Plan required |
Claude (claude.ai) | ✅ Supported | Pro, Max, Team, or Enterprise |
ChatGPT | ✅ Supported | Plus, Pro, Team, Enterprise, or Edu |
Microsoft Copilot (via Copilot Studio) | ✅ Supported | Copilot Studio licence – IT admin setup |
Amazon Quick | ✅ Supported | Enterprise subscription |
Gemini | ⚠️ Varies, check with your Google Workspace admin | – |
Other MCP-compatible tools | ✅ Supported | Follow your tool’s MCP guide |
Your Visibuild MCP URL
Visibuild is hosted in regional environments, and each region has its own MCP URL. Use the one for the region where your Visibuild data is hosted – the subdomain in your Visibuild web address (apac, eu, or us) tells you which.
Region | MCP URL |
Asia-Pacific |
|
Europe |
|
North America |
|
Not sure which region you’re on? Ask your Visibuild admin, or contact us and we’ll confirm.
Connecting Claude
Sign in at claude.ai.
In the left sidebar, click Customize, then open the Connectors tab.
Click + and select Add custom connector.
Enter a name (e.g. Visibuild) and paste in your region’s MCP URL.
Click Add. Claude redirects you to Visibuild to sign in and authorise the connection.
Start a new chat, click + in the message bar, select Connectors, and toggle Visibuild on.
Skip the per-chat toggle: go to Settings → Customize → Connectors → Visibuild and set read-only tools to Always allow.
On Claude Team or Enterprise: your Claude organisation owner must add the connector under Organisation settings → Connectors before members can connect.
Connecting ChatGPT
ChatGPT needs Developer Mode enabled before you can add a custom MCP connector. It’s available on Plus, Pro, Team, Enterprise, and Edu plans. Free accounts aren’t supported.
Open ChatGPT, click your profile picture, and go to Settings.
Select Connectors, click Advanced settings, and turn on Developer Mode.
Back in Connectors, click Add custom connector.
Give it a name (e.g. Visibuild) and paste in your region’s MCP URL.
Complete the sign-in and authorisation flow when prompted.
To use it: open a new chat, click + in the message bar, select More, and enable Visibuild for that session.
Connecting Amazon Quick
Amazon Quick connects to Visibuild through a team-level integration – set it up once and share it, rather than each person connecting individually. You’ll need an Amazon Quick Enterprise subscription and permission to add integrations.
In the Amazon Quick console, choose Connectors, then open the Create for your team tab.
Find and choose Model Context Protocol (MCP).
On the Create Integration page, enter a Name (e.g. Visibuild) and an optional Description, and paste your region’s MCP URL into MCP server endpoint.
For Connection type, choose Public network – the Visibuild MCP is reachable over the internet, so no VPC connection is needed. Click Next.
Visibuild supports Dynamic Client Registration, so Amazon Quick registers itself automatically – no client ID, secret, or redirect URL is needed, and the authentication step configures itself. Sign in with Visibuild when prompted to authorise the connection.
Click Create and continue. Amazon Quick discovers the Visibuild tools and registers each one as an action – review the list and turn on the ones you want, then click Next.
Share the integration with the rest of your team if needed.
Note: Amazon Quick registers the tool list once, when the integration is created. When Visibuild releases new MCP tools, delete and recreate the integration to pick them up.
For full Amazon documentation, see Model Context Protocol (MCP) integration in the Amazon Quick User Guide.
Connecting Microsoft Copilot (via Copilot Studio)
Copilot’s MCP integration works through Copilot Studio and is set up by your IT or Power Platform admin, not from the Copilot chat app. It isn’t a self-serve connection, so flag it to your admin and share this section with them.
Before starting, your admin should confirm:
They have a Copilot Studio licence and permission to add tools in the target environment.
Generative orchestration is turned on for the agent (Settings → Generative AI). MCP tools won’t appear without it.
Steps for your admin:
In Copilot Studio, open the agent (or create one) and go to Tools → Add a tool → New tool → Model Context Protocol.
Enter a name (e.g. Visibuild) and short description, and paste your region’s MCP URL into Server URL.
Under Authentication, select OAuth 2.0, then choose Dynamic discovery. No client ID, secret, or redirect URL is needed – Visibuild and Copilot Studio set those up automatically.
Click Create, then Create a new connection and sign in with Visibuild when the window appears. Access follows the signed-in user’s existing Visibuild permissions.
Once connected, the Visibuild tools load automatically on the agent’s Tools tab, ready to use in conversations.
If the tools don’t load: confirm generative orchestration is on and that you chose OAuth 2.0 → Dynamic discovery. Re-creating the tool re-runs the secure setup.
For full Microsoft documentation, see Connect your agent to an existing MCP server.
Test the connection
Once connected in any tool, ask:
What projects do I have access to in Visibuild?
If your project list comes back, you’re connected. You’ll only ever see data your Visibuild account already has access to – the connection follows your existing permissions. From there, try:
What’s the health of [Project Name]?
Show me open defects mentioning waterproofing.
Which subcontractor has the most open items on [Project Name]?
Troubleshooting
The connection fails or times out – check you’ve used the right URL for your region. Asia-Pacific, Europe, and North America each have their own.
Connected, but the assistant says it has no Visibuild data – MCP may not be enabled for your company yet. Check with your Auth Manager.
No option to add custom connectors in ChatGPT – enable Developer Mode (see above); you’ll also need a paid plan.
On a Team or Enterprise plan and can’t add the connector – on both Claude and ChatGPT, organisation owners control whether members can add connectors. Check with your IT admin.
Copilot tools don’t appear – confirm generative orchestration is on and that OAuth 2.0 → Dynamic discovery was selected.
New Visibuild tools don’t appear in Amazon Quick – Amazon Quick registers the tool list once at creation. Delete and recreate the integration to pick up new tools.
Not sure which region you’re on – check the subdomain in your Visibuild web address (apac, eu, or us), or ask your Visibuild admin.