MCP Connections

You can connect an AI assistant, such as Claude or Cursor, to ConstructEase and ask it questions about your projects in plain language. The assistant reads your project data directly, so you do not have to copy information out of ConstructEase by hand.

Connecting an assistant is safe by design. You sign in yourself, you see exactly what the assistant is asking for before you agree, and the assistant can never see more than you can see. You can disconnect it at any time.

An administrator has to turn this on for your organization first. Until they do, the connection will not work. See Integrations.

You do not need administrator access yourself, and you do not need access to the Integrations page. Connecting an assistant is something each person does for themselves.

Once it is on, MCP Connections appears in your user menu at the bottom of the sidebar. That page shows the address to give your assistant and lists the connections you have already allowed. If you do not see it, the feature is not enabled for your organization yet.

The exact wording differs between assistants, but the steps are the same.

1. Open MCP Connections from your user menu and copy the server address shown there. It is your ConstructEase address followed by /api/mcp, for example https://app.constructease.com/api/mcp.

2. In the assistant, add a new connector, integration, or MCP server and paste that address.

3. The assistant opens ConstructEase in your browser. Sign in if you are not already signed in.

4. A permission page appears showing which assistant is asking and what it wants to read.

5. If you belong to more than one organization, choose which one the assistant should have access to. It will only see that organization's data, apart from the one shared list explained below.

6. Review the list of what the assistant will be able to do, then select Allow access.

The browser returns you to the assistant, and it can start reading your data.

An assistant can read your projects, the communities and builders behind them, and the record of what your builders' feeds have changed. You can refer to a project by its project number when you ask, and to a community or builder by name. The assistant does not need internal ids.

The permission page lists each kind of access separately, with a checkbox:

• View projects. Each project's address, community, builder, model, stages, schedule dates, and purchase order details, as they stand now.

• View project change history. The audit trail behind a project: which fields changed, what they were before, when each change happened, and which person or automated process made it.

• View pullsheets. A project's pullsheets for a stage: the parts and assemblies to be pulled, their quantities and units of measure, whether each one comes from your own inventory or from a vendor, when the sheet was sent, its in-warehouse date and when its parts were added, and any note somebody typed on the sheet along with how many people are assigned to it. Each sheet also lists the vendors it could be priced for, with their email addresses, and names the one ConstructEase would actually email it to, so an assistant can say who would be billed, and the project's own details — its project number and street address, and its community, builder, division, model and inspection area — which are what decide the sheet's contents. This is the materials list, in the same order, that ConstructEase builds the pullsheet it emails to a vendor from — it covers the whole sheet, so it also includes the parts you pull yourself, which are not on the vendor's own copy. It includes no prices and no amounts — those are the two items below.

• View pullsheet part pricing. Adds the prices to a pullsheet: each part's unit price and line total, from your own price book or the vendor's, and totals for the sheet. The per-part prices are the same figures a vendor sees on the pullsheet you email them for billing; the totals are added up here, because the emailed sheet prints none. Needs the same access as viewing pricing on the Master Parts page.

• View pullsheet stage billing. Adds the stage's billing figures to a pullsheet: the builder's purchase order numbers, amounts and statuses, the subcontractor, base and payment amounts, and the accounting transactions recorded against the stage, with the amounts they were reviewed at. Needs the same access as the billing screens.

• View communities. Community details including the builder, division, address, key dates, and the community cost amounts for temp pole, underground, surcharge, excavation, under slab, and e-permit.

• View community change history. The audit trail behind a community: which fields changed, what they were before, when each change happened, and which person or automated process made it. Routine count updates that happen automatically as projects come and go are not included.

• View builders. The builders in your organization, with their contact details, warranty period, whether each one is enabled for the public API, and any SupplyPro builder IDs.

• View divisions. The divisions you are assigned to, with their trade division codes and warehouse codes.

• View builder import activity. What each builder feed has changed in ConstructEase and when: schedule dates, purchase orders, completed stages, inspection results, and newly created projects and communities. Covers the last 30 days.

• View builder schedule event mappings. How each builder's task names translate into ConstructEase stages, including any corrections someone has made by hand. This is the setting that explains why a builder task did or did not update a stage.

