Skip to main content
Glama
JobNimbus MCP Server

JobNimbus MCP Server

by drummouse

JobNimbus MCP Server

Connects Claude directly to your JobNimbus account via the API.

Tools Available

Tool

Description

jn_list_contacts

List/search contacts (filter by name, email, status)

jn_get_contact

Get a single contact by jnid

jn_create_contact

Create a new contact

jn_update_contact

Update contact fields + custom fields

jn_list_jobs

List/search jobs (filter by status, contact, name)

jn_get_job

Get a single job by jnid

jn_create_job

Create a new job (with Lead Number, Job Number, GPS, Plus Code)

jn_update_job

Update job fields + GHL migration fields

jn_list_notes

List notes on a contact or job

jn_create_note

Add a note to a contact or job

jn_list_files

List file/photo attachments

jn_list_tasks

List tasks

jn_create_task

Create a task

jn_list_estimates

List estimates

jn_list_invoices

List invoices

jn_list_activities

List activity records

jn_list_material_orders

List material orders

jn_list_work_orders

List work orders

jn_get_account

Get account info, stages, custom field definitions

Related MCP server: GHL MCP Server

Installation

1. Install dependencies and build

cd jobnimbus-mcp
npm install
npm run build

2. Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "jobnimbus": {
      "command": "node",
      "args": ["/FULL/PATH/TO/jobnimbus-mcp/dist/index.js"],
      "env": {
        "JOBNIMBUS_API_KEY": "your-jobnimbus-api-key"
      }
    }
  }
}

Replace /FULL/PATH/TO/jobnimbus-mcp with the actual absolute path where you placed this folder.

3. Restart Claude Desktop

The JobNimbus tools will appear in Claude's tool list.


GHL → JobNimbus Migration: Custom Fields

When migrating assets from GoHighLevel, use custom_fields_json to write GHL data into JobNimbus custom fields:

{
  "Lead Number": "L-1234",
  "Job Number": "J-5678",
  "Plus Code": "87JC+9W Edmonton",
  "GPS Coordinates": "53.5461,-113.4938"
}

Example prompt to Claude:

"Update JobNimbus job [jnid] with GHL Lead Number L-1234, Job Number J-5678, and Plus Code 87JC+9W"


Security Note

⚠️ Rotate your API key in JobNimbus Settings → API if it has been shared in any chat or document. Generate a new key and update the config above.

Available Tools

19 tools
jn_create_contactC

Create a new contact in JobNimbus.

Inputs: zip, city, tags, email, +10 more.

jn_create_jobB

Create a new job in JobNimbus. Pass GHL Lead Number and Job Number via custom_fields_json.

Inputs: name (required), zip, city, tags, +8 more.

jn_create_noteB

Add a note to a contact or job in JobNimbus.

Inputs: note (required), related_jnid (required), related_type (required).

jn_create_taskB

Create a task in JobNimbus linked to a contact or job.

Inputs: title (required), related_jnid (required), related_type (required), note, +2 more.

jn_get_accountA

Get JobNimbus account info: workflow stages, users, custom field definitions.

Inputs: no named parameters.

jn_get_contactA

Get a single JobNimbus contact by jnid.

Inputs: jnid (required).

jn_get_jobB

Get a single JobNimbus job by jnid.

Inputs: jnid (required).

jn_list_activitiesB

List all activity records (calls, emails, status changes, etc.) in JobNimbus. Note: response key is 'activity' not 'results'.

Inputs: from, size, related_jnid.

jn_list_contactsC

List or search contacts in JobNimbus.

Inputs: from, size, sort_field, filter_name, +3 more.

jn_list_estimatesC

List estimates in JobNimbus.

Inputs: from, size, related_jnid.

jn_list_filesB

List files and photo attachments linked to a contact or job.

Inputs: from, size, related_jnid.

jn_list_invoicesC

List invoices in JobNimbus.

Inputs: from, size, related_jnid.

jn_list_jobsC

List or search jobs in JobNimbus.

Inputs: from, size, sort_field, filter_name, +4 more.

jn_list_material_ordersC

List material orders in JobNimbus.

Inputs: from, size, related_jnid.

jn_list_notesB

List user-written notes on a contact or job. Excludes system-generated status change notes.

Inputs: from, size, related_jnid.

jn_list_tasksC

List tasks in JobNimbus.

Inputs: from, size, related_jnid.

jn_list_work_ordersC

List work orders in JobNimbus.

Inputs: from, size, related_jnid.

jn_update_contactC

Update a contact in JobNimbus.

Inputs: jnid (required), zip, city, tags, +11 more.

jn_update_jobC

Update a job in JobNimbus. Use custom_fields_json for Lead Number, Job Number, GPS, Plus Code from GHL.

Inputs: jnid (required), zip, city, name, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action (contact, job, note, task, activity, etc.) with clear descriptions that prevent confusion. The only minor overlap between list_notes and list_activities is resolved by description.

    Naming Consistency5/5

    All tools follow a consistent 'jn_verb_noun' pattern, using snake_case throughout. Verbs like create, get, list, update are used uniformly.

    Tool Count5/5

    19 tools cover a comprehensive set of CRM entities (contacts, jobs, notes, tasks, activities, estimates, files, invoices, material orders, work orders) without being excessive. The scope is well-matched to the domain.

    Completeness3/5

    Core CRUD is present for contacts and jobs (create, get, update, list). However, for entities like tasks, notes, and estimates, only create and list exist; updates and deletes are missing. This leaves workflow gaps that may require workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers