mcpbeat Sign in

JobNimbus MCP by usefulapi MCP Server

answering

JobNimbus MCP by usefulapi is answering right now. Last checked 3 min ago. It exposes 20 tools. Last commit 10 Oct 2026.

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

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
20
Tools
read from the server
132 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
30 Sep a tool changed version2 times that day
and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check JobNimbus MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add jobnimbus --transport http https://jobnimbus.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "jobnimbus": {
      "url": "https://jobnimbus.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.jobnimbus]
url = "https://jobnimbus.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jobnimbus": {
      "url": "https://jobnimbus.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "jobnimbus": {
      "url": "https://jobnimbus.usefulapi.io/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

jobnimbus
jobnimbus_create_contact
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.
jobnimbus_create_job
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.
jobnimbus_create_note
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.
jobnimbus_create_task
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.
jobnimbus_get_account_settings
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.
jobnimbus_get_contact
Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.
jobnimbus_get_invoice
Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.
jobnimbus_get_job
Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.
jobnimbus_get_task
Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.
jobnimbus_list_activities
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.
jobnimbus_list_contacts
List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.
jobnimbus_list_estimates
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.
jobnimbus_list_files
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.
jobnimbus_list_invoices
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.
jobnimbus_list_jobs
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.
jobnimbus_list_tasks
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.
jobnimbus_list_users
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.
jobnimbus_update_contact
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}.
jobnimbus_update_job
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}.
jobnimbus_update_task
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}.

Endpoints

URLTransportStateLatencyChecked
https://jobnimbus.usefulapi.io/mcp streamable-http answering 68 ms 3 min ago

Alternatives to JobNimbus MCP by usefulapi

same job, measured the same way
Invoice Ninja MCP by usefulapi
by usefulapi

Manage Invoice Ninja clients, invoices, quotes, expenses, tasks and projects.

24 tools answering
FreeAgent MCP by usefulapi
by usefulapi

Read FreeAgent contacts, invoices, bills, banking and reports; add contacts, draft invoices, time.

20 tools answering
Harvest MCP by usefulapi
by usefulapi

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

20 tools answering
Paymo MCP by usefulapi
by usefulapi

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

21 tools answering
Lexware Office MCP by usefulapi
by usefulapi

Read Lexware Office contacts, articles, invoices and vouchers; create contacts and draft invoices.

21 tools answering
Jobkeepr
by jobkeepr

Manage jobs, customers, scheduling, estimates and invoices for a field service business.

answering
Mercoa MCP by usefulapi
by usefulapi

Query and manage Mercoa AP/AR bill-pay: entities, invoices, transactions and payment methods.

17 tools answering
Quaderno MCP by usefulapi
by usefulapi

MCP server for Quaderno — tax-rate calculation, invoices, contacts, products, receipts & expenses.

23 tools answering

JobNimbus MCP by usefulapi — questions

Answers built from our own checks of this server.

What can JobNimbus MCP by usefulapi do?
It exposes 20 tools, read directly from the server on our last check. Among them: jobnimbus_create_contact, jobnimbus_create_job, jobnimbus_create_note, jobnimbus_create_task, jobnimbus_get_account_settings, jobnimbus_get_contact and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is JobNimbus MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 132 ms. The bar chart above shows every period we have measured.
How do I connect JobNimbus MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does JobNimbus MCP by usefulapi need an API key?
No. JobNimbus MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is JobNimbus MCP by usefulapi?
It answers our handshake in 132 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is JobNimbus MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.