---
name: procore-api-connector
description: Connect an AI agent to Procore project data safely through the Procore REST API (OAuth 2.0 app installed by a company admin, sandbox first, read-only) to list projects, RFIs and submittals, find overdue items and whose court the ball is in, and produce digests. Use when the user's company runs Procore and asks the agent to read RFIs, submittals, daily logs or project lists, "conectar Procore con Claude/ChatGPT", or to automate Procore follow-ups.
---

# Procore through the API (read-only first)

## Know the landscape (October 2026)
- Procore's own AI (Procore Helix, the agents from the Datagrid acquisition: deep search, submittal review, RFI, daily log, contract review; Agent Builder) runs **inside** Procore. At Groundbreak (21 Oct 2026) Procore showed more agents (submittal, procurement log, Procore AI Go voice app) and mentioned its first MCP connection, with the Compass prequalification platform.
- Procore does **not** publish an official general-purpose MCP server for external agents as of this date. External agents reach Procore through the REST API: directly (`scripts/procore_client.py`), through a community MCP server (review its code; many expose write tools), or through an integration platform the company already trusts.

## Access (the user's company admin does this; never ask for passwords)
1. Create an app in the Procore Developer Portal (developers.procore.com). Start in the **sandbox** the portal provides.
2. Authentication: OAuth 2.0 (authorization code for acting as a user; a service-account style grant for unattended jobs, if the company allows it). The admin installs the app in the company account and grants it access to the tools needed (RFIs, Submittals...) with read permission.
3. Every request carries the `Procore-Company-Id` header. Keep the token in an environment variable (`PROCORE_TOKEN`), never in the chat or a file.

## Procedure
1. Confirm company id, project id and what the user wants to see.
2. Run, sandbox first, with the sandbox URL shown in the app's Developer Portal page (typically `https://sandbox.procore.com`): `python scripts/procore_client.py projects --base <sandbox URL>`, then `rfis --project <id>` or `submittals --project <id>`. Production base: `https://api.procore.com`.
3. Check endpoint versions in developers.procore.com/reference if a call returns 404 (Procore versions resources one by one: v1.0, v1.1, v2.0).
4. Present: totals by status, overdue open items sorted by due date, ball-in-court owners, and drafted (not sent) follow-up messages.
5. For recurring use, propose the routine `procore-open-items`.

## Output
- CSV per resource + digest. For RFIs, offer the `rfi-writer` skill to improve drafts before they are created in Procore by a human.

## Never
- Never create, edit, respond to or close RFIs/submittals through the API without an explicit request and per-item approval; the API acts with the app's permissions and leaves an audit trail in the company's name.
- Never use production before the sandbox test passes.
- Never move Procore data to another service the company has not approved.