Procore MCP Server

Connect Procore to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for interacting with the Procore API (projects, RFIs, submittals, documents, and budget). The procore mcp server is what makes that connection.

What the server does

This project implements a Model Context Protocol (MCP) server that connects Claude (and other MCP‑aware clients) to the Procore API. It exposes tools for working with:

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Projects — RFIs
• Submittals — Documents
• Description — List Procore projects for the authenticated client, optionally filtered by company_id
• Inputs — - company_id (optional, integer): Filter projects by company
• RFIs — list_rfis
• Documents — list_folders
• Budget — list_budget_line_items
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — If you created the folder elsewhere, adjust the cd path accordingly

Credentials and setup notes

Configuration is passed through the environment: PROCORE_CLIENT_ID, PROCORE_CLIENT_SECRET, PROCORE_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js: v18+ (recommended) - npm: v9+ (comes with recent Node.js) - Procore Developer account with: - A registered OAuth2 client using Client Credentials flow - API access to the relevant projects/modules (RFIs, Submittals, Documents, Budget, etc.) ---

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Procore.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Procore's toolset — Projects, Submittals, Description and 6 more — is a fair guide to whether it matches your workflow. It is maintained by zeniasupp0rt-cmyk; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.