Full read-write Claude connector for Procore
Make Claude create RFIs and log entries in Procore
Stop tabbing back into Procore to file the RFI or write up the day. Claude turns a question or update from chat into the right Procore record, routed to the right project, and commits it only once you approve.
Procore is a construction management platform that general contractors and owners run projects from, covering RFIs, submittals, drawings, daily logs, and budgets. Teams want Claude to act inside it, not just read from it.
What is a Procore MCP server?
A Procore MCP server is a small hosted service that exposes Procore's data and actions to Claude over the Model Context Protocol, so Claude can industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Procore's current connector do today?
Today, Procore exposes a REST API, but a default read-write Claude connector is not something you can assume is in place. Any current connection tends to be read-leaning or built by hand. A custom Procore connector adds scoped write actions, such as creating RFIs or logging entries, with human-in-the-loop approval.
What does full read-write Procore access unlock?
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
Can Claude create an RFI in Procore from chat?
Yes. With a full read-write Procore connector, Claude can create an RFI on the right project, attach the relevant spec section, and route it to the assigned responder. It drafts the entry from your question, and submitting or notifying people is a gated step that waits for your approval.
Can Claude add a daily log entry in Procore?
Claude can add a daily log entry for weather, manpower, or notes against the correct project, and it can draft a submittal linked to its spec section the same way. These write actions are scoped, so Claude posts to the project you point it at and nothing beyond that.
Does the Procore connector get more access than my login?
No. The connector authenticates through OAuth and inherits the permissions of the account it runs as, including your project and company-level access. It never grants Claude more than that login already has, and scopes can be narrowed further to only the projects and tools you intend it to touch.
How a Procore connector works
We build a small MCP server that authenticates to Procore over OAuth 2.0 using the narrowest scopes the work needs. Read tools (list projects, read an RFI) and write tools (create RFI, add log, draft submittal) are kept separate, and outbound or destructive actions require your confirmation. Claude never has more access than the Procore account it runs as, and we can add IP allowlisting where your tenant supports it.
Frequently asked questions
Can Claude create an RFI in Procore, not just read project data?
Will Claude submit or send anything in Procore without my approval?
Does the connector get more access than my Procore login has?
Related connectors
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.