Integra el CRM de techados AccuLynx con clientes de IA para gestionar trabajos, contactos, presupuestos y finanzas.
También conocido como opsrev/acculynx-cli, @opsrev/acculynx-cli, acculynx-mcp
- Stars
- 0
- Herramientas
- 34
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 27 oct 2026
- Licencia
- MIT
¿Qué es AccuLynx MCP?
Integra el CRM de techados AccuLynx con clientes de IA para gestionar trabajos, contactos, presupuestos y finanzas. Expone 34 herramientas, como acculynx_ping, acculynx_jobs_list, acculynx_jobs_get.
Resumen generado a partir del README del proyecto
Acerca del MCP server de AccuLynx
Este servidor permite a los contratistas que utilizan el CRM AccuLynx gestionar las operaciones de su negocio de techado mediante IA. Al conectarse con clientes como Claude Desktop o Cursor, los usuarios pueden interactuar con los datos de su empresa usando lenguaje natural para gestionar trabajos, contactos, presupuestos y registros financieros. El servidor ofrece 30 herramientas específicas, como acculynx_jobs_list y acculynx_contacts_search, todas regidas por JSON Schemas estrictos para garantizar que los agentes de IA utilicen los parámetros correctos.
La configuración requiere una API key de AccuLynx que debe obtenerse en los ajustes del administrador de la cuenta. El servidor se ejecuta localmente mediante npx o una instalación global de npm, comunicándose a través de stdio. Más allá de la funcionalidad estándar de MCP, el paquete incluye una interfaz de línea de comandos que permite realizar scripting avanzado y procesamiento de datos. Esto incluye capacidades de escaneo especializadas para monitorear hitos de trabajos, rastrear la antigüedad de prospectos o generar informes de evidencia de marketing con valores financieros exactos en centavos.
Qué puedes hacer con él
- 1Recuperar detalles de trabajos recientesPide a tu cliente de IA que enumere los cinco trabajos más recientes de tu cuenta de AccuLynx.
- 2Analizar la antigüedad de prospectosGenera un informe para ver cuánto tiempo han estado en el sistema los prospectos actuales utilizando categorías de días calendario específicas.
- 3Auditar pagos de trabajosEscanea todos los trabajos dentro de hitos específicos para verificar que los pagos recibidos estén registrados correctamente.
- 4Automatizar la gestión de contactosUsa la CLI para buscar contactos dentro de un rango de fechas específico y redirige los resultados a otras herramientas.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar AccuLynx MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar AccuLynx MCP en Claude Code
$ claude mcp add acculynx-cli -- npx -y @opsrev/acculynx-cliInstalar AccuLynx MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"acculynx-cli": {
"command": "npx",
"args": [
"-y",
"@opsrev/acculynx-cli"
]
}
}
}Instalar AccuLynx MCP en VS Code
.vscode/mcp.json
{
"servers": {
"acculynx-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@opsrev/acculynx-cli"
]
}
}
}Instalar AccuLynx MCP en VS Code CLI
$ code --add-mcp '{"name":"acculynx-cli","type":"stdio","command":"npx","args":["-y","@opsrev/acculynx-cli"]}'Instalar AccuLynx MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"acculynx-cli": {
"command": "npx",
"args": [
"-y",
"@opsrev/acculynx-cli"
]
}
}
}Instalar AccuLynx MCP en Codex
$ codex mcp add acculynx-cli -- npx -y @opsrev/acculynx-cliInstalar AccuLynx MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.acculynx-cli] command = "npx" args = ["-y", "@opsrev/acculynx-cli"]
Instalar AccuLynx MCP en Gemini CLI
$ gemini mcp add -s user acculynx-cli npx -- -y @opsrev/acculynx-cliInstalar AccuLynx MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"acculynx-cli": {
"command": "npx",
"args": [
"-y",
"@opsrev/acculynx-cli"
]
}
}
}Herramientas de AccuLynx MCP 34
Detectado desde el READMEacculynx_pingacculynx_jobs_listacculynx_jobs_getacculynx_jobs_createacculynx_jobs_searchacculynx_jobs_contactsacculynx_jobs_estimatesacculynx_jobs_financialsacculynx_jobs_invoicesacculynx_jobs_milestonesacculynx_jobs_paymentsacculynx_jobs_history
| acculynx_ping | — | |
| acculynx_jobs_list | — | |
| acculynx_jobs_get | — | |
| acculynx_jobs_create | — | |
| acculynx_jobs_search | — | |
| acculynx_jobs_contacts | — | |
| acculynx_jobs_estimates | — | |
| acculynx_jobs_financials | — | |
| acculynx_jobs_invoices | — | |
| acculynx_jobs_milestones | — | |
| acculynx_jobs_payments | — | |
| acculynx_jobs_history | — |
Mostrar las 34 herramientasMostrar menos herramientas
acculynx_jobs_repsacculynx_jobs_reps_assignacculynx_jobs_work_typesacculynx_jobs_trade_typesacculynx_jobs_set_work_typeacculynx_jobs_set_trade_typesacculynx_jobs_document_foldersacculynx_jobs_add_expenseacculynx_jobs_upload_documentacculynx_contacts_listacculynx_contacts_getacculynx_contacts_createacculynx_contacts_searchacculynx_contacts_emailsacculynx_contacts_phonesacculynx_contacts_phone_addacculynx_estimates_listacculynx_estimates_getacculynx_estimates_sectionsacculynx_estimates_sectionacculynx_estimates_itemsacculynx_users_list
| acculynx_jobs_reps | — | |
| acculynx_jobs_reps_assign | — | |
| acculynx_jobs_work_types | — | |
| acculynx_jobs_trade_types | — | |
| acculynx_jobs_set_work_type | — | |
| acculynx_jobs_set_trade_types | — | |
| acculynx_jobs_document_folders | — | |
| acculynx_jobs_add_expense | — | |
| acculynx_jobs_upload_document | — | |
| acculynx_contacts_list | — | |
| acculynx_contacts_get | — | |
| acculynx_contacts_create | — | |
| acculynx_contacts_search | — | |
| acculynx_contacts_emails | — | |
| acculynx_contacts_phones | — | |
| acculynx_contacts_phone_add | — | |
| acculynx_estimates_list | — | |
| acculynx_estimates_get | — | |
| acculynx_estimates_sections | — | |
| acculynx_estimates_section | — | |
| acculynx_estimates_items | — | |
| acculynx_users_list | — |
Configuración
ACCULYNX_API_KEYJOB_ID
| Nombre | Descripción | Tipo |
|---|---|---|
| ACCULYNX_API_KEY | — | |
| JOB_ID | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleopsrev/acculynx-cli is public and reachablegithub.com/opsrev/acculynx-cli ↗Aprobado
- El paquete indica este repositorio como su origen@opsrev/acculynx-cli, acculynx-mcp name opsrev/acculynx-cli as sourcenpmjs.com/package/@opsrev/acculynx-cli ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for @opsrev/acculynx-cli, acculynx-mcpnpmjs.com/package/@opsrev/acculynx-cli/v/1.18.2#provenance ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-27github.com/opsrev/acculynx-cli ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @opsrev/acculynx-cli, acculynx-mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo34 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubAccuLynx MCP Server & CLI
npm:
acculynx-mcp(MCP server) ·@opsrev/acculynx-cli(CLI + MCP)
An MCP server for the AccuLynx roofing CRM — bring jobs, contacts, and estimates into Claude Desktop, Cursor, or any MCP client. Every tool is exposed with an enforced JSON Schema, so an AI agent can't invent a parameter or call a command that doesn't exist.
- 30 tools across jobs, contacts, estimates, and users.
acculynx-mcp— the MCP server, for Claude Desktop / Cursor / any MCP client.@opsrev/acculynx-cli— the same data as a JSON CLI (and it also ships theacculynx-mcpserver bin).
Use in Claude Desktop
- Get an AccuLynx API key (your AccuLynx account administrator creates it under Account Settings → API).
- Open your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the server (zero-install via
npx):
{
"mcpServers": {
"acculynx": {
"command": "npx",
"args": ["-y", "acculynx-mcp"],
"env": { "ACCULYNX_API_KEY": "your-api-key" }
}
}
}
Prefer a global install? Run npm i -g acculynx-mcp, then use
"command": "acculynx-mcp" with no args.
- Restart Claude Desktop. Open a new chat and ask "List my 5 most recent
AccuLynx jobs" — you should see the
acculynx_*tools available.
Use in Cursor / other MCP clients
Any client that speaks MCP over stdio works. Point it at npx -y acculynx-mcp
(or a global acculynx-mcp) and set ACCULYNX_API_KEY in the environment.
Example (Cursor ~/.cursor/mcp.json):
{
"mcpServers": {
"acculynx": {
"command": "npx",
"args": ["-y", "acculynx-mcp"],
"env": { "ACCULYNX_API_KEY": "your-api-key" }
}
}
}
MCP tools
All tools are prefixed acculynx_ and return JSON.
| Tool | Description |
|---|---|
acculynx_ping |
Health check — verify the API key and connectivity |
acculynx_jobs_list |
List jobs (paginated, filterable) |
acculynx_jobs_get |
Get one job by id |
acculynx_jobs_create |
Create a job |
acculynx_jobs_search |
Search jobs by free-text term |
acculynx_jobs_contacts |
List a job's contacts |
acculynx_jobs_estimates |
List a job's estimates |
acculynx_jobs_financials |
Get a job's financials |
acculynx_jobs_invoices |
List a job's invoices |
acculynx_jobs_milestones |
List a job's milestone history |
acculynx_jobs_payments |
List a job's payments |
acculynx_jobs_history |
Get a job's change history |
acculynx_jobs_reps |
List a job's representatives |
acculynx_jobs_reps_assign |
Assign a representative to a job |
acculynx_jobs_work_types |
List the company's active work types (id + name) |
acculynx_jobs_trade_types |
List the company's active trade types (id + name) |
acculynx_jobs_set_work_type |
Set a job's work type — by workType name or workTypeId |
acculynx_jobs_set_trade_types |
Set a job's trade types — by tradeTypes names or tradeTypeIds (empty array unassigns all) |
acculynx_jobs_document_folders |
List the company's document folders |
acculynx_jobs_add_expense |
Record an additional expense on a job |
acculynx_jobs_upload_document |
Upload a local file to a job |
acculynx_contacts_list |
List contacts (paginated) |
acculynx_contacts_get |
Get one contact by id |
acculynx_contacts_create |
Create a contact |
acculynx_contacts_search |
Search contacts within a date range |
acculynx_contacts_emails |
List a contact's email addresses |
acculynx_contacts_phones |
List a contact's phone numbers |
acculynx_contacts_phone_add |
Add a phone number to a contact |
acculynx_estimates_list |
List estimates (paginated) |
acculynx_estimates_get |
Get one estimate by id |
acculynx_estimates_sections |
List an estimate's sections |
acculynx_estimates_section |
Get one estimate section |
acculynx_estimates_items |
List items in an estimate section |
acculynx_users_list |
List users (paginated, optional name/email search) |
Configuration
| Env Var | Flag | Required | Description |
|---|---|---|---|
ACCULYNX_API_KEY |
--api-key |
Yes | AccuLynx official API key (Account Settings → API) |
ACCULYNX_EMAIL |
— | No | Login email; only for tools that use AccuLynx's web API |
ACCULYNX_PASSWORD |
— | No | Login password; only for web-API tools |
ACCULYNX_COMPANY_ID |
— | No | Company GUID; only for web-API tools |
Also a CLI
@opsrev/acculynx-cli exposes the same data as a JSON CLI (and bundles the
acculynx-mcp server bin). All output is JSON to stdout; errors are
{"error": "..."} to stderr with exit code 1.
npm install -g @opsrev/acculynx-cli
acculynx ping # verify API key
acculynx jobs list --limit 5 # 25 results by default; --all to fetch everything
acculynx jobs get <jobId>
acculynx jobs search --query "smith"
acculynx jobs scan --milestones Approved # scan all jobs → digest + coverage receipt
acculynx contacts list --limit 10
acculynx estimates get <estimateId>
List commands default to 25 results; use --limit <n> or --all. Commands
that create resources read a JSON body from stdin:
echo '{"name": "New Job"}' | acculynx jobs create
Pipe to jq for scripting:
JOB_ID=$(acculynx jobs list --limit 1 | jq -r '.[0].id')
acculynx jobs get "$JOB_ID" | jq .
Prospect aging with complete readable rows
acculynx jobs scan --report prospect-aging --as-of 2026-10-20 --exclude-trade-type "Maintenance Program"
This bounded GET-only report ages current Prospect inventory by its full milestone date in America/New_York, with inclusive 0–30, 31–60, 61–90 and 91+ calendar-day buckets. It is not a historical inventory snapshot. Exclusions use exact case-insensitive trade-type names; missing classification stays unknown. Every eligible row includes its full ID, date, age and separate approved/worksheet values in exact cents. Missing values remain unavailable rather than zero.
Enumeration is strict and capped at 5,000 jobs before per-job financial reads. Reports above 180,000 characters return partial with no detailed list, keeping output below the retained process-log limit. No history, payment, message or write requests are made. Invalid/incomplete inventory withholds totals and rows; missing dates or financial evidence make the result partial (exit 3). Incompatible filters and output modes fail before provider access (exit 2). Read long stdout through bounded process-log pages.
Monitoring scans: payments with strict coverage
Scan every job in a set of milestones and fetch each one's received payments in one process, with a coverage line a script can check:
acculynx jobs scan --milestones Approved,Completed,Invoiced \
--enrich payments --strict --format jsonl --out payments.jsonl
Each job line carries payments: the job's full received-payment objects
(id, from, amount, paymentDate, checkNumber, notes, …). The last
line is the coverage receipt:
{"type":"coverage","scanned":299,"serverCount":299,"complete":true,"pageError":null,"enrichErrors":0}
--strict(implied by--enrich payments) treats any pagination anomaly (changing total, duplicate job IDs, overfull or malformed pages) as a partial scan. Partial scans exit 3 and reportcomplete: false. Never treat them as a full inventory.- A per-job payments failure doesn't abort the scan. It appears in that job's
errors({"jobId", "source": "payments", "message"}) and counts towardenrichErrors, so retry just those jobs withacculynx jobs payments <id>. - Without
--strictand withoutpayments,jsonloutput is unchanged: job lines only.
Development
cp .env.example .env # fill in your credentials
npm install
npm test # run unit tests (mocked fetch)
npm run dev -- --help # run the CLI in dev mode (auto-loads .env)
npm run build # build both bins to dist/
npm run dev auto-loads .env via Node's --env-file:
npm run dev -- jobs list --limit 5
License
MIT
Private marketing evidence from a native scan
Operators preparing approval-date reconciliation can preserve exact source fields without parsing the rounded human digest:
acculynx jobs scan --start-date 2026-07-01 --end-date 2026-09-04 --date-filter-type ModifiedDate --enrich dates,financials --format marketing-evidence
This emits one acculynx-marketing-evidence/v1 JSON object. It is private
operator evidence containing full job IDs and individual values; do not post
it in a vendor/customer channel. It excludes contacts, addresses, names,
notes, documents, unrelated financials and raw provider error bodies.
--out and other enrichers are rejected before reading. Redirect stdout only
into an appropriately protected operator workspace if retaining the artifact.
This format does not alter downstream agents' command allowlists or authorize
them to export records.
The receipt distinguishes query completeness from enrichment completeness. Strict pagination requires a numeric stable total, advancing offsets and unique job IDs. Exit 3 means partial evidence; never publish it as a complete result. Full source dates are preserved without timezone conversion, repeated approval milestones remain separate, and current approved value is represented in exact cents. Missing/invalid values and dates remain null with issue codes.
This is not an approval cohort, an original-acquisition attribution, a complete lead-delivery inventory or historical revenue. ModifiedDate is a candidate filter; confirm historical and unassigned/dead-lead coverage separately. Review source date semantics, repeated approvals, transfers and current-versus-original contract value before producing normalized results. A large historical scan reads history and financials for each candidate; bootstrap it separately from short daily marketing jobs, then validate an incremental refresh strategy.
Preguntas sobre AccuLynx MCP
¿Cómo agrego AccuLynx MCP a Claude Code?
Ejecuta claude mcp add acculynx-cli -- npx -y @opsrev/acculynx-cli en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego AccuLynx MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona AccuLynx MCP?
Expone 34 herramientas, incluidas acculynx_ping, acculynx_jobs_list, acculynx_jobs_get, acculynx_jobs_create, acculynx_jobs_search.
¿Qué tipo de datos puedo consultar a través de las herramientas MCP?
Puedes acceder a 30 herramientas diferentes que cubren trabajos, contactos, presupuestos, usuarios, finanzas, facturas y más.
¿Puedo usar esto como una interfaz de línea de comandos?
Sí, el paquete @opsrev/acculynx-cli proporciona una CLI en JSON para scripting y uso en terminal.
¿Dónde obtengo una API key para AccuLynx?
El administrador de tu cuenta de AccuLynx puede crear una API key en Account Settings → API.