
tylerilunga/procore-mcp-server
API development이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
MCP server exposing the full Procore REST API for Claude Desktop and Claude Code
개요
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 , , and any MCP-compatible client. 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: - Node.js 18+ - A Procore Developer Portal account - An OAuth app with grant type - Set your redirect URI to http://localhost Copy the example env file and fill in your credentials: By default the server exposes the , 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: Coverage is identical in both modes; only the size of the advertised tool list differs.
README
원문 README의 일부입니다. 원문 보기.
Procore 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",
설치
This server does not publish a one-line install command.
Open the repository installation guide MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →설정
{
"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"
}
}
}
}