Delete Signature
/rest/v1.0/projects/{project_id}/time_and_material_entries/signatures/{id}Inspect fields and contract
Procore MCP
A Procore MCP connector in development for projects, RFIs, submittals and commercial records. Explore planned coverage and join the waitlist.
Construction
What is Procore MCP?
MCP XYZ is building an independent Procore MCP connector for teams that want an AI assistant to work with authorised construction project records through the Model Context Protocol. Planned coverage includes projects, RFIs, submittals, daily logs and commercial records. Access is waitlist-based while provider approval and live acceptance are pending.
Use the catalogue to check the operations and fields your work needs. If an existing connector is missing a useful action, tell us about it when joining the waitlist. Your software’s permissions and API limits still apply.
Procore workflows to explore
Find project and directory records
Planned access to projects, company information, people and project directories, within the connected account’s authorised permissions.
Inspect documented operationsExplore RFIs, submittals and daily logs
Inspect documented requests for information, submittals, drawing records and daily logs before choosing a project workflow.
Inspect documented operationsReview change events and commitments
Explore documented commercial records, including change events, commitments and prime contracts. Live acceptance is still pending.
Inspect documented operationsExample request to try after setup and validation
“Find the open RFIs for this project.”
Getting access to Procore MCP
New access starts with the Procore waitlist. Tell us which assistant you use and the work you want to do. We’ll contact you about relevant access updates; joining does not create an account or guarantee an invitation date.
Procore is in development. Live use requires an authorised developer app, installation in the relevant company, applicable provider approval and live acceptance.
The implemented connection paths support a developer-managed service account or user OAuth. Acceptance must confirm the account, region, permissions and intended agent use. The detailed catalogue tracks documented coverage; these workflows have not passed live business testing.
Production use needs the applicable Procore app and use-case approval. Procore’s Agentic APIs programme is a separate approved pilot. Ordinary REST credentials do not establish access to that pilot or approval for every agent or bulk-data use.
External presigned transfers, large uploads, some environments and provider-side token revocation have outstanding limits. A documented file operation does not mean a complete file workflow has been verified.
Procore API usage guidelines
Procore Agentic APIs guidance
Procore MCP questions
What is the Procore MCP from MCP XYZ?
It is an independent Procore connector in development by Jiffi. It is intended to make documented Procore API operations available to authorised AI assistants through the Model Context Protocol. Planned coverage includes projects, RFIs, submittals, daily logs and commercial records.
Is this an official Procore MCP server?
No. MCP XYZ is an independent product by Jiffi. This listing does not imply Procore endorsement or approval. Production use requires the applicable Procore app and use-case approval; Procore’s Agentic APIs programme is a separate approved pilot.
Can I connect Procore to Claude or ChatGPT?
MCP XYZ authentication and catalogue discovery have been checked with Claude. Procore business requests have not passed live acceptance, and ChatGPT acceptance has not been verified. Join the waitlist with your preferred assistant and workflow so we can assess the requirements.
Does the Procore MCP support RFIs, submittals and change events?
Those resources are included in the documented operation catalogue below, alongside projects, directories, commitments and other records. Catalogue coverage describes retained API contracts, not verified live workflows. Provider permissions, account region and applicable approval still determine what can be used.
What happens when I join the Procore waitlist?
We save your contact details and Procore interest, and notify the MCP XYZ team. We will contact you about relevant access updates. Joining does not create an account, grant Procore access or promise a release date. Existing invited users can still log in.
Documented coverage
Operations and fields
3,294 documented business operations across retained API versions. Open a contract to inspect its parameters, fields, sources and unresolved behaviour. No provider request is made here.
3,294 operations match. Showing 341–360.
Delete Time And Material Timecard
/rest/v1.0/projects/{project_id}/time_and_material_timecards/{id}Inspect fields and contractBulk Delete Time and material equipment logs
/rest/v1.0/projects/{project_id}/time_and_material_equipment_logs/bulk_destroyInspect fields and contractDelete a Time And Material Notification
/rest/v1.0/projects/{project_id}/time_and_material_notificationsInspect fields and contractDelete a Time And Material Entry
/rest/v1.0/projects/{project_id}/time_and_material_entries/{id}Inspect fields and contractDelete timecard entry (Project)
/rest/v1.0/projects/{project_id}/timecard_entries/{id}Inspect fields and contractDelete Signature
/rest/v1.0/projects/{project_id}/timesheets/signatures/{id}Inspect fields and contractDelete Timesheet
/rest/v1.0/projects/{project_id}/timesheets/{id}Inspect fields and contractDelete Timecard Entries
/rest/v1.0/projects/{project_id}/timesheetsInspect fields and contractRemove a user from the project
/rest/v1.0/projects/{project_id}/users/{id}/actions/removeInspect fields and contractDelete from project
/rest/v1.1/projects/{project_id}/vendors/{id}/actions/removeInspect fields and contractDelete project vendor insurance
/rest/v1.0/projects/{project_id}/vendors/{vendor_id}/insurances/{id}Inspect fields and contractDelete from project
/rest/v1.0/projects/{project_id}/vendors/{id}/actions/removeInspect fields and contractDelete Visitor Log
/rest/v1.0/projects/{project_id}/visitor_logs/{id}Inspect fields and contractDelete Waste Log
/rest/v1.0/projects/{project_id}/waste_logs/{id}Inspect fields and contractDelete Weather Log
/rest/v1.0/projects/{project_id}/weather_logs/{id}Inspect fields and contractDelete Project Segment Item
/rest/v1.0/projects/{project_id}/work_breakdown_structure/segments/{segment_id}/segment_items/{id}Inspect fields and contractBulk Delete Project Segment Items
/rest/v1.0/projects/{project_id}/work_breakdown_structure/segments/{segment_id}/segment_items/bulk_destroyInspect fields and contractDelete a classification
/rest/v1.0/projects/{project_id}/work_classifications/{id}Inspect fields and contractDelete Work Log
/rest/v1.0/projects/{project_id}/work_logs/{id}Inspect fields and contractWhat has been verified
- Documented coverage
- 3,294 business operations across retained Procore API versions, with four authentication endpoints tracked separately. Deprecated and beta contracts are labelled. These counts describe documentation, not proven live workflows.
- Agent connection
- Actual Claude Desktop and web connection, model-selected platform utility calls, renewal after natural token expiry and revoked-access rejection passed. Codex and Claude Code authentication and discovery were also checked. These tests made no provider business requests.
- Live business workflows
- Awaiting an authorised Procore app and account, live acceptance and the applicable approval for the intended use. Catalogue search passed in Claude Desktop and web; full contract retrieval passed in Claude web. Procore business requests have not been verified.
More software, the same workspace
Explore Unleashed MCP
The Unleashed waitlist is open. Inspect its documented coverage and account requirements.
Explore Unleashed