Local services & SaaS
ClockShark
Timesheets, schedules and jobs in your ClockShark account.
15 endpoints
Ontraccr has no public API documentation, and its Zapier app has one trigger and one action (checked 17 Nov 2026). Cotlet runs a hosted Ontraccr MCP server with 40 tools that ChatGPT and Claude use in your own Ontraccr account. Approvals, shifts and anything that reaches a client wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Ontraccr. Ontraccr is a trademark of its owner. If Ontraccr's own integrations cover what you need, use them first.
40 tools Read and write
Ontraccr publishes no public API documentation. Its Zapier app lists one trigger, Card Moved, and one action, Create a Board Card. No Ontraccr MCP server and no official ChatGPT or Claude connector was found.
| What you need | Ontraccr on Zapier | By hand | Cotlet |
|---|---|---|---|
| Create or move board cards | Create a card, react to a move | In the board | Create, move, add tasks |
| Approve forms and time cards | Not in the app | One by one | Listed, then approved after your OK |
| Shifts, budgets and equipment | Not in the app | One screen at a time | 40 tools |
| Ask ChatGPT or Claude to do the work | Through Zapier MCP, one action | Copy and paste | Hosted MCP server |
Checked 17 Nov 2026. Sources: Ontraccr on Zapier · Ontraccr integrations · Ontraccr Help Center · Help: Reviewing and approving time cards · Help: Forms pending your approval · Help: Creating shifts in the Field Schedule · Help: Project budget tracking · Help: Project status report · Help: Collect External Signature block · Help: Collect Payment block · Help: Creating cards in boards · Help: Checking equipment in and out
Once, in a browser we host for you.
One address in its settings.
Review Team Cards, then approve them.
Your agent works in your own signed-in Cloud Browser. Approvals, shifts and anything that reaches a client or a crew wait for your OK. Who can see your session
Sign in to Ontraccr in a Cloud Browser. Open app.ontraccr.com/login in your Cotlet Cloud Browser and log in with your own Ontraccr user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
One connector at https://cotlet.dev/mcp/v1 carries Ontraccr and every other app you enable. If you switch Ontraccr on later, refresh the connector and its 40 tools load.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: ontraccr_read One tool per workflow in the Ontraccr Help Center. Reports and searches only read; on tools with an `action`, `list` and `get` read and the rest write after your OK.
Manual and team time entry, Team Cards approval, the Employee Payroll report, Field Schedule shifts and the teams that decide who approves whom.
`list` shows submitted, approved and geofence-breached entries for the users you approve. Approved time goes to payroll. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → approve_time_cards
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/time-cards/approve
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `approve`, `reject`. `list` and `get` only read. |
| user string | string | Whose card. |
| period string | string | Week or dates. |
| note string | string | Optional note. |
{
"action": "action"
} {
"cards": [
{
"user": "Crew member C",
"hours": 45,
"status": "Submitted"
},
{
"user": "Crew member A",
"hours": 42,
"status": "Submitted"
}
]
} Manual Entry must be enabled in clock settings and your role must allow it. Hours feed payroll, so entries wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → enter_time
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/time/enter
| Name | Type | Description |
|---|---|---|
| users array required | array | Team entry: several users. |
| date string required | string | ISO date. |
| start string | string | Start time. |
| end string | string | End time. |
| break_minutes number | number | Break. |
| project string | string | Project. |
| cost_code string | string | Cost code. |
{
"users": [
"Crew member A",
"Crew member B"
],
"date": "2026-11-17",
"start": "07:00",
"end": "15:30",
"break_minutes": 30,
"project": "Maple Street watermain",
"cost_code": "02-200"
} {
"date": "2026-11-17",
"project": "Maple Street watermain",
"cost_code": "02-200",
"entries": [
{
"user": "Crew member A",
"hours": 8
},
{
"user": "Crew member B",
"hours": 8
}
]
} Hours by employee, project, date, work type and cost code, rounded by your company setting or actual. It only reads; paying people stays in your payroll system.
MCP callontraccr_read → run_payroll_report
REST endpointGET https://cotlet.dev/api/v1/ontraccr/payroll-reports/run
| Name | Type | Description |
|---|---|---|
| period string required | string | A preset such as `this_week`, `last_7_days`, or `custom`. |
| from string | string | ISO date, for `custom`. |
| to string | string | ISO date, for `custom`. |
| rounded boolean | boolean | True for rounded hours, false for actual. |
{
"period": "period"
} {
"period": "this_week",
"employees": [
{
"employee": "Crew member A",
"hours": 45
},
{
"employee": "Crew member B",
"hours": 42
}
]
} A published shift reaches the crew. Save as draft to hold it for later assignment. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → schedule_shifts
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/shifts/schedule
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| users array | array | Who works it. |
| start string | string | ISO date and time. |
| end string | string | ISO date and time. |
| project string | string | Project. |
| draft boolean | boolean | Save as draft instead of publishing. |
{
"action": "action"
} {
"shift": "Pipe crew",
"users": [
"Crew member A",
"Crew member B"
],
"start": "2026-11-19T07:00",
"project": "Maple Street watermain",
"draft": false
} Teams decide who approves whose time, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_teams
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/teams/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| team string | string | Team name. |
| supervisors array | array | Users who can approve time cards. |
| members array | array | Members. |
| projects array | array | Projects. |
{
"action": "action"
} {
"team": "Pipe crew",
"supervisors": [
"Site lead"
],
"members": 5,
"saved": true
} Templates, submissions, approvals and the workflow blocks that launch linked forms, collect signatures through DocuSign or send Stripe payment links.
`list` returns the forms where you are the approver, the ones Ontraccr marks with a red dot. An approval moves the form on in its workflow. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → approve_forms
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/forms/approve
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `approve`, `reject`. `list` and `get` only read. |
| form string | string | Form number, for `approve` and `reject`. |
| note string | string | Optional note. |
{
"action": "action"
} {
"pending": [
{
"form": "Change Order",
"number": "CO-0031",
"project": "Maple Street watermain",
"submitted_by": "Site lead"
}
]
} The form must allow a manual trigger. Submitting starts its workflow, which can send it for approval or to other people. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → submit_form
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/form/submit
| Name | Type | Description |
|---|---|---|
| form string required | string | Form template. |
| from string | string | Where it starts: `manual`, `card`, `task` or `equipment`. |
| linked string | string | The card, task or equipment it belongs to. |
| answers object required | object | Field values. |
{
"form": "form",
"answers": "answers"
} {
"form": "Daily Site Report",
"number": "DSR-0412",
"project": "Maple Street watermain",
"submitted": true
} Templates live under Documents > Forms > Templates. Your crews fill them in the field, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_form_templates
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/form-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| name string | string | Form name. |
| type string | string | Form type. |
| fields array | array | Fields and sections. |
| division string | string | Division. |
{
"action": "action"
} {
"form": "Daily Site Report",
"type": "Daily Log",
"fields": 9,
"saved": true
} The Form Trigger block launches linked forms after submit, approval or edit, with linked numbers and mapped fields. It affects every future submission. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_form_workflows
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/form-workflows/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `add_form_trigger`. `list` and `get` only read. |
| form string required | string | The parent form template. |
| triggered_form string | string | Form to launch next. |
| recipients array | array | Who fills it in. |
| shared boolean | boolean | One shared form, or one per user. |
| mapping object | object | Parent fields copied into the new form. |
{
"action": "action",
"form": "form"
} {
"form": "Site Inspection",
"triggered_form": "Deficiency Report",
"shared": true,
"saved": true
} Your DocuSign account must be connected in Settings > Integrations > DocuSign. Each future submission of the form then goes to clients or vendors by secure link, and the signed PDF locks the form data. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → add_signature_step
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/signature-steps
| Name | Type | Description |
|---|---|---|
| form string required | string | Form template, for example Change Order. |
| after string | string | The step it follows, usually Submit or Approval. |
| signers array required | array | Signers in signing order: a fixed email or a form field that holds one. |
{
"form": "form",
"signers": "signers"
} {
"form": "Change Order",
"after": "Approval",
"signers": [
"Client email field"
],
"saved": true
} Needs Stripe linked in Settings > Integrations > Stripe. Each submission then sends the customer a Stripe payment link; `status` reads Pending, Paid or Failed. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → add_payment_step
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/payment-steps
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `add`, `status`. `list` and `get` only read. |
| form string required | string | Form template for `add`, form number for `status`. |
| amount_field string | string | For `add`: the form field with the amount. |
| payer_field string | string | For `add`: the field with the customer email. |
{
"action": "action",
"form": "form"
} {
"form": "SRV-0208",
"amount": 1250,
"status": "Pending"
} Anyone with the link can submit without a login, so publishing waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → publish_external_form
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/external-form/publish
| Name | Type | Description |
|---|---|---|
| form string required | string | Form template. |
{
"form": "form"
} {
"form": "Site Visitor Sign-In",
"url": "https://example.com/f/visitor",
"qr_code": true
} Returns the rows of the export as Ontraccr builds them, the same data as its CSV. Use it for daily log, time and material or inspection summaries.
MCP callontraccr_read → export_form_report
REST endpointGET https://cotlet.dev/api/v1/ontraccr/form-reports/export
| Name | Type | Description |
|---|---|---|
| export string required | string | Export title from Settings > Forms > Exports. |
| from string | string | ISO start date. |
| to string | string | ISO end date. |
| division string | string | Division, if you use several. |
{
"export": "export"
} {
"export": "Daily Log Report",
"rows": [
{
"project": "Maple Street watermain",
"date": "2026-11-16",
"crew_size": 6
}
]
} Boards and card designs, cards moving across statuses, status workflows, card tasks, your own My Tasks list and Advanced Search.
A card is a job, lead, request or anything you track. Moving a card can start the board's workflows, such as copying it or creating tasks. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_cards
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/cards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `move`. `list` and `get` only read. |
| board string required | string | Board title. |
| card string | string | Card title, for `get` and `move`. |
| status string | string | Status column. |
| assigned array | array | Assigned users. |
| linked array | array | Linked project, customer, equipment or material. |
{
"action": "action",
"board": "board"
} {
"board": "Active Jobs",
"card": "Maple Street watermain",
"status": "Ready to Bill",
"saved": true
} The task appears in the assignee's My Tasks, so new and reassigned tasks wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_card_tasks
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/card-tasks/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| board string required | string | Board title. |
| card string required | string | The card. |
| title string | string | Task title. |
| assignees array | array | Users. |
| due_date string | string | ISO date. |
| priority string | string | Priority. |
| status string | string | One of `To Do`, `In Progress`, `Done`. |
{
"action": "action",
"board": "board",
"card": "card"
} {
"card": "Maple Street watermain",
"task": "Book the vac truck",
"assignees": [
"Site lead"
],
"due_date": "2026-11-19",
"status": "To Do"
} My Tasks sorts by due date and covers card and equipment tasks. Completing a task can move its card on. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_my_tasks
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/my-tasks/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `complete`. `list` and `get` only read. |
| task string | string | Task title, for `complete`. |
{
"action": "action"
} {
"tasks": [
{
"task": "Book the vac truck",
"type": "Card Task",
"due": "2026-11-19",
"priority": "High"
}
]
} A board can track any workflow, from jobs to procurement. Statuses become its columns. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_boards
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/boards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| title string | string | Board title, for `create`. |
| card_design string | string | Card type the board uses. |
| statuses array | array | Status columns in order. |
| division string | string | Division, if you use several. |
{
"action": "action"
} {
"board": "Site Equipment Tracker",
"card_design": "Equipment Request",
"statuses": [
"Requested",
"Approved",
"Delivered"
],
"saved": true
} Card designs live under Settings > Boards and are reused across boards, so a change shows on every board that uses the design. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_card_designs
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/card-designs/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| title string | string | Card design title. |
| fields array | array | Text, dropdown, date, number and other fields, with required flags. |
{
"action": "action"
} {
"card_design": "Service Tracker",
"fields": [
"Customer",
"Site address",
"Due date",
"Priority"
],
"saved": true
} A workflow runs on every future card that enters the status, so the agent names the trigger and target first. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_board_workflows
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/board-workflows/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| board string required | string | Board title. |
| type string | string | Workflow type, for example Copy Card When Status Changes. |
| trigger_status string | string | Status that starts it. |
| target_board string | string | Where the copy goes. |
{
"action": "action",
"board": "board"
} {
"board": "Sales",
"workflow": "Copy to Estimating Board",
"trigger_status": "Send to Estimating",
"target_board": "Estimating",
"saved": true
} A board search is built around a card design and can span every board that uses it. Returns the matching cards or forms with their fields.
MCP callontraccr_read → search_records
REST endpointGET https://cotlet.dev/api/v1/ontraccr/records/search
| Name | Type | Description |
|---|---|---|
| source string required | string | One of `boards`, `forms`. |
| card_design string | string | For boards: the card design, for example Project Tracker. |
| boards array | array | Boards that use that design. Leave empty for all. |
| filters array | array | Field, operator and value, on standard or custom fields. |
{
"source": "source"
} {
"card_design": "Project Tracker",
"results": [
{
"card": "Maple Street watermain",
"board": "Active Jobs",
"status": "In Progress"
}
]
} Dashboards gather analytics from boards, forms and time cards; the default one has Clock, Live Feed and Quick Stats. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_dashboards
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/dashboards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `create`, `add_widget`. `list` and `get` only read. |
| dashboard string required | string | Dashboard name. |
| widget object | object | For `add_widget`: type and the board, form or time card analytics it shows. |
{
"action": "action",
"dashboard": "dashboard"
} {
"dashboard": "Safety Compliance Overview",
"widgets": [
"Quick Stats",
"Inspections this week"
],
"saved": true
} Projects, cost codes, the Budget Tracking tab, the Project Status report, the Contract tab with change orders, and the project Gantt.
Most tools take a project, so `list` usually comes first. A blank project number is generated and must be unique. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_projects
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/projects/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| project string | string | Name or number, for `get` and `update`. |
| fields object | object | Name, division, location, number, client, type, geofence radius, info, billing and budget. |
{
"action": "action"
} {
"project": "Maple Street watermain",
"number": "P-2026-118",
"client": "Example Municipality",
"saved": true
} Returns the summary (estimated labor hours and costs, material, overhead and equipment costs, burden rate, contract value, expected profit) and per cost code the allocated hours and forecasted costs, including subcontract budgets.
MCP callontraccr_read → view_project_budget
REST endpointGET https://cotlet.dev/api/v1/ontraccr/project-budgets/view
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as manage_projects `list` returns it. |
{
"project": "project"
} {
"project": "Maple Street watermain",
"contract_value": 486000,
"expected_profit": 58300,
"cost_codes": [
{
"code": "02-200",
"name": "Trenching",
"allocated_hours": 320,
"forecast": 41200
}
]
} Returns estimated hours (from the budget), actual hours (from progress), remaining hours and the percentage used. Labor only: no materials, overhead or equipment.
MCP callontraccr_read → run_project_status_report
REST endpointGET https://cotlet.dev/api/v1/ontraccr/project-status-reports/run
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as manage_projects `list` returns it. |
{
"project": "project"
} {
"project": "Maple Street watermain",
"rows": [
{
"phase": "Excavation",
"cost_code": "02-200",
"estimated": 320,
"actual": 288,
"used": "90%"
}
]
} The contract drives progress billing to your client, so every change waits for your OK. Approved and pending change orders are tracked apart. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_project_contract
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/project-contract/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `add_item`, `add_change_order`. `list` and `get` only read. |
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| item object | object | Description, amount and holdback or retainage. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street watermain",
"contract_value": 486000,
"change_orders": [
{
"title": "Extra hydrant",
"amount": 8400,
"status": "Pending"
}
]
} Number and name must be unique; the agent runs `list` first. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_cost_codes
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/cost-codes/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| number string | string | Unique cost code number. |
| name string | string | Unique name, for example Fire Alarm. |
| description string | string | What the work is. |
| project string | string | Leave empty for a global code. |
{
"action": "action"
} {
"number": "02-210",
"name": "Backfill",
"saved": true
} Tasks can be dispatched to the Field Schedule, so date changes reach crews. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_gantt
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/gantt/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add_task`, `import`. `list` and `get` only read. |
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| task object | object | Name, start, end and the task it depends on. |
| file_url string | string | For `import`: a link to the file. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street watermain",
"task": "Pipe install, block 2",
"start": "2026-11-23",
"end": "2026-11-27",
"saved": true
} Customers under Contacts, Client Portal broadcasts and the custom databases Ontraccr calls buckets.
Run `list` first so the same customer is not added twice. Labels such as Commercial are created if new. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_customers
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/customers/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| customer string | string | Name, for `get` and `update`. |
| fields object | object | Name, division, labels, bucket, office and mobile phone, office and billing email, website. |
{
"action": "action"
} {
"customer": "Example Municipality",
"labels": [
"Commercial"
],
"billing_email": "ap@example.com",
"saved": true
} Customers see it in their portal and get an email about it. It reaches people outside your company. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → broadcast_client_message
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/client-message/broadcast
| Name | Type | Description |
|---|---|---|
| to string required | string | `all` or a list of customers with Client Portal accounts. |
| text string required | string | The message. |
{
"to": "to",
"text": "text"
} {
"recipients": 4,
"sent": true
} Buckets are set up under Settings > Customization > Buckets. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_buckets
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/buckets/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| name string | string | Bucket name. |
| parents array | array | Customers or buckets that link to it. |
| children array | array | Projects, equipment or buckets it links to. |
{
"action": "action"
} {
"bucket": "Highway Segment A",
"parents": [
"Example Municipality"
],
"saved": true
} Equipment records and check in or out, stock by location with low-stock thresholds, spreadsheet imports, assemblies and bulk labor cost changes.
Name, division and status are required. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_equipment
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/equipment/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| name string | string | For example Ford F150. |
| status string | string | For example Active or Needs Repair. |
| fields object | object | ID, type and other optional fields. |
{
"action": "action"
} {
"equipment": "Excavator 3",
"status": "Active",
"id": "EQ-103",
"saved": true
} Check-in starts a usage timer and adds a timeline record; check-out stops it. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → check_equipment
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/equipment/check
| Name | Type | Description |
|---|---|---|
| equipment string required | string | Equipment name or ID. |
| direction string required | string | One of `in`, `out`. |
| project string | string | For `in`: project or location. |
{
"equipment": "equipment",
"direction": "direction"
} {
"equipment": "Excavator 3",
"project": "Maple Street watermain",
"active": true
} Below the threshold Ontraccr raises a low-stock alert. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_inventory
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/inventory/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `update`. `list` and `get` only read. |
| material string | string | Material. |
| threshold number | number | Low-stock alert level. |
| quantity number | number | Quantity at a location. |
| location string | string | Location, job or vehicle. |
{
"action": "action"
} {
"material": "8 in PVC pipe",
"threshold": 20,
"locations": [
{
"location": "Yard",
"quantity": 34
}
]
} Name, description and part number are required columns; supplier, purchase cost, markup, units and quantity are optional. The agent reports the row count first. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → import_materials
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/materials
| Name | Type | Description |
|---|---|---|
| file_url string required | string | A link to the spreadsheet. |
| worksheet string | string | Tab to read. |
| division string | string | Division. |
{
"file_url": "https://example.com"
} {
"rows": 212,
"imported": true
} An assembly is quoted and tracked as one line item; its cost is calculated from its parts. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_assemblies
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/assemblies/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| name string | string | Assembly name. |
| materials array | array | Material and quantity per part. |
{
"action": "action"
} {
"assembly": "Hydrant set",
"materials": 5,
"saved": true
} Changes are additive: $3 plus $2 becomes $5. The agent lists the selection first. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → bulk_edit_labor_costs
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/edit-labor-costs/bulk
| Name | Type | Description |
|---|---|---|
| items array required | array | Materials or assemblies. |
| field string required | string | One of `labor_cost`, `labor_markup`. |
| change number required | number | Dollars to add, or percent. |
{
"items": "items",
"field": "field",
"change": 1
} {
"items": 14,
"field": "labor_cost",
"change": 2,
"saved": true
} Project folders, uploads, markups in the Advanced Viewer, file versions and the Notes tab with mentions.
Every project has its own folder under Files > Main > Projects. A file with an existing name becomes a new version. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → manage_project_files
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/project-files/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create_folder`, `upload`. `list` and `get` only read. |
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| folder string | string | Folder path. |
| file_url string | string | For `upload`: a link to the file. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street watermain",
"folder": "Permits",
"file": "Road closure permit.pdf",
"uploaded": true
} Saving annotations creates a new version; earlier versions stay in list_file_versions. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → annotate_file
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/file/annotate
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| file string required | string | File name. |
| marks array required | array | Type (`highlight`, `rectangle`, `text`), page, position and text. |
{
"project": "project",
"file": "file",
"marks": "marks"
} {
"file": "Site plan rev C.pdf",
"marks": 2,
"version": 4
} Ontraccr saves a new version when someone saves annotations or uploads a file with the same name. Earlier versions stay available.
MCP callontraccr_read → list_file_versions
REST endpointGET https://cotlet.dev/api/v1/ontraccr/file-versions
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| file string required | string | File name. |
| version number | number | Version to download. Leave empty to list them. |
{
"project": "project",
"file": "file"
} {
"file": "Site plan rev C.pdf",
"versions": [
{
"version": 3,
"saved": "2026-11-15",
"by": "Site lead"
},
{
"version": 2,
"saved": "2026-11-10",
"by": "Estimator"
}
]
} A mention sends the user a push notification, so notes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callontraccr_write → add_project_note
REST endpointPOST https://cotlet.dev/api/v1/ontraccr/project-notes
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| project string required | string | Project name or number, as manage_projects `list` returns it. |
| text string | string | The note; @username mentions notify that user. |
| file_url string | string | Attachment. |
{
"action": "action",
"project": "project"
} {
"project": "Maple Street watermain",
"note": "@SiteLead permit is in Files > Permits.",
"saved": true
} Your signed-in Ontraccr browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 40 Ontraccr tools. The session cookie stays in the Cloud Browser.
The boards, forms, projects and time cards your Ontraccr role and divisions allow.
Users, roles and permissions, clock settings, and the QuickBooks Online, Sage 100 Contractor, Stripe, Gmail and DocuSign integrations.
You log in again yourself, in the same Cloud Browser.
Disable Ontraccr for agents, reset the browser, or change your Ontraccr password.
Cotlet never sees or stores your password. You log in yourself and the agent works only with the session left behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Card status, card task, draft shift | Call manage_cards, manage_card_tasks or schedule_shifts again with the right values |
| Time entry or approval | Edit the entry in Team Cards; payroll may already have read it |
| Published shift or project note with a mention | The crew was notified: tell them the change |
| Client Portal broadcast, signature or payment link | Already with the client: follow up with them |
All 34 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 6 read tools, the reports, searches, budget and file versions, run at once.
{
"name": "enter_time",
"arguments": {
"users": [
"Crew member A",
"Crew member B"
],
"date": "2026-11-17",
"start": "07:00",
"end": "15:30",
"break_minutes": 30,
"project": "Maple Street watermain",
"cost_code": "02-200"
}
} curl -X POST https://cotlet.dev/api/v1/ontraccr/time/enter \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"users":["Crew member A","Crew member B"],"date":"2026-11-17","start":"07:00","end":"15:30","break_minutes":30,"project":"Maple Street watermain","cost_code":"02-200"}' {
"date": "2026-11-17",
"project": "Maple Street watermain",
"cost_code": "02-200",
"entries": [
{
"user": "Crew member A",
"hours": 8
},
{
"user": "Crew member B",
"hours": 8
}
],
"total_hours": 16
} The example logs 07:00 to 15:30 with a 30 minute break for two crew members on cost code 02-200: 8 hours each, 16 in all. A cron job or n8n flow can make the same call over REST at /api/v1/ontraccr with the same key and price, in JSON. Failed calls are free.
About $25 a monthfor a contractor with 12 field staff on four projects, 4,280 credits. Your Ontraccr plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning form approvals | 2 × 22 | 440 |
| Friday time card review and payroll report | 3 × 4 | 120 |
| Field shifts for next week | 12 × 4 | 480 |
| Board card moves and follow-up tasks | 2 × 40 | 800 |
| Weekly budget and status, four projects | 8 × 4 | 320 |
| Equipment check in and out | 1 × 40 | 400 |
| Daily site report submissions | 1 × 22 | 220 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 278 calls | 4,280 |
The smallest pack, 5,000 credits for $29, covers this month. More crews and projects mean more calls.
Credit packs are bought once, with no subscription. The month above is our assumption, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Ontraccr on Zapier | Card Moved trigger and Create a Board Card action. | Nothing for forms, time cards, projects or equipment. |
| Zapier MCP | Puts that Ontraccr action in front of ChatGPT or Claude. | The same single action, run through your Zapier account. |
| Ontraccr's own integrations | QuickBooks Online, Sage 100 Contractor, Stripe, Gmail, DocuSign. | Accounting, payment and signature links, not a route for an AI agent. |
| Custom Form Exports | Chosen form fields as CSV or a dashboard widget. | A report you download, not actions. |
If creating a board card from another app is all you need, Ontraccr's Zapier app does it. Cotlet fits when ChatGPT, Claude or a script should work across time cards, forms, projects and equipment, from your own login, with nothing to host.
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and trading since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Ask about the Ontraccr tools at contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=ontraccr, turn on Ontraccr under Integrations in the console and log in at https://app.ontraccr.com/login in your Cloud Browser. Then connect your AI agent and ask it for this week's Team Cards. The trial needs no card.
Ontraccr publishes no public API documentation. Its integration with other tools runs through named integrations and a Zapier app with one trigger (Card Moved) and one action (Create a Board Card); no Ontraccr MCP server or official ChatGPT or Claude connector was found (checked 17 Nov 2026). Cotlet works in your own signed-in Ontraccr account instead.
Only through the integrations you set up in Ontraccr. add_signature_step needs DocuSign connected in Settings > Integrations > DocuSign, and add_payment_step needs Stripe linked there. No Cotlet tool connects or changes those integrations.
No. Ontraccr documents its own QuickBooks Online, Sage 100 Contractor, Stripe and Gmail integrations in its Help Center. You manage them in Ontraccr; no Cotlet tool changes them, or your users, roles and permissions.
A user whose role covers the work, usually a supervisor or admin. Approving time cards, Manual Entry for others and form approvals all follow that user's permissions and divisions.
Only in how it is called. Both carry the same 40 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Ontraccr.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy