JobNimbus MCP Server
This server connects Claude directly to your JobNimbus account via its API, enabling full management of CRM data, jobs, tasks, and more through natural language.
Contacts: List/search (by name, email, status), get by ID, create, and update — including custom fields.
Jobs: List/search (by status, name, contact, or last-updated timestamp), get by ID, create, and update — including custom fields and GHL migration fields (Lead Number, Job Number, GPS Coordinates, Plus Code).
Notes: List notes on a contact or job (excludes system-generated notes), and add new notes.
Tasks: List tasks linked to a contact or job, and create tasks with due dates and assignees.
Files: List file and photo attachments linked to a contact or job.
Financial Documents: List estimates and invoices, optionally filtered by related record.
Orders: List material orders and work orders, optionally filtered by related record.
Activities: List all activity records (calls, emails, status changes, etc.).
Account Info: Retrieve account details, workflow stages, users, and custom field definitions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JobNimbus MCP Server list recent jobs from last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JobNimbus MCP Server
Connects Claude directly to your JobNimbus account via the API.
Tools Available
Tool | Description |
| List/search contacts (filter by name, email, status) |
| Get a single contact by jnid |
| Create a new contact |
| Update contact fields + custom fields |
| List/search jobs (filter by status, contact, name) |
| Get a single job by jnid |
| Create a new job (with Lead Number, Job Number, GPS, Plus Code) |
| Update job fields + GHL migration fields |
| List notes on a contact or job |
| Add a note to a contact or job |
| List file/photo attachments |
| List tasks |
| Create a task |
| List estimates |
| List invoices |
| List activity records |
| List material orders |
| List work orders |
| 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 build2. 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 toolsjn_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
Scored across 19 tools
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.
All tools follow a consistent 'jn_verb_noun' pattern, using snake_case throughout. Verbs like create, get, list, update are used uniformly.
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.
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
Related MCP Connectors
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
1Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Personal CRM for Claude. Contacts live as plain-text files in your own Google Drive.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables remote access to JobNimbus CRM through Claude Desktop with 48+ tools for managing jobs, contacts, estimates, and advanced analytics. Features zero-storage security architecture where API keys are never stored on the server.2 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to manage GoHighLevel CRM contacts, pipelines, and workflows through natural language commands.115 npmMIT
- FlicenseCqualityDmaintenanceConnects Claude to ServiceTitan via API, providing 60 tools across CRM, Jobs, Accounting, and more for business management.601-
- AlicenseBqualityDmaintenanceConnects Claude to Jira, allowing users to query tasks, log work, add comments, and execute JQL queries through conversational AI.22MIT