• View project stages. Your organization's stage setup: which stages a project moves through for each trade, in what order, and whether each one needs an inspection, a walk, a punch, or a locate. This is what lets an assistant explain a stage name it has seen on a project, in a schedule date, or in a builder's task mappings. It describes how stages are set up, not where any project stands.

• View roles and permissions. The list of roles in ConstructEase, such as Division Administrator or Warehouse Staff, and what each one is allowed to do: which parts of ConstructEase it can reach and which actions it can take there. This is what lets you ask an assistant who is able to do something, or why a colleague cannot see a screen you can. It covers no personal data: it describes the roles themselves, not who holds them.

Everything is ticked to begin with. Untick anything you would rather not grant. The assistant only gets what is still ticked when you select Allow access. Change history is listed separately because it shows who did what, so you can hand over project data without handing over that. Communities are listed separately because they include cost amounts. You need to leave at least one item ticked; granting nothing is the same as cancelling.

Roles and permissions are one item rather than two, because the list of what each role can do already names every role. Ticking it would not be much use with only half of it.

Project stages are listed separately from projects, because they are your organization's setup rather than any project's data: an assistant can be given the stage list to make sense of what it reads without being given your projects, or the other way round.

Pullsheets are three items rather than one, and the split is worth understanding before you untick anything. The first covers the materials — what to pull and how much — and is the one an assistant needs to answer a warehouse question at all. The other two each add money, and they add different money: part pricing is what the parts cost you or the vendor, while stage billing is what the builder has been charged. Granting one does not grant the other, and granting neither still lets the assistant read the full materials list. If you leave a money item unticked, the assistant is told plainly that you did not grant it, so it will say so rather than reporting a sheet as having no prices.

Not every item will be available to you. Communities, the two builder import items, and roles and permissions all depend on permissions your account may not have, and anything you cannot grant is marked No permission. Roles and permissions needs the same access as the Settings page, because that is where roles are managed in ConstructEase. Project stages do not: everyone in ConstructEase sees stage names on projects already, so this item needs nothing beyond belonging to the organization — even though stages are edited on the Settings page.

Some assistants also offer your builder and division lists as items you can attach to a conversation directly, without asking the assistant to look them up. That is a convenience the assistant provides, not extra access: the attached list is the same data, behind the same permission, as asking the assistant to list them. Communities are not offered this way — that list is usually too long to attach whole, so ask the assistant to look communities up instead.

You may also see a notice that new access is available. A connection is only offered the kinds of access that existed when you made it, so when ConstructEase starts sharing something new, an assistant you connected earlier will not have it. The notice lists what has been added since, and those items are ticked ready to grant.

We are adding to this list regularly at the moment. If your assistant cannot do something you expect, reconnecting it is usually all that is needed to pick up whatever has been added since.

Give the list a glance all the same. If it includes something you would not expect this assistant to want, untick that item, or cancel and check with whoever provided the application.

Three limits always apply:

• It only sees one organization. The one you picked when you connected it. Roles and permissions are the exception, and not because of a gap: roles are set up once for the whole of ConstructEase rather than per organization, so that list is the same wherever you connect from. Who holds which role is per organization, and the assistant is not given that.

• It only sees your divisions. Just like your own project list, the assistant sees projects, communities, and import activity in the divisions you are assigned to and no others. If you are not assigned to any division, it will not find any of those. Three lists are not split by division and so match what you see in ConstructEase: builders, project stages, and roles and permissions.

• It only sees what you can see. Your own permissions still apply. If you cannot view projects in ConstructEase, the assistant cannot either. If someone changes your permissions later, the assistant's access changes with them straight away.

The permission page lists anything the assistant asked for that you are not allowed to grant, marked No permission. You can still continue; the assistant simply will not get that access.

An assistant can only read. It cannot create, change, or delete anything in ConstructEase.

Anyone can build an assistant that connects to ConstructEase, and the name shown on the permission page is not verified by us. If the page says the application has not connected before, treat that as a prompt to check you recognize it.

Only continue if you started the connection yourself, from an application you trust. If a permission page appears when you were not expecting it, select Cancel.

1. Open your user menu at the bottom of the sidebar and select MCP Connections.

