Skip to content

JobNimbus MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat.

Deletes · 7
CompareRegistry entry

20 tools: 7 can delete or cancel things and 13 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http jobnimbus https://jobnimbus.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

20 tools

Deletes or cancels 7Claude Code: deny
  • jobnimbus_create_contactCreate a contact.No findings

    Why it is in this group

    • The name "jobnimbus_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a contact. Give at least one of first_name, last_name, display_name or company. record_type_name (a contact workflow, e.g. Customer) and status_name (a status in that workflow, e.g. Lead) are required and must match the account settings (jobnimbus_get_account_settings). Workflow automations may fire. JobNimbus: POST /contacts.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • jobnimbus_create_jobCreate a job (project).No findings

    Why it is in this group

    • The name "jobnimbus_create_job" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a job (project). name, record_type_name (a job workflow, e.g. Residential) and status_name (a status in it, e.g. Lead) are required and must match the account settings. Link the homeowner with primary_contact_id. Workflow automations may fire. JobNimbus: POST /jobs.

    Annotations the server declares

    • title: Create a job
    • destructiveHint: true
  • jobnimbus_create_noteAdd a note (activity entry) to a contact or job's activity feed.No findings

    Why it is in this group

    • The name "jobnimbus_create_note" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add a note (activity entry) to a contact or job's activity feed. record_type_name defaults to Note; use another activity type from the account settings if needed. JobNimbus: POST /activities.

    Annotations the server declares

    • title: Add a note
    • destructiveHint: true
  • jobnimbus_create_taskCreate a task or appointment on a contact or job.No findings

    Why it is in this group

    • The name "jobnimbus_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a task or appointment on a contact or job. title, date_start (unix seconds) and record_type_name (a task type from the account settings, e.g. Task or Appointment) are required; related_id links it to the contact/job. JobNimbus: POST /tasks.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • jobnimbus_update_contactEdit fields on an existing contact — only the fields you pass change.No findings

    Why it is in this group

    • The name "jobnimbus_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Edit fields on an existing contact — only the fields you pass change. Changing status_name moves it along its workflow (automations may fire). Cannot delete or archive. JobNimbus: PUT /contacts/{jnid}.

    Annotations the server declares

    • title: Update a contact
    • destructiveHint: true
  • jobnimbus_update_jobEdit fields on an existing job — e.g.No findings

    Why it is in this group

    • The name "jobnimbus_update_job" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Edit fields on an existing job — e.g. move it to a new status_name, change the address, sales rep or dates. Only the fields you pass change; if JobNimbus rejects a status change, pass record_type_name alongside status_name. Automations may fire. Cannot delete or archive. JobNimbus: PUT /jobs/{jnid}.

    Annotations the server declares

    • title: Update a job
    • destructiveHint: true
  • jobnimbus_update_taskEdit an existing task — reschedule it, change the title or priority, reassign it, or mark it complete with is_completed=true (reopen with false).No findings

    Why it is in this group

    • The name "jobnimbus_update_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Edit an existing task — reschedule it, change the title or priority, reassign it, or mark it complete with is_completed=true (reopen with false). Only the fields you pass change. Cannot delete. JobNimbus: PUT /tasks/{jnid}.

    Annotations the server declares

    • title: Update a task
    • destructiveHint: true
