Contractor Foreman by Cotlet
PYPI · CONTRACTOR-FOREMAN-API-MCP · 3 COMPONENTS
Projects, estimates, daily logs and invoices in Contractor Foreman.
Available components
Last scanned (1 day ago)
Scores higher than 76% of PyPI servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 35 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to cotletdev/contractor-foreman-api-mcp-server). View diagnostics → Pass
- License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 12393 tokens (~136/item across 91 items; 89 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 91 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/contractor-foreman-api-mcp@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | cotletdev/contractor-foreman-api-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/cotletdev/contractor-foreman-api-mcp-server/.github/workflows/publish.yml@refs/tags/v1.0.2 |
| Rekor log index | 3440923831 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c8ffc7ffe3e029c8868bc362323949bd0d1cd3faec452502b8553a940ad2580f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_change_order_items Add change order items ~98
Adds priced line items to a change order or change order request. Adds line items at the end of the change order's first section: name, type (material, labor, equipment, subcontractor, other), quantity, unit, unit cost in dollars and markup percent. The app computes totals. Returns the saved items and the new total.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order_id | string | yes | From list_change_orders. |
| items | array | yes | – |
No output schema declared.
No examples provided.
add_estimate_items Add estimate items ~140
Adds priced line items to an existing estimate. Adds line items at the end of an estimate section (the first one unless section_id says otherwise). Each item has a name, a type (material, labor, equipment, subcontractor, other), quantity, unit, your unit cost in dollars and a markup percent. Contractor Foreman computes the totals. cost_code_id comes from list_cost_codes. Returns the saved items and the new estimate total.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | string | yes | From list_estimates or create_estimate. |
| items | array | yes | – |
| section_id | string | – | From get_estimate. Default: the first section. |
No output schema declared.
No examples provided.
add_invoice_items Add invoice items ~97
Adds priced line items to an invoice. Adds plain priced lines at the end of an invoice: name, type, quantity, unit, unit cost in dollars, markup percent. Items billed from an estimate, change order or schedule of values are added in the app. Returns the saved items, the new total and the balance due.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | From list_invoices or create_invoice. |
| items | array | yes | – |
No output schema declared.
No examples provided.
add_project_note Add project note ~91
Adds a note to a project's Notes tab. Writes a note on a Contractor Foreman project's Notes tab as the signed-in user, with an optional title. It is visible to the company's users with access to the project. Nobody is notified. Returns the saved note.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The project's numeric id (list_projects). |
| text | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
create_bill Create bill ~197
Records a vendor bill with its line items, optionally against a project. Enters a bill from a vendor in Contractor Foreman: the vendor's invoice number, bill and due date, subject, notes and line items (description, quantity, unit, unit cost, cost type). With a project_id the cost shows in that project's job costing. The bill starts Open and nothing is paid or sent. Returns the saved bill.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_date | string | – | YYYY-MM-DD. Default: today. |
| due_date | string | – | YYYY-MM-DD. |
| items | array | yes | Line items. The total is the sum of quantity times unit cost. |
| notes | string | – | – |
| number | string | yes | The vendor's invoice number. |
| project_id | integer | – | The project the cost belongs to. |
| subject | string | – | – |
| vendor_id | integer | yes | A vendor's contact_id (list_contacts type vendor). |
No output schema declared.
No examples provided.
create_change_order Create change order ~212
Creates a change order or change order request on a project, with line items. Saves a new change order (status open) or change order request (status draft) on a project, for the project's customer. description records the reason. items are priced lines (name, type, quantity, unit, unit cost in dollars, markup percent, cost code). The app computes the total. Nothing is sent. send_change_order emails it after your OK, update_change_order sets the status.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Default: today. |
| description | string | – | Why it changes: who asked, when, what. |
| items | array | – | – |
| kind | string | – | request = a change order request (COR) to price before it becomes a change order. |
| number | string | – | Your own number. Default: the app's next, or COR-<requests on the project + 1>. |
| project_id | string | yes | From list_projects. |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_contact Create contact ~189
Adds a customer, employee, contractor, vendor or misc contact to the Directory. Creates a Contractor Foreman Directory record as the Add drawer does. Employees need a first and last name, contractors and vendors a company name, the others a name or a company. The record gets no app access and nobody is invited or emailed. Giving an employee a login stays a step in the app. Returns the new contact_id.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| address2 | string | – | – |
| cell | string | – | – |
| city | string | – | – |
| company_name | string | – | Required for contractors and vendors. |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| phone | string | – | – |
| state | string | – | – |
| type | string | yes | What kind of contact. |
| zip | string | – | – |
No output schema declared.
No examples provided.
create_daily_log Create daily log ~346
New daily log on a project: work notes, people, deliveries, weather notes and delays. Adds a daily log to the project for the date you give (arrival 07:00 unless you say otherwise) and returns it as get_daily_log shows it. Contractor Foreman records the weather for the date and the project address itself, and weather_notes sits next to it. notes must not be empty. people takes a headcount per crew or free text. The log reaches no client or crew and update_daily_log can edit it, so this tool runs without asking. One project can have several logs on one date: check list_daily_logs first.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_time | string | – | Arrival on site, e.g. 07:00 or 7:00 AM. |
| date | string | yes | Log date. |
| departure_time | string | – | Departure from site, e.g. 15:30. |
| jobsite_notes | string | – | Jobsite condition notes. |
| materials_delivered | array | – | Materials delivered or used, one line each. |
| notes | string | yes | Work done and site notes (the log's Work Performed). |
| people | – | – | Crews, subcontractors and visitors on site: headcount per crew, or free text. |
| project_id | string | yes | project_id from list_projects. |
| schedule_delay | string | – | What else held the schedule up. Marks a schedule delay. |
| visitors | string | – | Visitors on site (inspector, owner, architect). |
| weather_delay | string | – | What the weather delayed. Marks a weather delay. |
| weather_notes | string | – | Your own notes next to the recorded weather. |
No output schema declared.
No examples provided.
create_estimate Create estimate ~204
Creates a draft estimate on a project or for a customer, with priced line items. Saves a new estimate in the Estimating status, unit-price billing, dated today. With project_id it belongs to that project and its customer. Without one, customer_id is required. items are priced lines (name, type, quantity, unit, unit cost in dollars, markup percent, cost code). The app computes totals. Nothing is sent: send_estimate does that after your OK. More lines later with add_estimate_items, other fields with update_estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Directory customer id. Needed without a project. |
| description | string | – | Scope shown on the estimate. |
| exclusions | string | – | – |
| expire_date | string | – | – |
| inclusions | string | – | – |
| items | array | – | – |
| project_id | string | – | From list_projects. Its customer is used. |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_expense Create expense ~203
Records an expense (receipt, purchase, fee) with amount, date, vendor and project. Enters an expense in Contractor Foreman as the signed-in user: name, amount, date, vendor, project, cost type, reason and whether it is billable to the customer. The project is required by the app, and the expense shows in that project's job costing. No receipt file is attached. Returns the saved expense.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | In the account currency. |
| billable | boolean | – | Bill it on to the customer. |
| date | string | – | YYYY-MM-DD. Default: today. |
| name | string | yes | What was bought or paid. |
| project_id | integer | yes | The project the cost belongs to (list_projects). The app refuses an expense without one. |
| reason | string | – | – |
| type | string | – | – |
| vendor_id | integer | – | The vendor's contact_id (list_contacts type vendor). |
No output schema declared.
No examples provided.
create_inspection Create inspection ~151
Logs an inspection on a project with type, date, agency, inspector and notes. Creates a Contractor Foreman inspection in Draft status on a project: inspection type, day, agency (internal, county, city or independent agency), inspector and notes. record_inspection_result sets pass, fail or re-inspect afterwards. Nobody is notified. Returns the saved inspection.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | – |
| date | string | – | Inspection day, YYYY-MM-DD. Default: today. |
| inspected_by | string | – | Inspector or office. |
| notes | string | – | – |
| project_id | integer | yes | The project being inspected. |
| type | string | yes | e.g. Framing, Rough Electrical. |
No output schema declared.
No examples provided.
create_invoice Create invoice ~205
Creates a draft invoice for a project or customer, with priced line items. Saves a new invoice in the Draft status. With project_id it bills that project's customer. Without one, customer_id is required. A description needs due_date in the same call. items are plain priced lines (name, type, quantity, unit, unit cost in dollars, markup percent). It is not sent. update_invoice with status submitted marks it sent and lets record_payment take payments. send_invoice emails it after your OK.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Directory customer id. Needed without a project. |
| description | string | – | Shown on the invoice. Needs due_date in the same call. |
| due_date | string | – | – |
| invoice_date | string | – | Default: today. |
| items | array | – | – |
| number | string | – | Your own number. Default: the app's next. |
| project_id | string | – | From list_projects. Its customer is billed. |
No output schema declared.
No examples provided.
create_lead Create lead ~163
Adds a sales lead with contact details and a pipeline stage. Creates a lead in the Contractor Foreman Directory as the Leads Add drawer does: a name or a company, contact details, address and the stage (received by default). Nobody is emailed. Returns the new contact_id, which list_leads and get_contact read.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| address2 | string | – | – |
| cell | string | – | – |
| city | string | – | – |
| company_name | string | – | – |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| phone | string | – | – |
| stage | string | – | – |
| state | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
create_opportunity Create opportunity ~233
Adds a sales opportunity for a customer with stage, score, budget and expected sale date. Creates an opportunity in Contractor Foreman as the Opportunities Add drawer does, for a customer from the Directory. It is assigned to the signed-in user. Nobody is emailed. The opportunity number must be unique. Without one it gets OPP- and the UTC date and time (OPP-261021-1213). Returns the saved opportunity.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| budget | number | – | Expected value in the account currency. |
| city | string | – | – |
| customer_id | integer | yes | A customer's contact_id (list_contacts type customer). |
| est_sales_date | string | – | Expected sale date, YYYY-MM-DD. |
| name | string | yes | – |
| number | string | – | Your opportunity number. Left out: OPP- and the UTC date and time, as OPP-261021-1213. |
| project_type | string | – | – |
| score | integer | – | – |
| stage | string | – | – |
| state | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
create_project Create project ~215
New project for a customer, with number, type, stage, address and dates. Adds a project in the stage you give (default pending) for a customer from your Directory. Without number the account's next project number is used. Accounts that number projects by hand need one. The project reaches nobody outside your company, so this tool runs without asking. Returns the project as get_project shows it.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| customer_id | string | yes | The customer's contact_id from list_contacts. |
| description | string | – | – |
| end_date | string | – | – |
| name | string | yes | Project name, e.g. Kitchen remodel - Oak St. |
| number | string | – | Project number. Default: the next number when the account numbers projects itself. |
| start_date | string | – | – |
| state | string | – | – |
| status | string | – | – |
| street | string | – | – |
| street2 | string | – | – |
| type | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
create_punchlist Create punchlist ~99
New, empty punchlist on a project. Adds an empty punchlist to the project and returns it as get_punchlist shows it. Items cannot be added through this tool yet, so add them in Contractor Foreman. Nobody is assigned or notified, so this tool runs without asking.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Punchlist name, e.g. Final walkthrough - kitchen. |
| project_id | string | yes | project_id from list_projects. |
No output schema declared.
No examples provided.
create_purchase_order Create purchase order ~172
Creates a draft purchase order to a supplier with line items, optionally for a project. Creates a Contractor Foreman purchase order in Draft status, ordered by the signed-in user: subject, supplier, project, order date, notes and line items (description, quantity, unit, unit cost, cost type). The supplier is not notified. Sending the PO stays a step in the app. Returns the saved order.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Line items. The total is the sum of quantity times unit cost. |
| notes | string | – | – |
| order_date | string | – | YYYY-MM-DD. Default: today. |
| project_id | integer | – | The project the order is for. |
| subject | string | yes | – |
| vendor_id | integer | yes | The supplier's contact_id (list_contacts type vendor). |
No output schema declared.
No examples provided.
create_rfi Create RFI ~168
Drafts a request for information on a project, with the question and a reply-by date. Creates a Contractor Foreman RFI in Draft status on a project, from the signed-in user, dated now: title, question, the area and plan sheet it refers to and the date a response is needed by. It is not sent to anyone. Submitting it to the architect or owner stays a step in the app. Returns the saved RFI.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_sheet | string | – | Plan sheet number. |
| project_id | integer | yes | The project the question is about. |
| question | string | yes | The information requested. |
| reference_area | string | – | Area or element it refers to. |
| response_needed_by | string | – | YYYY-MM-DD. |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_service_ticket Create service ticket ~210
Opens a service ticket for a customer, optionally scheduled for a date and time. Creates a Contractor Foreman service ticket for a customer from the Directory: title, description, an optional project and the planned service date and time. The service address is the customer's (or the project's). With a date it is Scheduled, without one Unscheduled. Technicians are assigned in the app. The customer is not notified. Returns the saved ticket, with service_time on the 12-hour clock (02:00 PM).
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | A customer's contact_id (list_contacts type customer). |
| description | string | – | What the customer reported. |
| project_id | integer | – | Links the ticket to a project. The service address is then the project's. |
| service_date | string | – | Planned visit, YYYY-MM-DD. The ticket is then Scheduled. |
| service_time | string | – | Planned time on the 24-hour clock, like 13:30. |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_share_link Create share link ~122
Makes a short internal link that opens an estimate, change order or invoice for your signed-in team. The panel's Share Internal Link: a short URL that opens the record in the Contractor Foreman app. Only people who sign in to your Contractor Foreman company can open it. It is not a public page for the customer. To get a document to the customer, send_estimate, send_change_order and send_invoice email the PDF.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | estimate_id, change_order_id or invoice_id. |
| record_type | string | yes | – |
No output schema declared.
No examples provided.
create_sub_contract Create sub-contract ~173
Creates a draft sub-contract with a subcontractor on a project. Creates a Contractor Foreman sub-contract in Draft status, issued by the signed-in user, for a project and a subcontractor from the Directory, with subject, agreement number and date. This API cannot add scope items, terms or send it for signature. Those stay steps in the app. The subcontractor is not notified. Returns the saved sub-contract.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_number | string | yes | Your agreement number, e.g. the project number and a sequence (BP-2001-07). |
| contractor_id | integer | yes | The subcontractor's contact_id (type contractor). |
| date | string | – | YYYY-MM-DD. Default: today. |
| project_id | integer | yes | The project the work is for. |
| subject | string | yes | – |
No output schema declared.
No examples provided.
create_todo Create to-do ~145
New to-do, optionally on a project, with due date, priority and assignees. Adds a to-do and returns it as get_todo shows it. Assignees see it in their Contractor Foreman app.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | array | – | contact_id values from list_contacts of the employees or contacts who should do it. |
| description | string | – | – |
| due_date | string | – | – |
| due_time | string | – | e.g. 09:00 or 2:30 PM. |
| name | string | yes | What has to be done. |
| priority | string | – | – |
| project_id | string | – | Project from list_projects. |
No output schema declared.
No examples provided.
create_work_order Create work order ~163
Creates an Open work order on a project with subject, description and dates. Creates a Contractor Foreman work order in Open status on a project, issued by the signed-in user, for the project's customer: subject, description, start and end date. It has no line items. Nobody is notified, and sending it to the customer stays a step in the app. update_work_order_status moves it on. Returns the saved order.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What has to be done. |
| end_date | string | – | YYYY-MM-DD, not before start_date. Default: today. |
| project_id | integer | yes | The project the work is on. |
| start_date | string | – | YYYY-MM-DD. Default: today. |
| subject | string | yes | – |
No output schema declared.
No examples provided.
delete_change_order Delete change order ~60
Deletes a change order or change order request for good. Deletes the change order and its items. It cannot be undone. To keep the record, use update_change_order with status denied instead.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order_id | string | yes | From list_change_orders. |
No output schema declared.
No examples provided.
delete_estimate Delete estimate ~77
Deletes an estimate for good. Deletes the estimate and its line items, as Delete in the estimate's menu does. Records made from it (projects, change orders, invoices) stay. It cannot be undone. To keep the history, use update_estimate with status lost instead.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | string | yes | From list_estimates. |
No output schema declared.
No examples provided.
delete_invoice Delete invoice ~71
Deletes an invoice that has no payments, for good. Deletes the invoice and its items. It cannot be undone. An invoice with payments recorded is refused. For that one, or to keep the record, use update_invoice with status write_off or denied.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | From list_invoices. |
No output schema declared.
No examples provided.
get_bill Get bill ~80
One vendor bill with its line items, dates, total, balance due and status. Reads one Contractor Foreman bill by bill_id: what list_bills gives plus the payment terms and every line item with description, cost type, quantity, unit, unit cost, total and cost code.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | integer | yes | bill_id from list_bills. |
No output schema declared.
No examples provided.
get_change_order Get change order ~78
One change order or request with description, status, total and line items. Everything on one change order or change order request: number, title, status, project, customer, date, the reason (description), the estimate it came from, time delay and the priced line items.
| Name | Type | Req | Description |
|---|---|---|---|
| change_order_id | string | yes | From list_change_orders. |
No output schema declared.
No examples provided.
get_clock_status Get clock status ~94
Who is clocked in right now, whether you are, and this and last week's crew hours. Reads the Contractor Foreman Time Cards dashboard: the employees clocked in at this moment with their project and clock-in time, whether the signed-in user is clocked in (and that card's id), and the regular, overtime and total hours of the whole team and of the signed-in user for this week and last.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_contact Get contact ~113
One Directory record in full: contact details, status, services, terms and additional contacts. Reads one Contractor Foreman Directory record by contact_id: everything list_contacts gives plus a second phone, fax, website, status, services, tags, default payment terms, referral source, the date it was added and the additional contacts kept under it. For leads also stage and quality. Login details, wages and personal ids of employees are left out.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | contact_id from list_contacts or list_leads. |
No output schema declared.
No examples provided.
get_daily_log Get daily log ~107
One daily log: work notes, people and visitors, materials, equipment, weather and delays. Returns one daily log in full: the work performed, crew notes and employees on site, visitors, materials, equipment used with hours, the weather Contractor Foreman recorded for the date and the address (temperatures in both scales, the day's conditions), your weather notes and any weather or schedule delay. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_log_id | string | yes | daily_log_id from list_daily_logs. |
No output schema declared.
No examples provided.
get_estimate Get estimate ~108
One estimate with customer, dates, terms, totals and every line item. Everything on one estimate: status, project, customer contact, estimate and expiry dates, billing type, description, inclusions, exclusions, terms, totals in dollars and the line items by section (type, quantity, unit, unit cost, markup, total, cost code). section_id is what add_estimate_items takes to put new items in a section.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate_id | string | yes | From list_estimates. |
No output schema declared.
No examples provided.
get_expense Get expense ~68
One expense with amount, date, vendor, project, cost type, cost code and reason. Reads one Contractor Foreman expense by expense_id: what list_expenses gives plus the cost code and the reason written on it.
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | integer | yes | expense_id from list_expenses. |
No output schema declared.
No examples provided.
get_inspection Get inspection ~59
One inspection with type, project, date, result, agency, inspector and notes. Reads one Contractor Foreman inspection by inspection_id, with the same fields as list_inspections.
| Name | Type | Req | Description |
|---|---|---|---|
| inspection_id | integer | yes | inspection_id from list_inspections. |
No output schema declared.
No examples provided.
get_invoice Get invoice ~89
One invoice with customer, dates, terms, line items, payments and balance due. Everything on one invoice: status, project, customer and their email, invoice and due dates, terms, retainage, total, amount paid and balance due in dollars, the line items and every payment recorded against it (date, amount, method, status).
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | From list_invoices. |
No output schema declared.
No examples provided.
get_job_costing Get job costing ~177
Estimated and actual cost per cost code for one project, with the difference and totals. Sums the project's Job Cost Actual report per cost code: contract value, estimated cost (from the Schedule of Values or the approved estimates, plus change orders), actual cost split into bills, expenses, time cards and equipment, the difference (estimated minus actual, negative means over) and the amount invoiced. Time card hours are priced at labor_rate (default burden_rate). Costs with no cost code are under Unassigned. Amounts are in dollars. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_from | string | – | Estimated cost from the Schedule of Values or the approved estimates. Default: the project's own setting. |
| labor_rate | string | – | Rate that prices time card hours as labor cost. |
| project_id | string | yes | project_id from list_projects. |
No output schema declared.
No examples provided.
get_opportunity Get opportunity ~75
One opportunity in full: customer contact, stage, score, budget, notes and last activity. Reads one Contractor Foreman opportunity by opportunity_id: what list_opportunities gives plus the customer's email and phone, the notes and the subject of the last sales activity.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | integer | yes | opportunity_id from list_opportunities. |
No output schema declared.
No examples provided.
get_project Get project ~104
One project: customer, address, stage, dates, contract amounts, costs, billing and retainage. Returns one project. The revised contract amount is the original contract plus approved change orders, as the project shows it. Costs are budgeted, committed and actual. Billing is invoiced, paid and outstanding invoices, with retainage held shown apart. Amounts are in dollars. Use project_id from list_projects.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | project_id from list_projects. |
No output schema declared.
No examples provided.
get_punchlist Get punchlist ~96
One punchlist: project, address, customer and how many items are open and completed. Returns one punchlist with its project, the project address and customer, the number of open and completed items, who made it and when. The items themselves are not returned yet: open the punchlist in Contractor Foreman to see them. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| punchlist_id | string | yes | punchlist_id from list_punchlists. |
No output schema declared.
No examples provided.
get_purchase_order Get purchase order ~78
One purchase order with supplier, dates, status and its line items. Reads one Contractor Foreman purchase order by purchase_order_id: what list_purchase_orders gives plus every line item with description, cost type, quantity, unit, unit cost, total and cost code.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_order_id | integer | yes | purchase_order_id from list_purchase_orders. |
No output schema declared.
No examples provided.
get_rfi Get RFI ~59
One RFI with its question, dates, answer and status. Reads one Contractor Foreman RFI by rfi_id, with the same fields as list_rfis.
| Name | Type | Req | Description |
|---|---|---|---|
| rfi_id | integer | yes | rfi_id from list_rfis. |
No output schema declared.
No examples provided.
get_service_ticket Get service ticket ~79
One service ticket with customer, service address, schedule, technicians and priority. Reads one Contractor Foreman service ticket by service_ticket_id: what list_service_tickets gives plus the priority, planned duration, service address, the customer's phone and the hours logged on it.
| Name | Type | Req | Description |
|---|---|---|---|
| service_ticket_id | integer | yes | service_ticket_id from list_service_tickets. |
No output schema declared.
No examples provided.
get_sub_contract Get sub-contract ~107
One sub-contract with subcontractor, amounts, retainage, scope of work and items. Reads one Contractor Foreman sub-contract by sub_contract_id: what list_sub_contracts gives plus the scope of work text (HTML as saved) and the items added in the app, with quantity, unit cost, total and cost code. paid and balance come back null here. list_sub_contracts has them.
| Name | Type | Req | Description |
|---|---|---|---|
| sub_contract_id | integer | yes | sub_contract_id from list_sub_contracts. |
No output schema declared.
No examples provided.
get_submittal Get submittal ~90
One submittal with plan sheet, specification section, status, dates and its items. Reads one Contractor Foreman submittal by submittal_id: what list_submittals gives plus the plan sheet and specification section and each submitted item with manufacturer, status and the date it was sent back.
| Name | Type | Req | Description |
|---|---|---|---|
| submittal_id | integer | yes | submittal_id from list_submittals. |
No output schema declared.
No examples provided.
get_time_card Get time card ~82
One time card or crew sheet with hours per employee and cost code. Reads one Contractor Foreman time card by timecard_id: what list_time_cards gives plus one entry per employee and cost code with the hours worked and the entry's notes. A crew sheet lists every crew member.
| Name | Type | Req | Description |
|---|---|---|---|
| timecard_id | integer | yes | timecard_id from list_time_cards. |
No output schema declared.
No examples provided.
get_todo Get to-do ~67
One to-do: description, project, priority, status, due date, assignees and checklist. Returns one to-do with its description, due date and time, assignees and checklist items. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| todo_id | string | yes | todo_id from list_todos. |
No output schema declared.
No examples provided.
get_work_order Get work order ~76
One work order with project, customer, status, dates, location, notes and items. Reads one Contractor Foreman work order by work_order_id: what list_work_orders gives plus the location, notes and line items with quantity, unit cost and total.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order_id | integer | yes | work_order_id from list_work_orders. |
No output schema declared.
No examples provided.
list_bills List bills ~119
Vendor bills with vendor, project, dates, total, balance due and status. Reads the Contractor Foreman Bills list, newest first: bill number, subject, vendor, project, bill date, due date, total, balance still due and status (Open, Paid). Filter by project or search. get_bill adds the line items.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous call. |
| limit | integer | – | – |
| project_id | integer | – | Only this project's records. |
| search | string | – | Words to look for. |
No output schema declared.
No examples provided.
list_change_orders List change orders ~231
Change orders and change order requests, newest first, with status, project and total. The Change Orders list: number, title, kind (change_order or request), status, project, customer, date and total in dollars. Filter by project, kind, status or a search over title and number. Archived ones only with include_archived. Change orders have the statuses open, pending_approval, on_hold, approved, denied, billed. Requests have draft, on_hold, approved, denied, closed. A status that does not fit the kind stops the call. get_change_order gives the line items.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous call. |
| include_archived | boolean | – | – |
| kind | string | – | request = change order requests (COR) not yet turned into a change order. |
| limit | integer | – | – |
| project_id | string | – | Only this project's (list_projects). |
| search | string | – | Matches the title or number. |
| status | string | – | With kind all or change_order, a change order status. Request statuses need kind request. |
No output schema declared.
No examples provided.
list_contacts List contacts ~154
Customers, employees, contractors, vendors and misc contacts from the Directory. Reads the Contractor Foreman Directory: active contacts with their type, name, company, title, email, phone, cell and address. Filter by type or search by name, company, email or phone. contact_id is the id other tools ask for as customer_id, vendor_id, contractor_id or employee_id. Leads have their own tool, list_leads.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous call. |
| limit | integer | – | – |
| search | string | – | Name, company, email or phone to look for. |
| type | string | – | Only this kind of contact. Left out: all of them, leads excluded. |
No output schema declared.
No examples provided.
How do I install the Contractor Foreman by Cotlet MCP server?
Contractor Foreman by Cotlet runs locally as a PyPI package, launched with uvx contractor-foreman-api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · contractor-foreman-api-mcp
claude mcp add dev-cotlet-contractor-foreman -- uvx contractor-foreman-api-mcp
What is the Contractor Foreman by Cotlet MCP server?
Contractor Foreman by Cotlet is an MCP server listed in the public MCP registry as dev.cotlet/contractor-foreman. Projects, estimates, daily logs and invoices in Contractor Foreman. This page covers its PyPI package (contractor-foreman-api-mcp).
Is the Contractor Foreman by Cotlet MCP server safe to use?
Contractor Foreman by Cotlet scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Contractor Foreman by Cotlet MCP server expose?
Contractor Foreman by Cotlet exposes 89 tools: add_change_order_items, add_estimate_items, add_invoice_items, add_project_note, create_bill, and 84 more. Their descriptions and schemas cost roughly 12,278 tokens of context every time the server is loaded.
Is the Contractor Foreman by Cotlet MCP server still maintained?
Contractor Foreman by Cotlet is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Contractor Foreman by Cotlet MCP server under?
Contractor Foreman by Cotlet declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.