How do you connect Claude Desktop to construction software with MCP? First confirm the software provides a remote MCP connector, then add its URL in Claude’s connector settings, authenticate, and test a read-only task. Do not begin with an agent that can send invoices or edit financial records.
Disclosure: Opsite sells construction software with an MCP endpoint. Connector screens, permissions, and plan availability can change. The steps below explain the current evaluation path, not a guaranteed two-minute setup or permission to use every tool.
Before you connect
- Use a test account or representative sample job with no sensitive client information.
- Confirm your Opsite plan includes the external agent connection; current plan details list API access and AI agents on Enterprise.
- Ask an administrator for the current connector URL and authentication method. Do not paste an API key into a chat message or public document.
- Choose a user or credential with the least access needed for the first test.
Opsite’s hosted MCP service is exposed at https://app.useopsite.com/api/mcp. Its tool list is governed by the authenticated credential’s scopes. Ask the Opsite team to confirm your account’s current authentication flow and permitted tools before entering credentials.
Add the remote connector in Claude
Anthropic’s remote MCP connector instructions describe the current Claude, Cowork, and Claude Desktop flow. For an individual account, open Customize → Connectors, add a custom connector, enter the server URL, and follow the authentication prompt. Team and Enterprise owners add the connector for their organization first; members then connect individually. Claude reaches a remote connector from Anthropic’s cloud, so the server must be publicly reachable to that service.
The connector method differs from installing a local MCP server in a desktop configuration file. Use the flow that matches the vendor’s supported transport and your organization’s security policy. If Claude rejects the connection, confirm the URL, account permissions, and authentication method with the vendor before broadening access.
Test one safe contractor question
Begin with “List the open action items on the sample job and show their source records.” Check the job name, record IDs, dates, and access permissions in Opsite. Then try a bounded financial read such as “Show unpaid invoices for this job” without requesting a send or update. The assistant’s prose is not an accounting record; open the underlying invoices before acting.
Only after read-only tasks are reliable should you test a draft action, such as preparing a client update for a PM to approve. Review tool permissions, audit history, failure handling, and what happens when an invoice is paid or a client message is changed mid-run.
Questions that matter more than tool count
- Which tools can this credential read, and which can write?
- Can a user see and revoke the connection?
- What audit record is left when Claude calls a tool?
- Can the system require a person to approve a message or financial action?
- What data does Claude receive for a specific query?
For broader platform selection, use the AI contractor software guide. To see the current Opsite connection and permissions on a sample job, request a workflow review.