Only reads 13Claude Code: allow
  • jobnimbus_get_account_settingsFetch the account's configuration: contact and job workflows with their statuses, task types, activity (note) types, file types and lead sources.No findings

    Why it is in this group

    • The name "jobnimbus_get_account_settings" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the account's configuration: contact and job workflows with their statuses, task types, activity (note) types, file types and lead sources. Use it to find the exact record_type_name / status_name / source_name values the create and update tools need. Pass field (e.g. groups) to get just one setting. JobNimbus: GET /account/settings.

    Annotations the server declares

    • title: Get account settings
    • readOnlyHint: true
  • jobnimbus_get_contactFetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields.No findings

    Why it is in this group

    • The name "jobnimbus_get_contact" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.

    Annotations the server declares

    • title: Get one contact
    • readOnlyHint: true
  • jobnimbus_get_invoiceFetch a single invoice by jnid, including line items, payments applied, total, total_paid and due.No findings

    Why it is in this group

    • The name "jobnimbus_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.

    Annotations the server declares

    • title: Get one invoice
    • readOnlyHint: true
  • jobnimbus_get_jobFetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields.No findings

    Why it is in this group

    • The name "jobnimbus_get_job" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.

    Annotations the server declares

    • title: Get one job
    • readOnlyHint: true
  • jobnimbus_get_taskFetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records.No findings

    Why it is in this group

    • The name "jobnimbus_get_task" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.

    Annotations the server declares

    • title: Get one task
    • readOnlyHint: true
  • jobnimbus_list_activitiesList activity entries — notes plus system events such as status changes and record creation — optionally for one contact or job (related_id).No findings

    Why it is in this group

    • The name "jobnimbus_list_activities" says "list": a word for reading.
    Description, as the server wrote it
    List activity entries — notes plus system events such as status changes and record creation — optionally for one contact or job (related_id). Returns {count, activity}. JobNimbus: GET /activities.

    Annotations the server declares

    • title: List activity and notes
    • readOnlyHint: true
  • jobnimbus_list_contactsList contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query.No findings

    Why it is in this group

    • The name "jobnimbus_list_contacts" says "list": a word for reading.
    Description, as the server wrote it
    List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.

    Annotations the server declares

    • title: List or search contacts
    • readOnlyHint: true
  • jobnimbus_list_estimatesList estimates with number, status, line items, subtotal, tax, total, margin, e-sign state and related job/contact.No findings

    Why it is in this group

    • The name "jobnimbus_list_estimates" says "list": a word for reading.
    Description, as the server wrote it
    List estimates with number, status, line items, subtotal, tax, total, margin, e-sign state and related job/contact. Returns {count, results}; count is the account total. JobNimbus: GET /v2/estimates.

    Annotations the server declares

    • title: List estimates
    • readOnlyHint: true
  • jobnimbus_list_filesList file attachments (photos, documents) with filename, content type, size, file type and the contact/job they belong to — optionally for one record (related_id).No findings

    Why it is in this group

    • The name "jobnimbus_list_files" says "list": a word for reading.
    Description, as the server wrote it
    List file attachments (photos, documents) with filename, content type, size, file type and the contact/job they belong to — optionally for one record (related_id). Metadata only; file bytes are not downloaded. Returns {count, files}. JobNimbus: GET /files.

    Annotations the server declares

    • title: List file attachments
    • readOnlyHint: true
  • jobnimbus_list_invoicesList invoices with number, status, line items, total, total_paid, amount due, due date and related job/contact.No findings

    Why it is in this group

    • The name "jobnimbus_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices with number, status, line items, total, total_paid, amount due, due date and related job/contact. Returns {count, results}; count is the account total. JobNimbus: GET /v2/invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • jobnimbus_list_jobsList jobs (projects), newest first by default, optionally filtered — e.g.No findings

    Why it is in this group

    • The name "jobnimbus_list_jobs" says "list": a word for reading.
    Description, as the server wrote it
    List jobs (projects), newest first by default, optionally filtered — e.g. by status {"must":[{"term":{"status_name":"Lead"}}]} or by the related contact via related_id. Returns {count, results}. JobNimbus: GET /jobs.

    Annotations the server declares

    • title: List or search jobs
    • readOnlyHint: true
  • jobnimbus_list_tasksList tasks and appointments, optionally for one contact or job (related_id) or filtered, e.g.No findings

    Why it is in this group

    • The name "jobnimbus_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    List tasks and appointments, optionally for one contact or job (related_id) or filtered, e.g. open ones: {"must":[{"term":{"is_completed":false}}]}. Returns {count, results}. JobNimbus: GET /tasks.

    Annotations the server declares

    • title: List or search tasks
    • readOnlyHint: true
  • jobnimbus_list_usersList the account's JobNimbus users (team members) with name, email, id and whether they are active.No findings

    Why it is in this group

    • The name "jobnimbus_list_users" says "list": a word for reading.
    Description, as the server wrote it
    List the account's JobNimbus users (team members) with name, email, id and whether they are active. The id is what owners, sales_rep and owner_ids take. JobNimbus: GET /account/users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http jobnimbus https://jobnimbus.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jobnimbus__jobnimbus_get_account_settings",
      "mcp__jobnimbus__jobnimbus_list_users",
      "mcp__jobnimbus__jobnimbus_list_contacts",
      "mcp__jobnimbus__jobnimbus_get_contact",
      "mcp__jobnimbus__jobnimbus_list_jobs",
      "mcp__jobnimbus__jobnimbus_get_job",
      "mcp__jobnimbus__jobnimbus_list_tasks",
      "mcp__jobnimbus__jobnimbus_get_task",
      "mcp__jobnimbus__jobnimbus_list_activities",
      "mcp__jobnimbus__jobnimbus_list_files",
      "mcp__jobnimbus__jobnimbus_list_estimates",
      "mcp__jobnimbus__jobnimbus_list_invoices",
      "mcp__jobnimbus__jobnimbus_get_invoice"
    ],
    "ask": [],
    "deny": [
      "mcp__jobnimbus__jobnimbus_create_contact",
      "mcp__jobnimbus__jobnimbus_update_contact",
      "mcp__jobnimbus__jobnimbus_create_job",
      "mcp__jobnimbus__jobnimbus_update_job",
      "mcp__jobnimbus__jobnimbus_create_task",
      "mcp__jobnimbus__jobnimbus_update_task",
      "mcp__jobnimbus__jobnimbus_create_note"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as jobnimbus. Review it before you use it.