Procore

What this connects to: the Procore REST API (https://api.procore.com/rest/...): companies, projects, directory, RFIs, submittals, daily logs, the Documents tool, budgets and commitments. Every call runs as the Procore user who authorized the connector and sees what that user sees. This first version only reads.

Start with procore_list_companies for the company id, then procore_list_projects. Every company-scoped tool takes company_id; it is sent as the Procore-Company-Id header, which Procore requires (calls without it are refused with 400).

Setup (OAuth 2.0 authorization code)

1. At https://developers.procore.com sign in, Create New App, and add an OAuth credential of type Web server application (authorization code). Set the redirect URI to <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
2. Copy the production client ID and client secret into PROCORE_CLIENT_ID and PROCORE_CLIENT_SECRET.
3. A company administrator installs the app in the company (Company Admin > App Management > Install Custom App, with the app's version key), otherwise the company's data is not reachable.
4. On the connector page click Authorize with Provider and sign in to Procore. Tokens are refreshed automatically.

Sandbox: developer sandboxes use https://sandbox.procore.com and https://login-sandbox.procore.com; change the base URL and the OAuth URLs in the connector settings to test there.

Paging: lists return 100 items per page; pass page (and per_page). The _headers of the answer carry total and a link header; _pagination.nextUrl is absent on the last page.

Rate limits: 3,600 requests per hour per app and user, with short bursts limited too; a 429 says when to retry.

Pitfalls: a 403 means the user's permission template lacks access to that tool (RFIs, Budget, Documents) on the project. Budget and commitments need the Financials tools enabled on the project. Ids are integers.