Connect Procore to Claude Code

Make Claude create RFIs and log entries in Procore. From the terminal, inside the sessions where you already work.

How do you connect Procore to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Procore, you add a Procore MCP server: a small hosted service that exposes Procore's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Procore account. No API keys pasted into config files.

claude mcp add --transport http procore https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Procore once connected?

Full read-write Procore access lets Claude create an RFI from a question in chat, add a daily log entry, draft a submittal, attach the right project and spec section, and post a comment, all once you approve. The coordination that used to mean tabbing back into Procore happens where the work starts.

Create an RFI on a project and route it to the assigned responder
Add a daily log entry for weather, manpower, or notes
Draft a submittal and link it to its spec section
Post a comment or response on an existing RFI
Create a punch list item tied to a location and trade
Update a project directory contact after you confirm the details

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Procore access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Procore API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Procore changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Procore connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Procore connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Procore account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Procore's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Procore?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Procore account it signs in with. Revoking access is one click in Procore.

More on the Procore connector

Procore connector for claude.ai Custom CRM + Claude Code DocuSign + Claude Code QuickBooks Online + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us