2. Find the assistant in the list.

3. Select the delete icon next to it, then confirm.

You do not need any special permission for this. Anyone who can connect an assistant can disconnect it.

The assistant loses access immediately. To use it again you will need to connect it and allow access from the beginning.

The list also shows when each assistant was connected and when it last read your data, which is a useful way to spot anything you do not recognize.

• The assistant cannot connect at all. Check that your address ends in /api/mcp, and ask an administrator whether MCP connections are enabled for your organization.

• The permission page says no organization is available. No organization you belong to has this turned on yet. An administrator can enable it under Integrations.

• The assistant says it is not authorized to read projects. Your account may not have permission to view projects, or you may have connected the assistant without granting that access. Disconnect it and connect again.

• The assistant can read a project but not its change history. Those are separate permissions, and change history may have been unticked when you connected. Disconnect the assistant, connect again, and leave View project change history ticked.

• The assistant can read a community but not its change history. The same separation applies to communities: View community change history is its own item on the permission page, and it needs the same community access as View communities. Reconnect and leave it ticked.

• A permission you expected is not listed at all. The application only receives what it asks for. Most assistants re-read what ConstructEase offers each time you sign in, so a newly added permission appears the next time you connect, under New access is available. If yours still does not list it, remove the connection from your assistant and add it again so it registers afresh.

• The assistant says a permission was only offered when you connected. That is the same thing from the assistant's side. Reconnect it and the newer access will be on the permission page.

• The assistant finds no projects at all. Check which divisions you are assigned to. The assistant only sees projects in your divisions, so an account with no division assigned will come up empty even though the connection itself is working. Ask it to list your divisions first: an empty answer there explains an empty answer for projects, communities, and import activity.

• The assistant cannot read a pullsheet. Pullsheets are their own item on the permission page, separate from viewing projects, so an assistant granted projects alone cannot read them. Reconnect and leave View pullsheets ticked.

• The assistant reads a pullsheet but reports no prices, or no billing. Check whether it is saying the prices are missing or that it was not given them — it will tell you which. Part pricing and stage billing are each their own item on the permission page and each needs its own access in ConstructEase: pricing needs the same access as viewing pricing on the Master Parts page, and billing the same access as the billing screens. If either was unticked when you connected, reconnect and leave it ticked. If your account does not have the underlying access, the item shows as No permission and an administrator has to grant it.

• A pullsheet shows a dash or no price against some parts. That is a part with no price set for the book being used, not a permission problem — it is the same dash a vendor sees on the emailed sheet. Parts you pull from your own inventory are priced from your own price book, and parts a vendor pulls from that vendor's, so a part can have one and not the other. If a whole vendor's column is empty, nobody has entered prices for that vendor yet.

• The assistant says the vendor you asked for is not available for that sheet. That is deliberate rather than a fault: it will not quietly price the sheet for a different vendor, so it refuses and lists the vendors that sheet can be priced for. Check the spelling, and remember that in organizations requiring a warehouse for pullsheets only warehouse vendors are offered.

• The assistant prices a pullsheet for the wrong vendor. By default it uses the vendor assigned to the project's inspection area: the trade-specific vendor if your organization requires a warehouse for pullsheets, and the general one otherwise. Outside warehouse mode that is the same vendor the send screen picks. Inside warehouse mode the send screen picks from the division's first inspection area instead, which may not be the project's own, so the two can disagree — the assistant is told to flag that rather than present its vendor as the one you would send to. Either way you can ask it to price the sheet for a vendor by name, and it can tell you which vendors are available for that sheet.

• The assistant says a pullsheet has no vendor copy. That is not a fault. ConstructEase stops short of emailing a vendor for more than one reason, so the assistant is told which one applies rather than quoting a vendor total. The ones it can report today: no part on the sheet is marked as pulled by a vendor for that division (set the pulled-by column on the parts a vendor supplies); the project's inspection area names no vendor, so the sheet would be addressed to your own organization however the parts are marked (assign a vendor to the inspection area); or a vendor is assigned but has no email address on file, in which case the vendor copy is prepared and then quietly not sent (add an address to the vendor). This answer is always about the vendor the sheet would actually be sent to, and the assistant names that vendor when it gives it — so if you asked it to price the sheet for a different vendor by name, the vendor-copy answer still refers to the assigned one, not the one you named.

