Skip to content

Procore MCP connector

The Procore connector lets Claude, ChatGPT, Cursor and the Elaichi Agent work with your Procore projects, budgets, budget line items and checklist responses, with every action running as the signed-in person and recorded in an audit log.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Procore to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Procore once

  1. Open Connections, choose Add connection, and pick Procore.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Procore app, then approve. Procore needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

procore
Procore
1Password
360learning
7shifts
Acquire
Active Ants
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Procore MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Procore MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Procore MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Procore to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Procore through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Project management

    See every active project across your companies

    Ask which Procore projects are open under each company and get the list back without clicking through portfolios one by one.

  • Finance

    Add budget line items from an estimate

    Paste the lines from an approved estimate and have them created as budget line items on the right Procore project, then check the budget totals.

  • Finance

    Lock a budget once it is approved

    When the owner signs off, lock the Procore budget so nobody adjusts it, and unlock it later when a change order comes through.

  • Quality

    Record checklist responses from the field

    Capture inspection answers as checklist responses on the project, and correct a single response later if the inspector picked the wrong option.

  • Safety

    Review checklist responses before a walkthrough

    Pull the latest safety checklist responses for a site and get a short summary of what failed so the superintendent knows where to look.

  • Payroll

    Keep timecard time types current

    Rename or adjust a timecard time type in Procore when the labor agreement changes so crews log hours against the right category.

Try asking

  • “List open projects under Acme Builders in Procore”
  • “Add these estimate lines as budget line items on the Riverside job”
  • “Summarize failed checklist responses on the Oak Street project this week”

See all 125 Procore tools below

Compare

Elaichi vs Zapier MCP vs Composio for Procore

All three can connect Procore to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Procore, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Procore tools Allow or restrict single Procore tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Procore call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Procore tools for your AI agents

125 tools are ready to call through Elaichi's MCP endpoint the moment you connect Procore, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Procore gets you

6 screens from the product, each doing one job for your Procore account.

The agent

Ask about Procore projects in plain language.

Get live answers about Procore budgets and checklist responses without opening a single project.

  • projects
  • budget line items
  • checklist responses
  • companies

Ask Elaichi to work across your apps.

List open projects under Acme Builders in Procore

Add these estimate lines as budget line items on the Riverside job

Summarize failed checklist responses on the Oak Street project this week

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint connects Procore to every client.

Claude, ChatGPT and Cursor reach Procore through one governed endpoint, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

125 Procore tools, ready without code.

Projects, budgets, line items and checklist responses are covered with no custom code.

  • Create a Procore oauth token
  • List all Procore oauth tokens
  • Procore oauth tokens revoke
  • List all Procore webhook hooks
ElaichiTools
Tool Action Description
Create a Procore oauth token Create Get or refresh a Procore OAuth access token. Returns: access_token, token_type, expires_in, refresh_token, created_at. Required: grant_type, client_id, client_secret. Use grant_type=authorization_code for a new token, grant_type=refresh_token to refresh an existing one, or grant_type=client_credentials for Procore Service Account authentication.
List all Procore oauth tokens List Get details about the current Procore access token, such as the resource owner it belongs to and its remaining lifetime. Returns: resource_owner_id, scopes, expires_in_seconds, application, created_at.
Procore oauth tokens revoke Revoke Revoke a Procore access token, invalidating both the access token and its refresh token; the authorization server returns success whether the token was revoked or was already invalid. Requires the Procore-Company-Id header. Returns an empty response body on success. Required: token, client_id, client_secret.
List all Procore webhook hooks List List Procore webhook hooks scoped to a company and/or project. Returns: id, api_version, destination_headers, destination_url, owned_by_company_id, owned_by_project_id, owned_by_user_id, namespace, ulid, timestamp, metadata, user_id, company_id, project_id, event_type, resource_name, resource_id. Required: company_id or project_id — hooks cannot be listed without a scope.
Create a Procore webhook hook Create Create a Procore webhook hook that delivers event payloads to a destination URL. Returns: id, api_version, destination_headers, destination_url, owned_by_company_id, owned_by_project_id, owned_by_user_id, namespace, ulid, timestamp, metadata, user_id, company_id, project_id, event_type, resource_name, resource_id. Required: hook (with api_version and destination_url), plus either company_id or…

