For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/jobnimbus
Skill page: https://www.mcpbundles.com/skills/jobnimbus
Tools: 31
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
What you can do with JobNimbus
Built for
Roofing contractors, restoration teams, field ops, and office staff on JobNimbus
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
JobNimbus
Add to your AI client, then sign in once when you connect.
Let AI agents review roofing and contractor jobs, contacts, and tasks in JobNimbus, log field notes, and keep estimates and invoices moving without living in the CRM UI.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Best forRoofing contractorsrestorationfield opsand office staff on JobNimbus
Create a JobNimbus activity note on job {job_id} summarizing today's inspection and next steps for the crew.
Context to know first
Does this replace JobNimbus mobile or desktop apps?
No — it lets AI assistants read and update JobNimbus data you already store while you keep using JobNimbus for day-to-day field workflows.
Which JobNimbus permissions apply?
The connection uses your JobNimbus API key and its access profile. Agents only see and change records that key is allowed to touch.
AI Skill
SKILL.md
Domain knowledge for JobNimbus — workflow patterns, data models, and gotchas for your AI agent.
JobNimbus
JobNimbus is contractor CRM and job tracking. Permissions follow the access profile bound to the API key used for the connection.
Hierarchy
Contacts — customers and leads; custom fields appear as display names or cf_* keys.
Jobs — projects tied to contacts; workflow status names come from account configuration.
Tasks — work items, usually linked to jobs or contacts.
Activities — high-volume log (calls, emails, notes, status changes).
Files — attachments on contacts or jobs; public URLs can be ingested when the API allows.
Estimates, invoices, payments, work orders, material orders, products — field ops and billing records on the same account.
Operational order
Read account settings or workflows before filtering jobs by status or pipeline name — status strings are account-specific.
Page jobs or contacts with narrow Elasticsearch filter_ JSON (date range, related.id, term on status fields).
Page tasks or activities for a job using related.id in filter_ rather than unfiltered large pulls.
Upsert contacts or jobs when updating CRM state; use bulk or skip query params when automations or notifications should not fire.
For contacts, include email when creating — duplicate creates are resolved to PUT on the existing row with that email.
Invoices — create or update, then send or record payment as separate steps when billing workflows require it.
Gotchas
Pagination: from_ is a zero-based offset and size caps page length (internally clamped to 250 per request).
Filtering: use must / term / range in filter_ JSON — not query_string.
JSON literals: filter_ must use true / false / null, not Python boolean or None spellings.
Activity volume: narrow date or related-record filters; very long filter_ strings can exceed URL limits on the activity feed (HTTP 414).
Financial writes: create and update estimates, invoices, work orders, and material orders on v2/ paths — not legacy api1 collection POST.
File download: fetching a file by jnid returns raw bytes (base64 in the tool response); paginated file lists return JSON metadata only.
Actor scoping: optional team-member email on reads and writes when the key has admin-level actor support.
Stable list entrypoints: older integrations may still call legacy list-only tools with the same pagination params; combined get tools add single-record fetch and sort/field projection on the list branch.
Jobnimbus Create Activity — Log a note, call, or other activity on a contact or job (POST only). Activities are append-only — pass related record ids and body fields in record.
Jobnimbus Create File From URL — Attach a file to a JobNimbus contact or job from a public HTTP(S) URL. Pass the source URL and related record ids in record per JobNimbus file API rules.
Jobnimbus Create Workflow — Create a new JobNimbus workflow (account configuration). Pass workflow fields in record; omit jnid — updates are not supported on this path.
Jobnimbus Create Workflow Status — Add a status step to an existing workflow. Requires the numeric workflow id from account settings and status fields in record.
Jobnimbus Get Account Settings — Retrieve JobNimbus account settings including workflows, statuses, and account metadata.
Jobnimbus Get Activities — Fetch one activity log row by jnid or page the activity feed with filter_ JSON. The feed is high-volume — narrow with date or related-record filters before paging.
Jobnimbus Get Contacts — Fetch one CRM contact by jnid or page contacts with Elasticsearch filter_ JSON, sort_field, and optional field projection.
Jobnimbus Get Estimates — Fetch one estimate by jnid or page estimates with pagination and filters.
Jobnimbus Get Files — Page file attachment metadata (omit jnid) or download one attachment by jnid (returns base64 file bytes and content_type — not JSON metadata).
Jobnimbus Get Invoices — Fetch one invoice by jnid or page invoices with pagination and filters.
Frequently Asked Questions
Does this replace JobNimbus mobile or desktop apps?
No — it lets AI assistants read and update JobNimbus data you already store while you keep using JobNimbus for day-to-day field workflows.
Which JobNimbus permissions apply?
The connection uses your JobNimbus API key and its access profile. Agents only see and change records that key is allowed to touch.
Standard connector25 free calls every 30 days, then from $49/month
$49 / month
Subject to fair usage limits
$99 / month
Subject to fair usage limits
$199 / month
Subject to fair usage limits
Jobnimbus Get Jobs — Fetch one job or project by jnid or page jobs with filter_ JSON (status, contact, dates).
Jobnimbus Get Material Orders — Fetch one material order by jnid or page material orders with pagination and filters.
Jobnimbus Get Payments — Fetch one payment by jnid or page payments with pagination and filters.
Jobnimbus Get Products — Fetch one catalog product by jnid or page the product catalog with filters.
Jobnimbus Get Tasks — Fetch one task by jnid or page tasks with optional filter_ JSON and actor scoping.
Jobnimbus Get Workflows — Return workflow definitions and their statuses from account settings — use before filtering jobs by workflow or status name.
Jobnimbus Get Workorders — Fetch one work order by jnid or page work orders with pagination and filters.
Jobnimbus List Activities — List activity log entries (calls, emails, notes, status changes). The feed is high-volume — narrow with filter_ Elasticsearch JSON (date range, job, or contact fields) or use a small size with from_ pagination; do not pull large unfiltered pages. Optional actor scopes to a team member's visibility.
Jobnimbus List Contacts — List CRM contacts. Paginate with from_ and size; filter with filter_ JSON (Elasticsearch syntax) or scope to a team member via actor.
Jobnimbus List Files — List files attached to JobNimbus contacts and jobs. Paginate with from_ and size; optional filter_ JSON and actor scoping.
Jobnimbus List Jobs — List jobs/projects. Paginate with from_ and size; filter with filter_ JSON or scope to a team member via actor.
Jobnimbus List Tasks — List tasks across jobs. Paginate with from_ and size; optional filter_ JSON and actor scoping.
Jobnimbus Record Invoice Payment — Record a payment against an invoice jnid. Pass amount and payment fields in record.
Jobnimbus Send Invoice — Email an existing invoice to recipients. Pass the invoice jnid and optional send options in record.
Jobnimbus Upsert Contact — Create a CRM contact (POST) or update an existing contact by jnid (PUT). When jnid is omitted and record includes email, an existing contact with that email is updated instead of creating a duplicate. Custom fields use display names or cf_* keys as returned on reads.
Showing the first 25 tools — full list and schemas: Directory API.
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/jobnimbus. Authentication is handled automatically.
How many tools does JobNimbus provide?
JobNimbus provides 31 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does JobNimbus require?
JobNimbus uses API Key. JobNimbus requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in project management
Other MCP servers in this category from the directory index