• The assistant says it cannot tell whether a vendor copy would be sent. Expected in organizations that require a warehouse for pullsheets, when the project's own inspection area names no vendor. The send screen may still find one from the first inspection area in the division, which the assistant deliberately does not follow, so it reports the answer as unknown instead of guessing. Open the send screen to see the recipient.

• The assistant quotes a different PO number than the sheet you sent. Ask it to check the sheet you sent. The assistant works the number out from the stage's name, while the emailed sheet takes it from the label on the send screen, and the two can differ for a stage whose Rough and Final pair is named unusually. The assistant is told to flag this rather than present the number as the vendor's — and only for the stages where it can actually happen, so when it does raise the point it is worth checking.

• The assistant says a "Rough & Final" stage's sheet is kept under two other stages. Expected when your organization also has separate Rough and Final stages for that trade: ConstructEase files that trade's two sheets under those, one each. The assistant still answers and names the two stages — ask it for one of the two instead. It is also told whether the combined stage is holding a sheet of its own anyway, which happens when a sheet was sent from it before the separate stages were added; in that case the sheet you want is the one on the combined stage, not on either named stage. If you have no separate Rough and Final pair for the trade, the combined stage keeps its own single sheet and the assistant reads it normally.

• A pullsheet the assistant read has never been sent. Expected, and the parts are still right. ConstructEase works the list out from your assemblies rather than storing it, so an unsent sheet has a complete list of parts. The send and arrival dates are simply empty.

• The assistant cannot see communities, or says it is not authorized to read them. Viewing communities is its own permission in ConstructEase, separate from viewing projects. If your account does not have it, the item appears on the permission page marked No permission. Ask an administrator about community access.

• The assistant cannot see builder import activity or the schedule event mappings. Both need permission to view the import log report. If your account does not have it, neither item can be granted, even though the rest of the connection works normally.

• A community is missing from the list. Communities follow the same division rule as projects. A community in a division you are not assigned to will not appear, and asking for it by code returns nothing rather than an error.

• Attaching the builder or division list to a conversation fails. The attachable lists use the same permissions as asking for them. If that kind of access was unticked when you connected, or your account does not have it, the attachment is refused with a message saying which permission it needs. Reconnect the assistant and leave that item ticked, or ask an administrator about the permission it names.

• The assistant cannot see roles or permissions. That item needs the same access as the Settings page, where roles are managed. If your account does not have it, the item appears on the permission page marked No permission, even though the rest of the connection works normally. Ask an administrator about settings access.

• The assistant lists a role but says it has no permissions. Roles and their permissions are two separate things in ConstructEase, and a role nobody has configured yet has none. Ask the assistant for the full list of roles to see it, then set its permissions under Settings > User Accessibility.

• A role the assistant should know about is missing. Roles marked inactive are left out by default, because an inactive role gives nobody access whoever holds it. Ask the assistant to include inactive roles.

• The assistant cannot look up a stage, or does not know what one means. Viewing project stages is its own item on the permission page, separate from viewing projects, so an assistant granted projects alone cannot read the stage setup. Reconnect and leave View project stages ticked. It needs no other permission — everyone in ConstructEase can see stage names already.

• The assistant cannot find a stage you named. Stage names have to match the ones in your setup, though capital letters do not matter. Ask it to list the stages first, or narrow the list to one trade, and use the name it reports. A stage in another organization is reported as simply not found.

• A builder task is not updating a stage. Ask the assistant about the schedule event mappings for that builder. A task name ConstructEase does not recognize has no mapping, so nothing happens when it arrives. The import activity list shows what the feed actually delivered.

• You cannot find the MCP Connections page. It is in your user menu at the bottom of the sidebar, not under Integrations. It only appears once an administrator has enabled MCP connections for your organization.

• The assistant stopped working after a while. Connections expire if unused for a long time, and they also stop working if your permissions change or an administrator turns the feature off. Reconnect to start a new session.

• You are asked to sign in again. Expected. Signing in is how ConstructEase confirms it is really you granting access.