How to Connect JobNimbus to Claude (and What It Can't Do)
JobNimbus users mostly aren’t at desks. The CRM tracks roofing and contracting work — contacts, jobs, boards, estimates — while the crew is on a ladder and the owner is driving between sites. That shapes the Claude question in a specific way: the pieces exist, but nobody official put them together. As of mid-2026 there’s no JobNimbus app in Anthropic’s connector directory and no MCP server from JobNimbus itself. What has grown up instead is a small, genuinely useful community scene: two open-source MCP servers, both built on JobNimbus’s public API.
Two community servers, no official one
clykins90/jobnimbus-mcp-server is the lightweight option: published on npm, runs locally over stdio, and covers contacts, jobs, tasks, products, workflows, and invoices. You add it to Claude Desktop’s MCP configuration with your JobNimbus API key and restart the app.
benitocabrerar/jobnimbus-mcp-remote is the heavyweight: a remote server exposing around 48 tools, designed with a zero-storage approach so your data isn’t persisted on the server. Because it’s remote, it plugs into Claude as a custom connector — and custom connectors require a paid Claude plan.
Both are community code under open licenses, which cuts both ways: free and inspectable, but maintained by volunteers rather than JobNimbus. Before connecting either, create a dedicated API key (Settings → API → New API key) and give it a scoped access profile so the server can touch only what it needs.
What that looks like on a Tuesday
Once wired up, Claude answers the questions you’d otherwise dig through boards for:
- “Which jobs on the Production board have sat in Material Ordered longer than a week?”
- “Pull everything on the Hendersons’ re-roof — contact record, job history, last estimate.”
- “List estimates older than ten days with no signed contract, and create a callback task for each.”
That last one shows both the power and the catch. Claude will find the stale estimates and create the tasks — right then, because you asked. It won’t be there next Tuesday unless you ask again.
The chat window vs the job site
Contracting runs on events that don’t wait for you to open a laptop, and Claude’s connectors act only inside a conversation you personally start. Play that against a normal week:
A hail storm fills your lead sources overnight; no contacts or jobs get created until someone sits down and prompts. An inspection wraps at 3 p.m. and the job moves to Inspection Complete; the estimate reminder doesn’t write itself. A sub marks their work done; the board doesn’t advance, the homeowner doesn’t hear anything. Claude has no schedule and no event hooks — every action needs a human in the chat, which is exactly the person who’s supposed to be on a roof.
Putting the boards on autopilot: Carly
Carly is built for the event side. It’s an AI executive assistant running in the cloud, and its workflows start from triggers, not prompts: a job changing status, a lead arriving, an email landing. You describe the outcome in plain English — “when a job moves to Approved, email the homeowner the schedule and create the material-order task” — and Carly interviews you about the details, then builds the workflow with you and runs it 24/7. It sends the homeowner email itself (Gmail and Outlook, attachments included), keeps JobNimbus records moving, and coordinates calendar and tasks around the work. AI agents start at $35/month, and steps that don’t use AI run free and unlimited. Carly covers 200+ tools across 40+ categories; see the JobNimbus integration page.
Community MCP vs Carly for JobNimbus work
| Claude (community JobNimbus MCP) | Carly | |
|---|---|---|
| Read contacts, jobs & boards | Yes | Yes |
| Update job status, add notes | When asked, in chat | When the job event fires |
| Server maintained by | Community volunteers | Carly (native) |
| Catches a stalled estimate on its own | No | Yes |
| Emails the homeowner the update | Draft only — you send it | Sends it (Gmail + Outlook) |
| Works from the truck, laptop closed | No | Yes (cloud) |
| Cost | Free OSS servers; paid Claude plan for the remote route | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with JobNimbus?
Yes, through community-built MCP servers — there’s no official option as of mid-2026. Two open-source projects (a local npm server and a remote one with ~48 tools) wrap the JobNimbus API. The remote route requires a paid Claude plan for the custom connector. Connected, Claude can read and update contacts, jobs, tasks, and estimates during a chat.
Is there an official JobNimbus MCP server or Claude connector?
No. JobNimbus publishes an open API with API-key authentication, but neither JobNimbus nor Anthropic offers a first-party connection. The community servers above fill the gap.
Which JobNimbus MCP server should I pick?
If you live in Claude Desktop and want minimal moving parts, the local npm server (jobnimbus-mcp-server) is simpler. If you want broader tool coverage or access from any Claude client, the remote server (jobnimbus-mcp-remote) is more capable but runs as a custom connector on a paid plan.
Can Claude move jobs across my boards automatically?
Only while you’re in a chat telling it to. Nothing in JobNimbus can wake Claude up — no status change, no new lead, no schedule. For hands-off board movement and homeowner follow-ups, Carly runs on triggers in the cloud; AI agents start at $35/month.
What API access does the MCP server need?
A JobNimbus API key, created under Settings → API. Keys carry an access profile that controls permissions — create one scoped specifically for the MCP server rather than reusing an admin key.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI CRM tools · Claude + Agiled · Claude + Apollo · Claude + Keap
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
