Claude + Procore: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Procore connector, and Procore hasn’t shipped an MCP server. Nothing in Claude’s connectors directory, no Procore-official MCP endpoint or repo. That’s a strategy, not an oversight: Procore’s AI bet is entirely in-platform — the Helix intelligence layer with Copilot, prebuilt Agents, and an Agent Builder, plus the ~$168M Datagrid acquisition (completed January 2026) to automate submittal reviews and RFI drafting inside Procore. What exists for Claude is third-party: community MCP servers wrapping Procore’s REST API, all requiring your own developer app credentials, none Procore-endorsed. And every path shares one gate — a Procore company admin has to install the app before anything touches your projects.
Here’s what’s actually available, how you’d wire it up, where the limits bite, and what to use if you want project work that runs on its own.
What actually exists today
- Community MCP servers. Several wrap Procore’s REST API — for example mohllal’s procore-mcp-server, TylerIlunga’s, and one that auto-generates tools from Procore’s OpenAPI spec. CData ships a Python MCP server too. All unofficial — vet before handing over credentials.
- Zapier MCP’s Procore actions. Zapier MCP exposes Procore actions to Claude through Zapier’s bridge — still your own Procore app credentials underneath, plus Zapier’s per-task metering.
- The underlying API is real and broad. Procore’s REST API at developers.procore.com covers projects, RFIs, submittals, daily logs, punch lists, drawings, budgets, and the directory, with OAuth 2.0 (auth-code for user apps, Developer Managed Service Accounts for server integrations) and sandbox environments. A Webhooks API delivers create/update/delete events per project.
So a technical PM can absolutely get Claude reading RFIs through a community server. It’s a build-and-maintain project, not a connector you toggle on.
Procore’s own AI: Helix, Copilot, and Agent Builder
If you’re evaluating “Claude + Procore,” you’re really comparing three routes, and the in-platform one is Procore’s answer. Procore Helix powers Copilot (retrieval and summarization over your project data), Insights, prebuilt Agents, and Agent Builder — custom agents from natural-language prompts, in open beta since Groundbreak 2025. The Datagrid deal adds reasoning and deep-search AI aimed at submittal cross-checks and RFI analysis, and Procore’s Q1 FY2026 earnings call was wall-to-wall agentic AI: embedded agents, event-driven triggers, a voice pilot.
The limits are the mirror image of the community-MCP route: Helix agents live inside Procore and stop at Procore’s walls. Your morning digest, your email follow-ups, your CRM — outside their reach.
How you’d wire Claude up anyway
- Create a developer app at developers.procore.com and set up OAuth 2.0 credentials (sandbox first).
- Get your company admin to install and authorize the app in the company account — this is the gate; permissions then follow Procore’s per-project role templates.
- Run a community MCP server with those credentials and add it to Claude Desktop or Claude Code as a custom connector.
- Ask Claude for open RFIs or yesterday’s daily logs — it reads through the API.
The limits that actually matter
- Nothing is official. No directory connector, no Procore MCP. Community servers are maintained by individuals; API versions and auth quirks are yours to babysit.
- The admin gate. No Procore integration self-serves. If you’re not the company admin, this is a request, a review, and a wait — by design, since Procore permissions carry real project risk.
- No triggers, no monitoring. Procore’s Webhooks API fires on new RFIs and submittal changes, but Claude can’t receive a webhook. MCP tools only run inside a conversation you start — nobody’s watching the ball-in-court clock while you’re on site.
- Laptop-bound for anything scheduled. The closest thing to autopilot is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events.
So Claude via a community server is a decent “query my projects in a chat” tool for a technical team — and not built for “keep RFIs and submittals moving on their own.”
If you want Procore work that runs on its own: Carly
Construction runs on clocks — ball-in-court days, submittal due dates, daily logs that pile up across five active projects. None of it waits for someone to open a chat.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers. Procore connects to Carly via your own API credentials — paste them on carlyassistant.com/integrations (using the app your company admin authorizes, same gate as any Procore integration) — and Carly works the API and webhooks for you:
- When a new RFI lands, Carly summarizes the question, pulls the relevant context, drafts a response for the PM, and starts the ball-in-court reminder clock.
- Every morning at 6am, yesterday’s daily logs across active projects roll up into one exec digest — manpower, weather, delays, safety notes.
- When a submittal nears its due date, Carly nudges the responsible reviewer and drafts the follow-up email to the architect.
- Weekly risk report — RFIs open more than 10 days and overdue submittals, with per-project counts, in leadership’s inbox.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it with you.
- Actually sends — drafts and sends email across Gmail and Outlook, updates tasks and records.
- Connects to anything — 200+ native integrations (see integrations), plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude’s Procore options vs Carly
| Claude (community MCP + API) | Carly | |
|---|---|---|
| Read RFIs, submittals, daily logs | Yes, via community servers | Yes, via your API credentials |
| Procore-official connection | No (Procore’s AI = Helix, in-product) | No — BYO credentials, admin-installed |
| Reacts when an RFI or submittal lands | No | Yes, via webhooks/polling |
| Morning cross-project digest, unprompted | No | Yes, on a schedule |
| Works while your laptop is closed | No | Yes (cloud) |
| Emails architects, reviewers, leadership | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 + server upkeep | AI agents from $35/mo |
Claude over a community server is a query console for your projects. Carly is a project coordinator that works the clock between site visits.
Frequently Asked Questions
Does Claude work with Procore?
Not officially. There’s no Procore connector in Claude’s directory and no Procore-built MCP server — Procore’s AI investment goes into its in-platform Helix layer (Copilot, Agents, Agent Builder) instead. Community MCP servers that wrap Procore’s REST API exist and Claude can use them, but they’re unofficial, need your own developer app credentials, and require a company admin to authorize the app.
What is Procore Helix?
Procore’s own AI layer: Copilot for retrieval and summarization, Insights, prebuilt Agents, and Agent Builder (open beta) for custom agents from natural-language prompts — bolstered by the ~$168M Datagrid acquisition completed January 2026 for submittal-review and RFI automation. It all runs inside Procore and doesn’t connect to Claude or the rest of your stack.
How would I connect Claude to Procore?
Create a developer app at developers.procore.com (OAuth 2.0), have your company admin install and authorize it, then run a community MCP server with those credentials and add it to Claude Desktop or Claude Code as a custom connector. It works for in-chat queries; there are no triggers.
Can Claude watch for new RFIs or overdue submittals?
No — Claude can’t receive Procore’s webhooks and only acts inside a conversation you start. For RFI alerts, due-date nudges, and cross-project digests that run unattended, you need a trigger-based agent like Carly. AI agents start at $35/month.
More: Claude + JobNimbus · Claude connectors · Can Claude send emails · Claude vs Carly · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