Toolboxes

Every team gets its own Procore toolbox.

Finance, field and project teams each see only the Procore tools their work needs.

  • Project management
  • Finance
  • Preconstruction
  • Field operations
ElaichiToolboxes
Name Source template Tools Created

Project management toolbox

Procore · companies and projects

Procore starter 18 Mar 4, 2026

Finance toolbox

Procore · budgets and budget line items

— 9 Mar 2, 2026

Preconstruction toolbox

Procore · estimates and budget setup

— 24 Feb 27, 2026

Field operations toolbox

Procore · checklist responses

Procore starter 6 Feb 19, 2026

Safety toolbox

Procore · inspection checklists

— 31 Jan 30, 2026

Payroll toolbox

Procore · timecard time types

— 12 Jan 22, 2026

Shared connections

Share a Procore connection, never a credential.

One person connects Procore, teammates work through it, nobody else sees a client secret.

  • Commercial projects
  • Residential
  • Finance
  • Field ops
ElaichiConnections
Connection Scope Status Access
PR

Procore (Commercial projects)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PR

Procore (Residential)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PR

Procore (Finance)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PR

Procore (Field ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PR

Procore (Safety)

Connected by Ryan Hayes

Personal • Active Not shared
PR

Procore (Payroll)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Procore action has a name on it.

See who locked a budget or changed a checklist response, when, and on which project.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Procore Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Procore Projects Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Procore Projects List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Procore checklists into a digest.

Checklist responses are fetched, grouped by project, drafted, approved by a person, then posted back.

Procore digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch projects

    Procore

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Procore

    Queued

Collections and dashboards

Procore health, computed on a schedule.

Budget line items created over 14 days, split by team, with no model doing the math.

Procore health

Refreshed 4 minutes ago · every 15 minutes · from the projects collection

Live

Projects

1,284 ↓ 12%

Budget line items

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Projects created

Last 14 days

By team

Share of activity

Commercial projects 34%

Residential 27%

Finance 21%

Field ops 18%

FAQ

Frequently asked questions

How do I connect Procore to Claude?

First connect Procore in Elaichi. Procore requires an OAuth application registered inside your own Procore account, so an administrator does that once, copies the client ID and secret it produces into Elaichi, and then signs in to Procore and approves access. Next, open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Nobody else on your team ever has to see or handle that client ID or secret again.

Does Procore work with ChatGPT and Cursor as well as Claude?

Yes. Once Procore is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Procore once and every client picks it up.

What can an AI agent actually do with my Procore data?

With Procore connected, an agent can list your companies and the projects under each one, read a project budget and its line items, add new budget line items, lock or unlock a budget, and create, read, update or delete checklist responses. It can also list and update timecard time types. Short, concrete asks such as "add these three lines to the Riverside budget" work better than long paragraphs.

Does connecting Procore give the AI access to every company and project?

No. Every call into Procore runs as the person who signed in, so the agent sees only the companies, projects and budgets that person can already open in Procore. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond what Procore itself allows that person.

Can my team share one Procore connection?

Yes. One administrator connects Procore in Elaichi and shares the connection with a team, and nobody else handles the client ID, secret or any Procore credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every budget change or checklist response.

Can I stop an agent from deleting or changing things in Procore?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Procore budgets while blocking the ability to delete budget line items, delete checklist responses or unlock a budget. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Procore connection when someone leaves?

When you offboard someone in Elaichi, their access to Procore through every AI client ends at once. A Procore connection shared with the team keeps working for everyone else. If you ever want it gone entirely, disconnecting Procore once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Procore MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Procore is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Procore?

Yes. Both let Claude, ChatGPT or Cursor use Procore. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Procore call.

How is Elaichi different from Composio for Procore?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Procore: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Procore in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.