Procore MCP server
Commit Aug 21, 2026Exposes the full Procore REST API to AI assistants through automated tool generation and discovery tools.
Also known as TylerIlunga/procore-mcp-server
- Stars
- 19
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Aug 21, 2026
- License
- MIT
What is Procore MCP?
Procore exposes the full Procore REST API to AI assistants through automated tool generation and discovery tools.
Summary generated from the project's README
About Procore MCP server
Connecting construction management data to AI assistants is what this server enables for engineers and project managers. It exposes the entire Procore REST API to clients like Claude Desktop and Claude Code by converting the massive Procore OpenAPI specification into usable tools. Users can interact with their Procore accounts through an AI interface to manage projects and company data without manual API requests.
To use this server, you need a Procore Developer Portal account, an OAuth app with Authorization Code grant type, and specific environment variables including your client ID, client secret, and company ID. The system operates using seven meta-tools for discovery, such as procore_discover_categories and procore_search_endpoints, which allow the AI to find the right data. While the default mode uses procore_api_call to execute requests, you can opt-in to a mode that registers every single endpoint as an individual tool if your model has a large enough context window.
Setup requires Node.js 18+ and a local build process to parse the large OpenAPI spec file. Once authenticated via a browser-based OAuth flow, the server handles authentication headers, rate limits, and pagination automatically.
What you can do with it
- 1Discovering available API endpointsAn AI assistant can search through the Procore API to find specific categories or endpoints needed for a task.
- 2Executing specific API operationsDevelopers can instruct an AI to perform any Procore API call using a single unified tool.
- 3Managing project configurationsUsers can update the runtime configuration to switch between different company or project IDs.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
PROCORE_CLIENT_IDPROCORE_CLIENT_SECRETPROCORE_COMPANY_IDPROCORE_TOOL_MODE
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletylerilunga/procore-mcp-server is public and reachablegithub.com/tylerilunga/procore-mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-21github.com/tylerilunga/procore-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubProcore MCP Server
MCP server that exposes the full Procore REST API to AI assistants like Claude. Built with TypeScript and the Model Context Protocol SDK.
Works with Claude Desktop, Claude Code, and any MCP-compatible client.
What it does
A build-time parser converts Procore's OpenAPI spec into a compact catalog, then auto-generates individual MCP tools for every API operation. At runtime, 7 meta-tools let the AI discover and call any Procore endpoint:
| Tool | Purpose |
|---|---|
procore_discover_categories |
List API categories with endpoint counts |
procore_discover_endpoints |
List endpoints in a category |
procore_search_endpoints |
Full-text search across all endpoints |
procore_get_endpoint_details |
Get full parameter schema for an endpoint |
procore_api_call |
Execute any Procore API call |
procore_get_config |
Show current config and auth status |
procore_set_config |
Set runtime config (company_id, project_id) |
Prerequisites
- Node.js 18+
- A Procore Developer Portal account
- An OAuth app with Authorization Code grant type
- Set your redirect URI to
http://localhost
Setup
git clone https://github.com/TylerIlunga/procore-mcp-server.git
cd procore-mcp-server
npm install
Copy the example env file and fill in your credentials:
cp .env.example .env
PROCORE_CLIENT_ID=your_client_id
PROCORE_CLIENT_SECRET=your_client_secret
PROCORE_COMPANY_ID=your_company_id
By default the server exposes the 7 discovery tools, and every Procore
endpoint is reached through procore_api_call. Registering a dedicated tool
per endpoint instead emits roughly 4.7 MB (~1.2M tokens) of tool definitions —
more than any current model's context window — so that surface is opt-in:
PROCORE_TOOL_MODE=all
Coverage is identical in both modes; only the size of the advertised tool list
differs. If you switch to all and are migrating from before v2.0.0, see
data/tool-renames.json for the old -> new tool name map.
You'll need Procore's OpenAPI spec file placed at specs/combined_OAS.json. This file is not included in the repo due to its size (~54MB). You can obtain it from Procore's API documentation.
Build the catalog and compile TypeScript:
npm run build
Authenticate with Procore (opens browser for OAuth):
npm run auth
Start the server:
npm start
Claude Desktop configuration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"procore": {
"command": "node",
"args": ["/absolute/path/to/procore-mcp-server/dist/src/index.js"],
"env": {
"PROCORE_CLIENT_ID": "your_client_id",
"PROCORE_CLIENT_SECRET": "your_client_secret",
"PROCORE_COMPANY_ID": "your_company_id"
}
}
}
}
Claude Code configuration
Add to .mcp.json in your project root:
{
"mcpServers": {
"procore": {
"command": "node",
"args": ["/absolute/path/to/procore-mcp-server/dist/src/index.js"],
"env": {
"PROCORE_CLIENT_ID": "your_client_id",
"PROCORE_CLIENT_SECRET": "your_client_secret",
"PROCORE_COMPANY_ID": "your_company_id"
}
}
}
}
Project structure
src/
auth/ OAuth token exchange, refresh, storage
api/ HTTP client with auth, rate limits, retries
catalog/ Endpoint catalog loading, search, filtering
tools/ MCP tool handlers and registration
scripts/
generate-catalog.ts Parse OAS into catalog
generate-tools-manifest.ts Generate per-endpoint MCP tools
validate-catalog.ts Validate catalog integrity
data/ Build output (committed): catalog.json, endpoint details, tools manifest
specs/ Source OAS file (gitignored — too large for the repo)
How it works
-
Build time:
scripts/generate-catalog.tsparses the ~54MB Procore OpenAPI spec (3,155 operations) and produces a compactdata/catalog.jsonplus individual endpoint detail files indata/endpoint-details/.scripts/generate-tools-manifest.tsthen generates a tools manifest with one named MCP tool per API operation — 2,929 in total, after collapsing older-version duplicates of the same path.Each generated tool carries a structured description covering what it acts on, when to reach for it, which parent ids to resolve first, what it returns, and how it fails. Endpoints Procore has deprecated are registered with their sunset date in the description and a
(Deprecated)title. The interactive/oauth/*endpoints are not registered as tools —npm run authowns that flow — but remain reachable throughprocore_api_call. -
Auth: Run
npm run authonce to complete the OAuth flow in your browser. Tokens are saved to~/.procore-mcp/tokens.jsonand auto-refresh when expired. -
Runtime: The MCP server loads the catalog and registers the 7 discovery tools (plus the full per-endpoint surface when
PROCORE_TOOL_MODE=all). When an AI assistant calls a tool, the server maps it to the correct Procore API endpoint, injects auth headers, handles rate limits and pagination, and returns the response.
Inspiration
Built to help my girlfriend, a construction engineer who uses Procore daily.
License
MIT
Procore MCP questions
How do I authenticate with Procore?
You need to run the command npm run auth which will open a browser to complete the OAuth flow.
What are the prerequisites for setting up this server?
You need Node.js 18+, a Procore Developer Portal account, and an OAuth app with the Authorization Code grant type.
Can I use this with Claude Desktop?
Yes, you can configure Claude Desktop by adding the server details to your claude_desktop_config.json file.
Does the server support all Procore API endpoints?
Yes, the server provides access to the full Procore REST API, either through discovery tools and a general API call tool or by opting into a mode that registers every endpoint as an individual tool.