Procore MCP server Let your AI agent do the Procore paperwork.

ToolWhat it doesAccess

• list_projects Procore projects of your company that you can open, with name and ID. read

  Returns the projects your Procore login can open, 25 to a page by default. Use project_id in every other tool. Projects you have no access to are not listed. Pass next_cursor back as cursor for the next page.

  MCP callprocore_read → list_projects

  REST endpointGET https://cotlet.dev/api/v1/procore/projects

  Parameters

  Parameters: list_projects

  Name	Type	Description
  query string	string	Only projects whose name contains this text.
  limit integer	integer	1 to 50. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "projects": [
      {
        "project_id": "5518204",
        "name": "Harbor Street Offices",
        "number": "HS-24",
        "active": true
      },
      {
        "project_id": "5518377",
        "name": "Elm Court Apartments",
        "number": "EC-25",
        "active": true
      }
    ],
    "next_cursor": null
  }

• list_rfis RFIs of one project with status, RFI Manager, assignees, due date and who has the ball in court. read

  Lists RFIs of one project, newest number first. Each row carries the subject, the status, the RFI Manager, the assignees, the due date, the Ball In Court and the cost and schedule impact. A Standard user sees fewer fields and can open a draft only if they created it. Pass next_cursor back as cursor for the next page.

  MCP callprocore_read → list_rfis

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/rfis

  Parameters

  Parameters: list_rfis

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  status enum	enum	draft, open or closed. Default: all.
  assignee string	string	Only RFIs assigned to this person, by name.
  overdue boolean	boolean	Only open RFIs past their due date.
  limit integer	integer	1 to 50. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "rfis": [
      {
        "rfi_id": "90417",
        "number": 31,
        "subject": "Slab edge at level two stair",
        "status": "open",
        "rfi_manager": "Dana Whitfield",
        "assignees": [
          "Marcus Hale"
        ],
        "ball_in_court": "Marcus Hale",
        "due_date": "2026-11-03",
        "cost_impact": "TBD",
        "schedule_impact": "No"
      },
      {
        "rfi_id": "90402",
        "number": 30,
        "subject": "Door hardware schedule conflict",
        "status": "open",
        "rfi_manager": "Dana Whitfield",
        "assignees": [
          "Priya Nair"
        ],
        "ball_in_court": "Priya Nair",
        "due_date": "2026-11-07",
        "cost_impact": "No",
        "schedule_impact": "No"
      }
    ],
    "next_cursor": null
  }

• get_rfi One RFI with its question, responses, attachments and distribution list. read

  Returns the full question, every response with its author and date, the attachment names, the distribution list and the location, spec section and drawing number. A Standard or Read-Only user sees every response only if the project does not limit them to official responses; otherwise only the official response is returned.

  MCP callprocore_read → get_rfi

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/rfis/{rfi_id}

  Parameters

  Parameters: get_rfi

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  rfi_id string required	string	RFI ID from list_rfis.

  Example input

  {
    "project_id": "project_8c41d2",
    "rfi_id": "rfi_8c41d2"
  }

  Example response

  {
    "rfi_id": "90417",
    "number": 31,
    "subject": "Slab edge at level two stair",
    "status": "open",
    "question": "Drawing S-201 shows the slab edge flush with the stair wall. Detail 4 on S-501 shows a 2 inch step. Which one governs?",
    "location": "Level 2, Stair B",
    "spec_section": "03 30 00",
    "drawing_number": "S-201",
    "responses": [],
    "attachments": [
      "S-201-markup.pdf"
    ],
    "distribution": [
      "Dana Whitfield",
      "Priya Nair"
    ]
  }

• create_rfi Create an RFI as a draft or as open, with subject, question, RFI Manager and assignees. writeasks first

  Creates an RFI. As a draft, the Ball In Court stays with the RFI Manager and nobody else is asked. As open, the assignees get the Ball In Court. Open needs number, subject, assignees, due date and question. Open and draft both need Admin on the RFIs tool, or Standard with the Act as RFI Manager permission; with Standard only, the RFI is saved as a draft for review. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → create_rfi

  REST endpointPOST https://cotlet.dev/api/v1/procore/projects/{project_id}/rfis

  Parameters

  Parameters: create_rfi

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  subject string required	string	Short subject of the RFI.
  question string required	string	The question, in full.
  status enum	enum	draft or open. Default: draft.
  number string	string	RFI number. Needed for an open RFI; duplicates are not allowed.
  rfi_manager string	string	RFI Manager, by name. Default: you.
  assignees array	array	Names of the people who must respond. Needed for an open RFI.
  due_date date	date	Needed for an open RFI.
  location string	string	Location from the project list.
  spec_section string	string	Spec section, e.g. 03 30 00.
  cost_impact enum	enum	yes, yes_unknown, no, tbd or na.
  schedule_impact enum	enum	yes, yes_unknown, no, tbd or na.

  Example input

  {
    "project_id": "5518204",
    "subject": "Roof drain location at gridline D",
    "question": "Drawing A-301 puts the roof drain 2 feet off gridline D. The structural plan shows a beam there. Please confirm the drain location.",
    "status": "draft",
    "spec_section": "22 14 00"
  }

  Example response

  {
    "rfi_id": "90431",
    "number": 32,
    "subject": "Roof drain location at gridline D",
    "status": "draft",
    "rfi_manager": "Dana Whitfield",
    "ball_in_court": "Dana Whitfield"
  }

