Contractor Foreman by Cotlet
REMOTE · COTLET.DEV · 2 COMPONENTS
Projects, estimates, daily logs and invoices in Contractor Foreman.
Available components
Last scanned (1 hour ago)
Scores higher than 57% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cotlet_browser_click). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 14600 tokens (~136/item across 107 items; 106 tools + 1 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 check failed: schema churn in the 1 day we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% 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 108 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 24 Oct 26 0
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “cotlet_balance” was removed ▼ security
- Tool “cotlet_browser_connect” was removed ▼ security
- Tool “cotlet_browser_sessions” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_change_order_items” rewrote its description, which is the text the model reads security
- Tool “add_estimate_items” rewrote its description, which is the text the model reads security
- Tool “add_invoice_items” rewrote its description, which is the text the model reads security
- Tool “add_project_note” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_click” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_close” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_navigate” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_open” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_press” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_read” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_screenshot” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_scroll” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_select” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_type” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_upload” rewrote its description, which is the text the model reads security
- Tool “create_bill” rewrote its description, which is the text the model reads security
- Tool “create_change_order” rewrote its description, which is the text the model reads security
- Tool “create_contact” rewrote its description, which is the text the model reads security
- Tool “create_daily_log” rewrote its description, which is the text the model reads security
- Tool “create_estimate” rewrote its description, which is the text the model reads security
- Tool “create_expense” rewrote its description, which is the text the model reads security
- Tool “create_inspection” rewrote its description, which is the text the model reads security
- Tool “create_invoice” rewrote its description, which is the text the model reads security
- Tool “create_lead” rewrote its description, which is the text the model reads security
- Tool “create_opportunity” rewrote its description, which is the text the model reads security
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “create_punchlist” rewrote its description, which is the text the model reads security
- Tool “create_purchase_order” rewrote its description, which is the text the model reads security
- Tool “create_rfi” rewrote its description, which is the text the model reads security
- Tool “create_service_ticket” rewrote its description, which is the text the model reads security
- Tool “create_share_link” rewrote its description, which is the text the model reads security
- Tool “create_sub_contract” rewrote its description, which is the text the model reads security
- Tool “create_todo” rewrote its description, which is the text the model reads security
- Tool “create_work_order” rewrote its description, which is the text the model reads security
- Tool “delete_change_order” rewrote its description, which is the text the model reads security
- Tool “delete_estimate” rewrote its description, which is the text the model reads security
- Tool “delete_invoice” rewrote its description, which is the text the model reads security
- Tool “get_bill” rewrote its description, which is the text the model reads security
- Tool “get_change_order” rewrote its description, which is the text the model reads security
- Tool “get_clock_status” rewrote its description, which is the text the model reads security
- Tool “get_contact” rewrote its description, which is the text the model reads security
- Tool “get_daily_log” rewrote its description, which is the text the model reads security
- Tool “get_estimate” rewrote its description, which is the text the model reads security
- Tool “get_expense” rewrote its description, which is the text the model reads security
- Tool “get_inspection” rewrote its description, which is the text the model reads security
- Tool “get_invoice” rewrote its description, which is the text the model reads security
- Tool “get_job_costing” rewrote its description, which is the text the model reads security
- Tool “get_opportunity” rewrote its description, which is the text the model reads security
- Tool “get_project” rewrote its description, which is the text the model reads security
- Tool “get_punchlist” rewrote its description, which is the text the model reads security
- Tool “get_purchase_order” rewrote its description, which is the text the model reads security
- Tool “get_rfi” rewrote its description, which is the text the model reads security
- Tool “get_service_ticket” rewrote its description, which is the text the model reads security
- Tool “get_sub_contract” rewrote its description, which is the text the model reads security
- Tool “get_submittal” rewrote its description, which is the text the model reads security
- Tool “get_time_card” rewrote its description, which is the text the model reads security
- Tool “get_todo” rewrote its description, which is the text the model reads security
- Tool “get_work_order” rewrote its description, which is the text the model reads security
- Tool “list_bills” rewrote its description, which is the text the model reads security
- Tool “list_change_orders” rewrote its description, which is the text the model reads security
- Tool “list_contacts” rewrote its description, which is the text the model reads security
- Tool “list_cost_codes” rewrote its description, which is the text the model reads security
- Tool “list_cost_items” rewrote its description, which is the text the model reads security
- Tool “list_daily_logs” rewrote its description, which is the text the model reads security
- Tool “list_estimates” rewrote its description, which is the text the model reads security
- Tool “list_expenses” rewrote its description, which is the text the model reads security
- Tool “list_inspections” rewrote its description, which is the text the model reads security
- Tool “list_invoices” rewrote its description, which is the text the model reads security
- Tool “list_leads” rewrote its description, which is the text the model reads security
- Tool “list_opportunities” rewrote its description, which is the text the model reads security
- Tool “list_payments” rewrote its description, which is the text the model reads security
- Tool “list_project_crew_hours” rewrote its description, which is the text the model reads security
- Tool “list_project_files” rewrote its description, which is the text the model reads security
- Tool “list_project_notes” rewrote its description, which is the text the model reads security
- Tool “list_projects” rewrote its description, which is the text the model reads security
- Tool “list_punchlists” rewrote its description, which is the text the model reads security
- Tool “list_purchase_orders” rewrote its description, which is the text the model reads security
- Tool “list_rfis” rewrote its description, which is the text the model reads security
- Tool “list_schedule_tasks” rewrote its description, which is the text the model reads security
- Tool “list_service_tickets” rewrote its description, which is the text the model reads security
- Tool “list_sub_contracts” rewrote its description, which is the text the model reads security
- Tool “list_submittals” rewrote its description, which is the text the model reads security
- Tool “list_time_cards” rewrote its description, which is the text the model reads security
- Tool “list_todos” rewrote its description, which is the text the model reads security
- Tool “list_work_orders” rewrote its description, which is the text the model reads security
- Tool “record_inspection_result” rewrote its description, which is the text the model reads security
- Tool “record_payment” rewrote its description, which is the text the model reads security
- Tool “remove_estimate_items” rewrote its description, which is the text the model reads security
- Tool “send_change_order” rewrote its description, which is the text the model reads security
- Tool “send_estimate” rewrote its description, which is the text the model reads security
- Tool “send_invoice” rewrote its description, which is the text the model reads security
- Tool “update_change_order” rewrote its description, which is the text the model reads security
- Tool “update_daily_log” rewrote its description, which is the text the model reads security
- Tool “update_estimate” rewrote its description, which is the text the model reads security
- Tool “update_invoice” rewrote its description, which is the text the model reads security
- Tool “update_project” rewrote its description, which is the text the model reads security
- Tool “update_schedule_task” rewrote its description, which is the text the model reads security
- Tool “update_service_ticket_status” rewrote its description, which is the text the model reads security
- Tool “update_todo” rewrote its description, which is the text the model reads security
- Tool “update_work_order_status” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 68
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 24 Oct 2026 · Probed https://cotlet.dev/mcp/v1/contractor-foreman
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cotlet.dev | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6afd7585ee8e24a40f5683c10835ec990a8 |
| SANs: *.cotlet.dev, cotlet.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cotlet.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| cotlet.dev. | present | 2371 | 13 | Verified |
| cotlet.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cotlet.dev/mcp/v1/contractor-foreman | Verified | 200 | |
| http (plaintext) | http://cotlet.dev/mcp/v1/contractor-foreman | HTTPS enforced | 301 | https://cotlet.dev/mcp/v1/contractor-foreman |
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.
cotlet_apps Cotlet: apps I can use ~89
The apps of the user's workspace and whether each works now: access granted or requested, the app account in the user's Cloud Browser (connected, signed out, not enabled for agents), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Only this app, e.g. skool. |
No output schema declared.
No examples provided.
cotlet_browser_click Click on the page ~121
Clicks a link, button or other element of the current page in the user's Contractor Foreman Cloud Browser, by its number in the page's element list, and returns the URL and title after the click. It acts as the user on that site. Buttons that pay or buy and buttons on account or sign-in pages are refused. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | yes | The element's number in the element list of the current page. |
No output schema declared.
No examples provided.
cotlet_browser_close Close the browser ~46
Ends the session in the user's Contractor Foreman Cloud Browser: the browser keeps its cookies, goes to sleep and the per-minute charge stops. Returns the session's minutes and credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cotlet_browser_navigate Go to a page ~101
Opens a public http or https address in the user's Contractor Foreman Cloud Browser and returns the URL and title it ended on. Only Contractor Foreman pages open. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public http or https address, e.g. https://example.com. In an app's browser, a page of that app. |
No output schema declared.
No examples provided.
cotlet_browser_open Open the browser ~131
Wakes the user's Contractor Foreman Cloud Browser, a real Chrome hosted on Cotlet and signed in to Contractor Foreman as the user. Use it for what the Contractor Foreman tools do not cover. Opens `url` when given and returns the page's URL and title. The user watches every step live. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | – | A public http or https address, e.g. https://example.com. In an app's browser, a page of that app. |
No output schema declared.
No examples provided.
cotlet_browser_press Press a key ~110
Presses one key on the current page in the user's Contractor Foreman Cloud Browser, on the element that has focus: Tab to the next field, Enter to send, Escape to close a dialog or pop-up, arrows to move through a suggestion list. Returns the URL and title after it. Enter on account pages is refused. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The key. |
No output schema declared.
No examples provided.
cotlet_browser_read Read the page ~99
Returns the current page of the user's Contractor Foreman Cloud Browser: its readable text, up to 20,000 characters, and a numbered list of its links, buttons and fields. Field values, cookies and storage are never returned. On a page longer than that, both start near where it is scrolled to. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cotlet_browser_screenshot See the page ~77
Returns a JPEG image of the visible part of the current page in the user's Contractor Foreman Cloud Browser, with its URL and title: boards, canvases and layouts that the page text does not show. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cotlet_browser_scroll Scroll the page ~177
Scrolls the current page in the user's Contractor Foreman Cloud Browser with the mouse wheel, as a person does: down or up by `screens` viewport heights (default 0.8), to the top or the bottom, or until element `element` is in view. Content that loads on scroll appears, and the next read lists it. Returns the URL, title and scroll position (at_top, at_bottom). Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Where to scroll. Default: down. |
| element | integer | – | Scroll until this element of the element list is in view. |
| screens | number | – | How far, in viewport heights, for down and up. Default: 0.8. |
No output schema declared.
No examples provided.
cotlet_browser_select Choose from a list ~124
Chooses an option of a drop-down list on the current page in the user's Contractor Foreman Cloud Browser, by the list's number in the element list and the option's label as read lists it (or its value). Returns the URL and title after it. Card fields and account pages are refused. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | yes | The element's number in the element list of the current page. |
| option | string | yes | The option. |
No output schema declared.
No examples provided.
cotlet_browser_type Type on the page ~150
Types text into a field of the current page in the user's Contractor Foreman Cloud Browser, by the field's number in the page's element list, and with `submit` presses Enter. Returns the URL and title after it. Password, card and one-time code fields and sign-in pages are refused: the user fills those in themselves. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | yes | The element's number in the element list of the current page. |
| submit | boolean | – | Press Enter after typing, e.g. to search. |
| text | string | yes | The text to type. |
No output schema declared.
No examples provided.
cotlet_browser_upload Upload a file ~153
Puts files into a file field of the current page in the user's Contractor Foreman Cloud Browser, or into the file picker that an upload button opens, by its number in the element list. A file is given as {"url": "https://..."} for a file online or {"file_id": "..."} for one uploaded to Cotlet first; up to 10 files, 20 MB each. Returns the URL and title after it. Every started minute of the session costs credits; it ends when closed or 3 minutes after the last call in the browser.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | yes | The element's number in the element list of the current page. |
| files | array | yes | The files. |
No output schema declared.
No examples provided.
cotlet_get_call Cotlet: check a call ~76
Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | call_id from the earlier call |
No output schema declared.
No examples provided.
cotlet_report_issue Cotlet: report a bug or a missing feature ~276
Sends a report straight to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a tool, field or app the task needed and Cotlet lacks. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| app | – | – | App slug the report is about, e.g. 'skool'. |
| call_id | – | – | call_id of the call that went wrong, if any. |
| client | – | – | Agent or tool sending this, e.g. 'Claude Code'. |
| description | string | yes | What you tried, what you expected and what happened, with the error text if there was one. No passwords, tokens or other secrets. |
| kind | string | yes | bug: a tool did the wrong thing or returned wrong data. error: a call failed or returned an error you could not get past. feature_request: something new the user wants. missing_feature: an app is her… |
| title | string | yes | One line, e.g. 'skool_list_members stops after 50 members'. |
| tool | – | – | Tool or endpoint name, e.g. 'skool_list_members'. |
No output schema declared.
No examples provided.
cotlet_request_apps Cotlet: request access to apps ~102
Requests access to apps for the user's workspace, as Request access in the console: a live app is granted at once, any other goes to the Cotlet team, who answer within 72 hours. Takes app slugs as listed at https://cotlet.dev/api/v1/apps. Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | yes | App slugs, e.g. ["skool", "substack"]. |
No output schema declared.
No examples provided.
cotlet_upload_file Cotlet: upload a file for a tool ~115
Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL works once. Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | MIME type, e.g. image/jpeg. |
| name | string | – | File name, e.g. photo.jpg. |
No output schema declared.
No examples provided.
cotlet_whoami Cotlet: who am I ~63
The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call and its credit balance. Free. Needs the user's Cotlet API key or sign-in.
Input schema present but exposes no named parameters.
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 ~211
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 ~203
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 ~204
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 ~168
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. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.
| 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.
How do I install the Contractor Foreman by Cotlet MCP server?
Contractor Foreman by Cotlet is a hosted endpoint at https://cotlet.dev/mcp/v1/contractor-foreman, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cotlet.dev
claude mcp add --transport http dev-cotlet-contractor-foreman 'https://cotlet.dev/mcp/v1/contractor-foreman'
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 hosted endpoint (https://cotlet.dev/mcp/v1/contractor-foreman).
Is the Contractor Foreman by Cotlet MCP server safe to use?
Contractor Foreman by Cotlet scores 68 out of 100 on VerifyMCP. 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 106 tools: cotlet_whoami, cotlet_apps, cotlet_request_apps, cotlet_get_call, cotlet_upload_file, and 101 more. Their descriptions and schemas cost roughly 14,404 tokens of context every time the server is loaded.
Does the Contractor Foreman by Cotlet MCP server require authentication?
No. We connected to Contractor Foreman by Cotlet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.