AccuLynx MCP Server
Jobs, contacts, photos and estimates in your AccuLynx account.
Server MCP Terhosting
npx add-mcp 'https://cotlet.dev/mcp/v1/acculynx'Terpasang ke Claude Code, Codex, Cursor, dan lainnya
Dokumentasi
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
AccuLynx API and MCP server
Yes, but only with the AppConnections add-on: AccuLynx has a REST API (v2) for jobs, contacts, estimates, photos, job messages and payments, and an administrator creates the API key for each location (checked 11 Oct 2026). The API reads milestones but cannot change them, it cannot create estimates, and there is no official AccuLynx MCP server.
Jobs, contacts, photos and estimates in your AccuLynx account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
Roofing contractor software: leads and jobs moving through milestones, contacts, estimates, job photos, job messages and payments.
What is the AccuLynx API?
Cotlet's AccuLynx API exposes 14 endpoints for your own AccuLynx account: list jobs, get job, find contact, list estimates, get estimate, list job messages, list job payments, create contact, create job, update job milestone, upload job photo, post job message, add contact note and record payment received. The list_jobs endpoint returns jobs in your location with name, address, current milestone, priority and dates. Each endpoint takes simple JSON inputs like job_id, milestone or limit and works both as an operation of the acculynx_read or acculynx_write MCP tool for agents and as a REST call for scripts.
- Category: Local services & SaaS
- Endpoints: 14 (7 read, 7 write)
- Updated: 2026-11-16
Yes, but only with the AppConnections add-on: AccuLynx has a REST API (v2) for jobs, contacts, estimates, photos, job messages and payments, and an administrator creates the API key for each location (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for AccuLynx with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.
Does AccuLynx have an official API?
Yes, but only with the AppConnections add-on: AccuLynx has a REST API (v2) for jobs, contacts, estimates, photos, job messages and payments, and an administrator creates the API key for each location (checked 11 Oct 2026). The API reads milestones but cannot change them, it cannot create estimates, and there is no official AccuLynx MCP server.
| Task | AccuLynx official | Cotlet |
|---|---|---|
| Find jobs by milestone | Partly: Needs the AppConnections add-on | Yes |
| Add a contact and open a job for it | Partly: Needs the add-on; the contact must exist before the job | Yes |
| Move a job to another milestone | No: Milestones are read only in the API | Yes |
| Upload job photos | Partly: Needs the add-on | Yes |
| Post a job message | Partly: Needs the add-on | Yes |
| Read estimates and their line items | Partly: Needs the add-on; read only, no creating estimates | Yes |
| Record a payment received | Partly: Needs the add-on | Yes |
| Add a note to a contact | Partly: Needs the add-on | Yes |
Sources: AccuLynx AppConnections, AccuLynx API docs: authentication, AccuLynx API docs: reference, AccuLynx on Zapier MCP, AccuLynx: Create automations in AccuLynx, AccuLynx API docs: Create Job
Quick reference
Yes, but only with the AppConnections add-on: AccuLynx has a REST API (v2) for jobs, contacts, estimates, photos, job messages and payments, and an administrator creates the API key for each location (checked 11 Oct 2026). The API reads milestones but cannot change them, it cannot create estimates, and there is no official AccuLynx MCP server.
Cotlet provides a hosted MCP server and REST API for AccuLynx: 14 tools (7 read, 7 write).
Access Sign up at https://cotlet.dev/app/signup?app=acculynx and request the app in the Cotlet console. ChatGPT and Claude connect with OAuth at https://cotlet.dev/mcp/v1/connect, no API key; code editors and scripts use an API key from the console.
MCP server https://cotlet.dev/mcp/v1
MCP tools acculynx_read, acculynx_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base https://cotlet.dev/api/v1/acculynx, each operation at its own route, e.g. PATCH /api/v1/acculynx/jobs/{job_id}/milestone
Auth Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations list_jobs, get_job, find_contact, list_estimates, get_estimate, list_job_messages, list_job_payments, create_contact, create_job, update_job_milestone, upload_job_photo, post_job_message, add_contact_note, record_payment_received
Confirm update_job_milestone, post_job_message, record_payment_received (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown https://cotlet.dev/integrations/acculynx-api-mcp-server.md
How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=acculynx and requests AccuLynx in the Cotlet console.
2. The user signs in to AccuLynx once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables AccuLynx for agents. An agent cannot do this step.
3. ChatGPT and Claude: the user adds https://cotlet.dev/mcp/v1/connect as a connector and signs in to Cotlet (OAuth). Code editors and scripts: an API key from the console goes into the MCP client or the REST call as a bearer token.
Fits: people who want a hosted AccuLynx server that someone else maintains, including non-developers.
Policy: Cotlet never stores passwords and never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to AccuLynx in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get AccuLynx only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no AccuLynx login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following AccuLynx's terms; Cotlet is not affiliated with AccuLynx.
What can an AI agent do in AccuLynx?
Cotlet is best for roofing contractors and their office staff who want an AI agent to add leads, upload job photos, move milestones and check estimates without running or fixing a server.
- Create jobs from new leads: "New lead from the website form: Jane Doe, (214) 555-0142, jane.doe@example.com, 12 Oak St, Plano, roof leaking since Sunday's storm, came from Google Ads. Check she is not already in AccuLynx, add her and open a job." →
find_contact,create_contact,create_job,add_contact_note - Upload inspection photos to a job: "Upload the 14 photos in ./inspection to the Oak St job and leave a message for the crew." →
list_jobs,upload_job_photo,post_job_message - Find stalled jobs and their estimates (runs: weekly): "Every Monday, list Prospect jobs that have sat there more than 21 days with their estimate totals and the last job message, plus Completed jobs older than 7 days that still have money owed." →
list_jobs,get_job,list_estimates,list_job_messages - Move a signed job to Approved: "The Miller job at 48 Pine Ridge Rd signed today. Move it to Approved and log the $2,500 deposit, check #2218 dated Oct 10." →
list_jobs,get_job,update_job_milestone,list_job_payments,record_payment_received - List completed jobs not yet invoiced (runs: weekly): "Every Monday, list jobs that reached Completed last week but are not Invoiced." →
list_jobs,get_job
Can AccuLynx automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a AccuLynx connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to find stalled jobs and their estimates, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.
| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/acculynx/jobs. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/acculynx/jobs with your API key. | cron or GitHub Actions. |
Tools
For AI agents: Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to AccuLynx.
list_jobs
Jobs in your location with name, address, current milestone, priority and dates. Access: read. REST: GET /api/v1/acculynx/jobs. MCP: acculynx_read → list_jobs.
| Parameter | Type | Required | Description |
|---|---|---|---|
milestone | enum | no | Lead, Prospect, Approved, Completed, Invoiced, Closed or Dead. Default: all. |
search | string | no | Job name, address or contact name. |
sort_by | enum | no | created, milestone_date or modified. Default: modified. |
limit | integer | no | 1 to 100. Default: 25. |
cursor | string | no | Next page cursor from the previous call. |
Lists jobs in one location, most recently modified first unless you sort otherwise. Filter by milestone or search by job name, address or contact name. Milestone is one of Lead, Prospect, Approved, Completed, Invoiced, Closed or Dead. Pages hold up to 100 jobs; pass next_cursor back as cursor for the next page.
Example response:
{
"jobs": [
{
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"job_name": "Miller - 48 Pine Ridge Rd",
"address": "48 Pine Ridge Rd, Plano, TX 75074",
"milestone": "Prospect",
"priority": "Normal",
"milestone_date": "2026-09-02T10:20:00-05:00",
"modified_at": "2026-10-08T15:41:00-05:00"
},
{
"job_id": "e91a47d3-5c60-4b2f-8d1e-0a7f3c9b5e24",
"job_name": "Garcia - 310 Elm Ct",
"address": "310 Elm Ct, Frisco, TX 75034",
"milestone": "Prospect",
"priority": "High",
"milestone_date": "2026-09-11T08:05:00-05:00",
"modified_at": "2026-10-06T09:12:00-05:00"
}
],
"next_cursor": null
}
get_job
Full job: contacts, address, trade and work type, milestone history, sales owner and financial totals. Access: read. REST: GET /api/v1/acculynx/jobs/{job_id}. MCP: acculynx_read → get_job.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
Returns one job with its contacts, job site address, trade and work type, sales owner and the milestone history in order. Financial totals are the figures shown on the job in AccuLynx. Use the job_id from list_jobs.
Example response:
{
"job_id": "e91a47d3-5c60-4b2f-8d1e-0a7f3c9b5e24",
"job_name": "Garcia - 310 Elm Ct",
"address": "310 Elm Ct, Frisco, TX 75034",
"milestone": "Completed",
"priority": "Normal",
"work_type": "Replacement",
"trade_types": [
"Roofing"
],
"sales_owner": "Dana Whitfield",
"contacts": [
{
"contact_id": "c2b8f6a1-90d4-4a37-b5e2-6f1d8a3c7e09",
"name": "Luis Garcia",
"role": "Primary"
}
],
"milestone_history": [
{
"milestone": "Lead",
"date": "2026-08-14T11:02:00-05:00"
},
{
"milestone": "Prospect",
"date": "2026-08-16T09:30:00-05:00"
},
{
"milestone": "Approved",
"date": "2026-09-11T08:05:00-05:00"
},
{
"milestone": "Completed",
"date": "2026-10-05T16:48:00-05:00"
}
],
"totals": {
"contract": "14850.00",
"received": "7425.00",
"currency": "USD"
}
}
find_contact
Contacts matching a name, email or phone number, with their jobs. Access: read. REST: GET /api/v1/acculynx/contacts/find. MCP: acculynx_read → find_contact.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | yes | Name, email or phone. |
Searches contacts by name, email or phone number and returns each match with the jobs linked to it. Run it before create_contact so you do not add the same person twice. Use the contact_id with create_job and add_contact_note.
Example response:
{
"contacts": [
{
"contact_id": "c7d2a9f0-3b11-4e8c-a6d5-91f0e2b47c18",
"name": "Jane Doe",
"phone": "(214) 555-0142",
"email": "jane.doe@example.com",
"jobs": []
}
]
}
list_estimates
Estimates on a job with name, total and date. Access: read. REST: GET /api/v1/acculynx/jobs/{job_id}/estimates. MCP: acculynx_read → list_estimates.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
Returns every estimate on one job with its name, total and date. Pass estimate_id to get_estimate for the sections and line items. Estimates are read only: Cotlet does not create or edit them.
Example response:
{
"estimates": [
{
"estimate_id": "a40d9e17-2f6b-4c83-b1a5-7e3c8d0f6291",
"name": "Full replacement, architectural shingles",
"total": "14850.00",
"date": "2026-09-09"
}
]
}
get_estimate
One estimate with its sections, line items, quantities and prices. Access: read. REST: GET /api/v1/acculynx/estimates/{estimate_id}. MCP: acculynx_read → get_estimate.
| Parameter | Type | Required | Description |
|---|---|---|---|
estimate_id | string | yes | Estimate ID from list_estimates. |
Returns one estimate with its sections in order and the line items in each section, with quantity and price. Line item totals add up to the estimate total. Use it to read back what was promised on a job.
Example response:
{
"estimate_id": "a40d9e17-2f6b-4c83-b1a5-7e3c8d0f6291",
"name": "Full replacement, architectural shingles",
"total": "14850.00",
"sections": [
{
"name": "Materials",
"items": [
{
"name": "Architectural shingles",
"quantity": 32,
"unit": "square",
"price": "210.00",
"total": "6720.00"
}
]
},
{
"name": "Labor",
"items": [
{
"name": "Tear-off and install",
"quantity": 32,
"unit": "square",
"price": "253.13",
"total": "8100.00"
},
{
"name": "Dumpster",
"quantity": 1,
"unit": "each",
"price": "30.00",
"total": "30.00"
}
]
}
]
}
list_job_messages
Messages posted on a job, with author, date and replies. Access: read. REST: GET /api/v1/acculynx/job-messages. MCP: acculynx_read → list_job_messages.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
limit | integer | no | 1 to 100. Default: 25. |
Returns the messages on one job, newest first, with replies nested under the message they answer. Use it to read what the crew and office said before you post.
Example response:
{
"messages": [
{
"message_id": "m-3a91",
"author": "Dana Whitfield",
"body": "Customer wants the ridge vent upgrade.",
"posted_at": "2026-10-04T14:10:00-05:00",
"replies": [
{
"message_id": "m-3a97",
"author": "Crew lead",
"body": "Added to the order.",
"posted_at": "2026-10-04T15:02:00-05:00"
}
]
}
]
}
list_job_payments
Payments recorded on a job with date, method and amount. Access: read. REST: GET /api/v1/acculynx/job-payments. MCP: acculynx_read → list_job_payments.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
Returns the payments recorded on one job, newest first, with the method and reference. Use it before record_payment_received to see whether a deposit is already there.
Example response:
{
"payments": [
{
"payment_id": "p-1182",
"type": "received",
"amount": "7425.00",
"method": "Check",
"reference": "#1043",
"received_on": "2026-09-12"
}
]
}
create_contact
New contact with name, phone, email and mailing address. Access: write. REST: POST /api/v1/acculynx/contacts. MCP: acculynx_write → create_contact.
| Parameter | Type | Required | Description |
|---|---|---|---|
first_name | string | yes | First name. |
last_name | string | yes | Last name. |
phone | string | no | Phone number. |
email | string | no | Email address. |
address | object | no | street, city, state, zip. |
Adds one contact to AccuLynx and returns its contact_id. It adds a record your team sees and sends nothing to the person, so it runs without asking. Use find_contact first to avoid duplicates.
Example response:
{
"contact_id": "c7d2a9f0-3b11-4e8c-a6d5-91f0e2b47c18",
"name": "Jane Doe",
"phone": "(214) 555-0142",
"email": "jane.doe@example.com",
"created_at": "2026-10-11T09:02:00-05:00"
}
create_job
New job for a contact, at the job site address. Access: write. REST: POST /api/v1/acculynx/contacts/{contact_id}/jobs. MCP: acculynx_write → create_job.
| Parameter | Type | Required | Description |
|---|---|---|---|
contact_id | string | yes | Contact ID from find_contact or create_contact. |
job_name | string | no | Default: contact name and street. |
address | object | no | Job site: street, city, state, zip. Default: contact address. |
priority | enum | no | Normal, High or Urgent. Default: Normal. |
Opens a job for an existing contact and returns it with the milestone it starts in. The job site address defaults to the contact address. It adds a record your team sees and sends nothing to the customer, so it runs without asking.
Example response:
{
"job_id": "f2a6c8d1-4e93-4b07-a1d5-3c9e7b0f5a62",
"job_name": "Doe - 12 Oak St",
"address": "12 Oak St, Plano, TX 75074",
"milestone": "Lead",
"priority": "High",
"created_at": "2026-10-11T09:03:00-05:00"
}
update_job_milestone
Move a job to another milestone, as you would in the job file, if your role allows it. Access: write, asks the user first. REST: PATCH /api/v1/acculynx/jobs/{job_id}/milestone. MCP: acculynx_write → update_job_milestone.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
milestone | enum | yes | Prospect, Approved, Completed, Invoiced, Closed or Dead. |
Moves one job to another milestone the way you do in the job file, and returns the previous milestone and the date of the new one. It fails if your AccuLynx role does not allow the move. A milestone change can set off your own AccuLynx workflow. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"job_name": "Miller - 48 Pine Ridge Rd",
"milestone": "Approved",
"previous_milestone": "Prospect",
"milestone_date": "2026-10-12T09:14:00-05:00"
}
upload_job_photo
Add a photo or video to the job file, with an optional tag and description. Access: write. REST: POST /api/v1/acculynx/jobs/{job_id}/photo. MCP: acculynx_write → upload_job_photo.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
file_url | string | yes | Image or video URL, or a file sent with the REST call. |
tag | string | no | One of your company photo and video tags. |
description | string | no | Caption shown with the photo. |
Adds one photo or video to the job file and returns its ID. The tag must be one of your company photo and video tags. The file goes into the job and nothing is sent to anyone, so it runs without asking.
Example response:
{
"photo_id": "ph-5530",
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"tag": "Inspection",
"description": "North slope, ridge cap damage",
"uploaded_at": "2026-10-11T10:21:00-05:00"
}
post_job_message
Post a message on a job for your team, or reply in a thread. Access: write, asks the user first. REST: POST /api/v1/acculynx/jobs/{job_id}/message. MCP: acculynx_write → post_job_message.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
body | string | yes | Message text. |
reply_to_id | string | no | Message ID from list_job_messages to reply to. |
Posts a message on one job under your name, or a reply under an existing message when reply_to_id is set. Your team sees it on the job. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"message_id": "m-3b02",
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"reply_to_id": null,
"status": "posted",
"posted_at": "2026-10-11T10:24:00-05:00"
}
add_contact_note
Add a note to a contact record. Access: write. REST: POST /api/v1/acculynx/contacts/{contact_id}/note. MCP: acculynx_write → add_contact_note.
| Parameter | Type | Required | Description |
|---|---|---|---|
contact_id | string | yes | Contact ID from find_contact or create_contact. |
body | string | yes | Note text. |
Adds a note to one contact record and returns its ID. The note shows on the contact in AccuLynx and is sent to no one, so it runs without asking.
Example response:
{
"note_id": "n-7741",
"contact_id": "c7d2a9f0-3b11-4e8c-a6d5-91f0e2b47c18",
"status": "added",
"created_at": "2026-10-11T09:05:00-05:00"
}
record_payment_received
Record a payment the customer made on a job. Nothing is charged. Access: write, asks the user first. REST: POST /api/v1/acculynx/jobs/{job_id}/payment-receiveds. MCP: acculynx_write → record_payment_received.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | yes | Job ID from list_jobs. |
amount | string | yes | Amount, e.g. "2500.00". |
method | string | yes | Payment method as named in your AccuLynx account, e.g. Check. |
received_on | date | no | Default: today. |
reference | string | no | Check number or memo. |
Records a payment the customer already made on one job, for example a deposit check, and returns the payment. Nothing is charged: it only writes the payment into the job. By default you confirm each call; you can switch that off for this tool.
Example response:
{
"payment_id": "p-1183",
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"amount": "2500.00",
"method": "Check",
"reference": "#2218",
"received_on": "2026-10-12",
"status": "recorded"
}
How do I connect AccuLynx to ChatGPT, Claude, Cursor or Codex?
Connecting AccuLynx takes three steps: sign up, sign in to AccuLynx once in your Cloud Browser and enable it for agents, then add Cotlet to ChatGPT or Claude as a connector, with no API key, or add one MCP server or call the REST API with an API key.
Connect AccuLynx to your agent.
-
Create an account Sign up and add AccuLynx in the console. ChatGPT and Claude need no API key: you sign in to Cotlet when you add the connector. Code editors and scripts take an API key from the console.
-
Sign in to AccuLynx in your Cloud Browser Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to AccuLynx there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.
-
Add Cotlet to ChatGPT, Claude or your agent Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude:
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:
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
- Ask your agent Ask in plain words. Your agent finds the AccuLynx tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.
New lead from the website form: Jane Doe, (214) 555-0142, jane.doe@example.com, 12 Oak St, Plano, roof leaking since Sunday's storm, came from Google Ads. Check she is not already in AccuLynx, add her and open a job.
Call AccuLynx from your scripts.
- Export your API key Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.
export COTLET_API_KEY="cotlet_..."
- Call a tool Every tool is an endpoint under /api/v1/acculynx with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.
curl -X PATCH https://cotlet.dev/api/v1/acculynx/jobs/b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90/milestone \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"milestone":"Approved"}'
- Read the result You get plain JSON back, ready for your script. A failed call costs nothing.
{
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"job_name": "Miller - 48 Pine Ridge Rd",
"milestone": "Approved",
"previous_milestone": "Prospect",
"milestone_date": "2026-10-12T09:14:00-05:00"
}
How to use the AccuLynx REST API
Create your Cotlet API key
Create a Cotlet API key with access to AccuLynx and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect AccuLynx in Cotlet and enable it for agents. Account access: Your own AccuLynx account (the role you use in the app decides what the tools can do).
Make your first AccuLynx API request
REST:
curl https://cotlet.dev/api/v1/acculynx/jobs \
-H "Authorization: Bearer $COTLET_API_KEY"
Read jobs and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "acculynx",
"tool": "list_jobs",
"result": {
"jobs": [
{
"job_id": "b3f1c2a4-7d2e-4f0a-9c51-2e8a4d6f1b90",
"job_name": "Miller - 48 Pine Ridge Rd",
"address": "48 Pine Ridge Rd, Plano, TX 75074",
"milestone": "Prospect",
"priority": "Normal",
"milestone_date": "2026-09-02T10:20:00-05:00",
"modified_at": "2026-10-08T15:41:00-05:00"
},
{
"job_id": "e91a47d3-5c60-4b2f-8d1e-0a7f3c9b5e24",
"job_name": "Garcia - 310 Elm Ct",
"address": "310 Elm Ct, Frisco, TX 75034",
"milestone": "Prospect",
"priority": "High",
"milestone_date": "2026-09-11T08:05:00-05:00",
"modified_at": "2026-10-06T09:12:00-05:00"
}
],
"next_cursor": null
}
}
Lists jobs in one location, most recently modified first unless you sort otherwise. Filter by milestone or search by job name, address or contact name.
Milestone is one of Lead, Prospect, Approved, Completed, Invoiced, Closed or Dead. Pages hold up to 100 jobs; pass next_cursor back as cursor for the next page.
limit: 1 to 100. Default: 25.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
AccuLynx workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Full job: contacts, address, trade and work type, milestone history, sales owner and financial totals. Use get_job in your configured business report. |
| Make | HTTP > Make a request | Estimates on a job with name, total and date. Use list_estimates in your configured business report. |
| Python or Node.js | REST API | Payments recorded on a job with date, method and amount. Use list_job_payments in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads AccuLynx; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Why use Cotlet for AccuLynx?
Built for agents
- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with ChatGPT, Claude, Claude Code, Codex and Cursor.
Your login stays yours
- You sign in to AccuLynx yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no MFA bypass.
You stay in control
- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.
Kept working for you
- We test every integration every 6 hours.
- When AccuLynx changes, the tool pauses until we fix it.
- Failed calls cost nothing.
Is it safe to connect AccuLynx to Cotlet?
Yes. You sign in to AccuLynx yourself, in your own Cloud Browser, and we never save your password. Your agents only get AccuLynx once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.
- A+ on Qualys SSL Labs: Encryption in transit: TLS setup and certificates, on all four server addresses. Live result
- A+ on securityheaders.com: Browser protections sent with every page, all six headers present. Live result
- A+ on Mozilla Observatory: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. Live result
- Clean on Sucuri SiteCheck: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. Live result
How Cotlet protects your access
Common concerns
Who runs Cotlet?
Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.
Is this an official AccuLynx integration?
No, Cotlet is independent of AccuLynx. AccuLynx's own API comes only with a paid plan. Cotlet works through your own AccuLynx account, the way you use AccuLynx in the browser, so you need no partner approval and no developer setup.
What about client data and GDPR?
Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.
Can I start with read only?
Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.
Is it reliable?
Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.
How do I stop?
Press Disable for agents next to AccuLynx in your console: your agents lose access at once and you stay signed in. Signing out of AccuLynx in the browser works too, and Reset browser deletes the whole profile.
Is there a AccuLynx MCP server on GitHub?
Zapier has an AccuLynx app, also through Zapier MCP. It has triggers on jobs, contacts and milestone changes, and actions that create contacts, jobs and leads and set custom fields. It runs on the same AppConnections API key, so it cannot move a job to another milestone.
| Zapier | Cotlet | |
|---|---|---|
| Setup | Zapier account, AppConnections add-on and an API key from an AccuLynx administrator | Sign up, sign in to AccuLynx once in your Cloud Browser, add one MCP server or API key |
| Write actions | Create contact, job or lead, update custom fields, set the initial appointment | Also move milestones, upload photos, post job messages, add contact notes and record payments |
| Milestones | Triggers when a milestone changes, cannot change it | Moves a job to another milestone, as your role allows in the app |
| When AccuLynx changes | Zapier updates its app; fields the API lacks stay out of reach | Our team tests it daily and fixes it for you; failed calls are free |
| Your AccuLynx access | An API key with access to one location | Signed in inside your own Cloud Browser in the EU, profile encrypted, disabled for agents in one click |
| Where it runs | Zapier cloud: Zaps or Zapier MCP | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Your Zapier plan, each action counts as a task | Free 7-day trial, then pay-as-you-go credit packs, no subscription |
Which one fits you
Pick Cotlet if
- you are not a developer, or you do not want to maintain a server
- you need it to keep working when AccuLynx changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off
Pick an open-source server if
- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client
How much does the AccuLynx API cost?
Free 7-day trial with 2,000 credits, no card needed. After that, the AccuLynx API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 to 100 credits (10 for most tools, about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.
| 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. See full pricing
How Cotlet holds your access
Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own AccuLynx account.
- Company details: Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. Terms of service
- Your sign-in: You sign in to AccuLynx yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get AccuLynx only after you enable it. When AccuLynx signs you out, your agent gives you a link to sign in again. Security
- Revoking access: Press Disable for agents next to AccuLynx, sign out of AccuLynx in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- What we never do: Store passwords or bypass MFA.
- AccuLynx's terms: You use your own AccuLynx account and stay responsible for following AccuLynx's terms. Cotlet is independent and not affiliated with AccuLynx. Terms
- Contact: Questions about the company, security or an app: contact@cotlet.dev
AccuLynx API and MCP: questions
How do I get access?
Sign up free, open AccuLynx in the console and press Activate. Then you create your API key and connect AccuLynx there.
Do I need to be technical?
No. You sign in to AccuLynx once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.
Is it safe to connect AccuLynx to Cotlet?
Yes. You sign in to AccuLynx yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get AccuLynx once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.
Is a hosted server safer than a local one? My AccuLynx sign-in would leave my computer.
On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your AccuLynx cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.
Why does Cotlet send requests instead of clicking in my browser?
To be fast, Cotlet doesn't click through AccuLynx's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. AccuLynx sees the same browser and IP you signed in with, and every request is listed in your Background activity.
What if someone gets my Cotlet API key?
The key holds no AccuLynx login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.
Why a signed-in browser and not OAuth, like other integration platforms?
AccuLynx offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).
How do I connect AccuLynx to ChatGPT or Claude?
Sign up at cotlet.dev, log in to AccuLynx once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your AccuLynx account through Cotlet, in their phone apps too.
What can ChatGPT do in AccuLynx?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in AccuLynx: create jobs from new leads; upload inspection photos to a job; find stalled jobs and their estimates. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need the AppConnections add-on?
No. Cotlet works in your own AccuLynx account and does not use an API key, which AccuLynx gives only with the AppConnections add-on (checked 11 Oct 2026). What the tools can do depends on your AccuLynx role.
Can it create or edit estimates?
No. list_estimates and get_estimate only read. AccuLynx's own API also has read-only estimate endpoints.
Can my agent post or send messages in AccuLynx without asking me?
No. Every call to update_job_milestone, post_job_message or record_payment_received waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_contact, create_job, upload_job_photo and add_contact_note run without asking, because they send nothing to anyone and one call undoes it.
Can I use the AccuLynx API in n8n?
Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/acculynx from the HTTP Request node.
Can I use the AccuLynx API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.