ToolWhat it doesAccess

• list_submittals Submittals of one project with number, title, spec section, type, status, responsible contractor and ball in court. read

  Lists submittals of one project in log order. Each row carries the number and revision, title, spec section, type, status, responsible contractor, Submit By date and the Ball In Court. Procore sets the Ball In Court to the Submittal Manager when there is no workflow, and to the current workflow step when there is one. Pass next_cursor back as cursor for the next page.

  MCP callprocore_read → list_submittals

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/submittals

  Parameters

  Parameters: list_submittals

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  status string	string	A status name exactly as your project's Submittals log shows it.
  spec_section string	string	Only submittals under this spec section, e.g. 08 71 00.
  overdue boolean	boolean	Only submittals past their Submit By date.
  limit integer	integer	1 to 50. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "submittals": [
      {
        "submittal_id": "70133",
        "number": "08 71 00-1",
        "revision": 0,
        "title": "Door hardware, Level 1 and 2",
        "spec_section": "08 71 00",
        "type": "Product Information",
        "status": "Open",
        "responsible_contractor": "Ridgeline Doors",
        "ball_in_court": "Dana Whitfield",
        "submit_by": "2026-10-30"
      }
    ],
    "next_cursor": null
  }

ToolWhat it doesAccess

• list_punch_list_items Punch list items of one project with location, assignee, final approver, priority and due date. read

  Lists punch list items of one project. Each row carries the title, number, punch manager, assignees, final approver, location, trade, priority, due date and whether it has been sent. Private items appear only if you are the creator, an assignee, on the distribution list or a Punch List Admin. Pass next_cursor back as cursor for the next page.

  MCP callprocore_read → list_punch_list_items

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/punch-list-items

  Parameters

  Parameters: list_punch_list_items

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  assignee string	string	Only items assigned to this person, by name.
  location string	string	Only items at this location.
  priority enum	enum	low, medium or high.
  overdue boolean	boolean	Only items past their due date.
  limit integer	integer	1 to 50. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "items": [
      {
        "item_id": "30871",
        "number": 14,
        "title": "Touch up paint at corridor door frames",
        "location": "Level 1 > Corridor",
        "assignee": "Priya Nair",
        "final_approver": "Dana Whitfield",
        "priority": "Medium",
        "due_date": "2026-11-12",
        "sent": true
      }
    ],
    "next_cursor": null
  }

• create_punch_list_item Add a punch list item with location, assignee, final approver, priority and due date. Nobody is notified until you send. writeasks first

  Creates one punch list item and returns its ID and number. Procore sends no notification on save: assignees and the distribution list hear about the item only after send_punch_list_items. Standard users can assign only a Punch Item Manager, and Read Only users cannot be assigned. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → create_punch_list_item

  REST endpointPOST https://cotlet.dev/api/v1/procore/projects/{project_id}/punch-list-items

  Parameters

  Parameters: create_punch_list_item

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  title string required	string	Title shown in the list.
  location string	string	A location from the project, up to two tiers, e.g. Level 1 > Corridor.
  assignee string	string	Person who resolves the item, by name. Must be in the project directory.
  final_approver string	string	Person who can close the item. Default: you.
  priority enum	enum	low, medium or high.
  due_date date	date	Default: the number of days set in the project settings.
  trade string	string	A trade set up in your company.
  description string	string	What is wrong and how to fix it.

  Example input

  {
    "project_id": "project_8c41d2",
    "title": "title"
  }

  Example response

  {
    "item_id": "30884",
    "number": 15,
    "title": "Replace cracked tile at the lobby threshold",
    "location": "Level 1 > Lobby",
    "assignee": "Priya Nair",
    "priority": "Medium",
    "due_date": "2026-11-12",
    "sent": false
  }

• send_punch_list_items Send every unsent punch list item of a project to its assignees and distribution list by email. writeasks first

  Does what Send All Items does in the Punch List banner: assignees and distribution list members get an email for each unsent item. Returns how many items went out and to whom. After the first send, assignees get daily emails about overdue items, which end after 45 days. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → send_punch_list_items

  REST endpointPOST https://cotlet.dev/api/v1/procore/projects/{project_id}/punch-list-items/send-punch-list-items

  Parameters

  Parameters: send_punch_list_items

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "project_id": "5518204",
    "items_sent": 3,
    "notified": [
      "Priya Nair",
      "Marcus Hale"
    ]
  }

ToolWhat it doesAccess

• list_observations Observations of one project with type, status, priority, assignee and due date. read

  Lists observations of one project. Each row carries the number, title, type, status, priority, trade, assignee, due date and location. Initiated means the observation waits for the assignee, Ready for Review waits for the creator, and Not Accepted has gone back to the assignee. Pass next_cursor back as cursor for the next page.

  MCP callprocore_read → list_observations

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/observations

  Parameters

  Parameters: list_observations

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  status enum	enum	initiated, ready_for_review, not_accepted or closed. Default: all.
  priority enum	enum	low, medium, high or urgent.
  assignee string	string	Only observations assigned to this person, by name.
  limit integer	integer	1 to 50. Default: 25.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "observations": [
      {
        "observation_id": "41250",
        "number": 8,
        "title": "Open floor edge near the loading dock",
        "type": "Safety",
        "status": "ready_for_review",
        "priority": "High",
        "trade": "Concrete",
        "assignee": "Marcus Hale",
        "due_date": "2026-11-04",
        "location": "Level 1 > Loading dock"
      }
    ],
    "next_cursor": null
  }

• create_observation Create an observation with type, priority, assignee, trade, location and due date. writeasks first

  Creates an observation in the status Initiated, which waits for the assignee. Procore does not send observation emails automatically. With no assignee, nobody is notified; adding an assignee and saving triggers an email. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → create_observation

  REST endpointPOST https://cotlet.dev/api/v1/procore/projects/{project_id}/observations

  Parameters

  Parameters: create_observation

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  title string required	string	Title that names the topic.
  type string	string	A type set up in the project.
  assignee string	string	Person who does the work. Must have Standard or Admin on the Observations tool.
  priority enum	enum	low, medium, high or urgent.
  trade string	string	A trade set up in your company.
  location string	string	Location from the project list.
  due_date date	date	Default: the number of days set in the project settings.
  description string	string	What was observed and what the work should be.

  Example input

  {
    "project_id": "project_8c41d2",
    "title": "title"
  }

  Example response

  {
    "observation_id": "41266",
    "number": 9,
    "title": "Missing guardrail at the Level 2 stair",
    "status": "initiated",
    "priority": "Urgent",
    "assignee": "Marcus Hale",
    "due_date": "2026-11-06"
  }

• set_observation_status Move an observation to Ready for Review, Not Accepted or Closed. writeasks first

  The assignee sets Ready for Review, which emails the creator. The creator sets Closed to finish the item; Not Accepted sends it back to the assignee. The call fails if your login is not the right person for that step. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → set_observation_status

  REST endpointPUT https://cotlet.dev/api/v1/procore/projects/{project_id}/observations/{observation_id}/status

  Parameters

  Parameters: set_observation_status

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  observation_id string required	string	Observation ID from list_observations.
  status enum required	enum	ready_for_review, not_accepted or closed.

  Example input

  {
    "project_id": "project_8c41d2",
    "observation_id": "observation_8c41d2",
    "status": "ready_for_review"
  }

  Example response

  {
    "observation_id": "41250",
    "number": 8,
    "status": "closed"
  }

ToolWhat it doesAccess

• get_daily_log The daily log of one project for one day: how many entries each section has, and the manpower entries. read

  Returns the daily log of one project for one day. entries_by_section counts the entries in each section that has any, such as Manpower, Deliveries, Visitors or Notes. The manpower entries come with company, workers, hours and total hours. Collaborator entries that wait for approval are marked pending.

  MCP callprocore_read → get_daily_log

  REST endpointGET https://cotlet.dev/api/v1/procore/projects/{project_id}/daily-log

  Parameters

  Parameters: get_daily_log

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  date date	date	The log day. Default: today.

  Example input

  {
    "project_id": "project_8c41d2"
  }

  Example response

  {
    "date": "2026-11-04",
    "entries_by_section": {
      "Manpower": 2,
      "Deliveries": 1
    },
    "manpower": [
      {
        "company": "Ridgeline Doors",
        "workers": 3,
        "hours": 7,
        "total_hours": 21,
        "location": "Level 1",
        "pending": false
      },
      {
        "company": "Summit Concrete",
        "workers": 4,
        "hours": 8,
        "total_hours": 32,
        "location": "Level 2",
        "pending": false
      }
    ]
  }

• add_manpower_entry Add a manpower entry to the daily log: company, number of workers and hours each. writeasks first

  Adds one entry to the Manpower section of the daily log and returns it with total hours (workers times hours). Creating manpower entries needs Standard or Admin on the Daily Log tool. The entry reaches nobody by itself. By default you confirm each call; you can switch that off for this tool.

  MCP callprocore_write → add_manpower_entry

  REST endpointPOST https://cotlet.dev/api/v1/procore/projects/{project_id}/manpower-entries

  Parameters

  Parameters: add_manpower_entry

  Name	Type	Description
  project_id string required	string	Project ID from list_projects.
  company string required	string	Company or person doing the work. Must be in the project directory.
  workers integer required	integer	Number of workers from that company on the job.
  hours number required	number	Hours each worker worked. Different hours need a separate entry.
  date date	date	The log day. Default: today.
  location string	string	Location from the project list.
  comments string	string	Anything that clarifies the entry.

  Example input

  {
    "project_id": "project_8c41d2",
    "company": "company",
    "workers": 1,
    "hours": 1
  }

  Example response

  {
    "entry_id": "66120",
    "date": "2026-11-04",
    "company": "Summit Concrete",
    "workers": 4,
    "hours": 8,
    "total_hours": 32,
    "location": "Level 2"
  }