.png)
Early access testing: This MCP connector is currently in early access testing. Features, availability, and behavior may change as testing continues.
The dRofus MCP connector lets MCP-capable AI tools connect to dRofus through a remote server so users can query project data using natural language. This guide explains what it is, how to connect, which server addresses to use by region, and the key precautions to follow before using it.
Use the MCP connector carefully. Before connecting an AI tool to dRofus project data, make sure you have permission from the person or organization that owns or controls that project data. Only share data with AI tools that your project owner, employer, or organization has approved for that purpose.
How sign-in and access works: When you connect an AI tool, you sign in with your normal dRofus account and pick a project. The connector can only access the dRofus projects and information that your account is allowed to access. If you do not have permission to see or change something in dRofus, the connected AI tool cannot do it either.
What the MCP connector is for
MCP stands for Model Context Protocol. In dRofus, the MCP connector provides a structured way for AI clients to access dRofus data and tools over HTTP. Instead of only chatting with a language model, you can let a compatible client retrieve live information from dRofus and, where supported and permitted, perform structured actions.
-
Ask questions about project data in plain language
-
Find rooms, items, and occurrences using filters and project context
-
Inspect details such as room data, item definitions, and equipment assignments
-
Support analysis workflows like discrepancy checks, standards review, and data verification
The exact tools available inside the client depend on the current MCP server implementation, your permissions, and the MCP client you are using.
Regional MCP server addresses
Use the regional endpoint that matches the dRofus environment or region you need to access. The endpoint format is https://api-xx.drofus.com/mcp.
|
Region |
Address |
Typical use |
|---|---|---|
|
EU |
|
Europe |
|
NO |
|
Nordics |
|
US |
|
United States |
|
CA |
|
Canada |
|
AU |
|
Australia and Oceania |
|
JP |
|
Japan |
|
UK |
|
United Kingdom |
Before you connect
-
Pick your regional address from the table above.
-
Check that your organization allows it. Some AI tools need an administrator to enable custom connectors or remote MCP servers, and some plans do not include them.
-
Add a remote MCP server or custom connector in the client's MCP, connector, plugin, extension, or tool settings, using your regional URL.
-
Use browser sign-in only. Choose OAuth browser sign-in with your dRofus account. If the client shows advanced OAuth settings, leave OAuth Client ID and OAuth Client Secret empty. Do not choose API key, bearer token, basic authentication, or manual client ID/secret setup. The only exception is Microsoft Copilot Studio, which needs a client ID and secret from dRofus (see the Microsoft Copilot Studio section).
-
Open a new chat or agent session and verify that the dRofus tools are available.
Tools
|
Client or tool |
Status |
Notes |
|---|---|---|
|
Claude |
Supported |
Use when your organization has approved Claude and the client supports remote MCP over HTTP. |
|
ChatGPT |
Supported |
Use where custom connectors are available for your plan and organization settings. |
|
GitHub Copilot CLI |
Supported |
Add the regional dRofus MCP URL as a remote MCP server and sign in with your dRofus account when prompted. |
|
Microsoft Copilot Studio |
Manual setup |
Needs a manual OAuth setup with a client ID and secret from dRofus. See the Microsoft Copilot Studio section below. |
|
Other MCP-capable clients |
Depends |
Requires remote MCP over HTTP, CIMD support, and OAuth browser sign-in without manual client ID or client secret setup. |
Good to know before you start
Does the AI tool get my password?
-
No. You sign in on the dRofus sign-in page, and the AI tool only receives a time-limited access token linked to your dRofus account. When it expires, you are asked to sign in again.
-
If a dRofus sign-in page opens that you did not start yourself, close it without signing in.
Where does the data go?
-
When you ask the AI tool something, data from dRofus is sent to the AI provider to create the answer. From that point, the agreement between you or your organization and the AI provider decides how the data is handled. If the data contains personal information, your organization is the data controller.
-
How the provider handles the data depends on your plan:
-
Personal plans (such as Claude Free, Pro or Max, and ChatGPT Free, Plus or Pro) may use conversations to train models unless you turn this off in the settings.
-
Business plans (such as Claude Team or Enterprise, ChatGPT Business or Enterprise, and Microsoft Copilot Studio) usually do not use your data for training and include a data processing agreement.
-
-
If you work with project data that belongs to a client or project owner, we recommend a business plan. Always check your provider's current terms and your organization's rules for AI tools.
Can I use other connectors in the same chat?
-
Yes, but only connectors and tools you trust. Other MCP servers in the same chat can in principle read what the AI tool gets from dRofus. Turn off unknown or untrusted connectors when you work with dRofus data.
Who is responsible if the AI tool makes a mistake?
-
You are. AI tools can misunderstand a question, miss data or draw conclusions the data does not support. Check the answers before you rely on them. If the AI tool offers to change data in dRofus, read what it plans to do before you confirm, just as you would when working directly in dRofus.
How do I disconnect?
-
Remove the dRofus connector in the AI tool's connector or MCP settings at any time.
-
If you no longer use the AI tool, or think someone else may have gained access to it, remove the connector right away and contact your dRofus administrator.
Do I need a paid AI plan?
-
You need a plan with the AI provider that allows custom connectors or remote MCP servers. Availability differs by provider and plan, and some business plans require an administrator to turn it on.
How to use the connector effectively
Once connected, start with small, low-risk queries to confirm that the tool is using the right project and returning expected results.
Good first tasks
-
List rooms in a department or level
-
Find rooms missing a required property
-
Retrieve details for a known room or item
-
List item occurrences for a selected room
-
Compare room or item data against a standard
Example prompts
List all operating rooms on Level 2 and show their room numbers and statuses.
Find rooms in Department A that are missing the required acoustic rating.
Show all equipment occurrences assigned to Room 3.215.
List item definitions related to surgical lighting and summarize the key fields.
Best practice: Be explicit about scope. Include the project, department, building, level, room type, or item class in your prompt whenever possible. This improves result quality and reduces the chance of acting on the wrong data.