MCP serverio.usefulapi/jobnimbus
Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat.
Overview
Score?
UNRATED 0.130
of what a free look can see, on 1 looks
Looks
6
last 8 hr ago
Tools
20
More info
URL
jobnimbus.usefulapi.io/mcp
streamable-http
Says it is
jobnimbus-mcp 1.0.0
protocol 2025-06-18
In the record since
4 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.130 · highest on record 0.8561
Toolsfrom sha256:b2bdbfc579…8d98d0
| Tool | Schema |
|---|---|
| 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 workfl |
input · no output |
| 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 |
input · no output |
| 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 / |
input · no output |
| 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 requir |
input · no output |
| 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_ty |
input · no output |
| 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}. |
input · no output |
| jobnimbus_get_invoice Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}. |
input · no output |
| 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}. |
input · no output |
| 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}. |
input · no output |
| 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: |
input · no output |
| jobnimbus_list_contacts List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: G |
input · no output |
| 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: |
input · no output |
| 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; f |
input · no output |
| 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 |
input · no output |
| 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 {co |
input · no output |
| 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}. JobNi |
input · no output |
| 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/use |
input · no output |
| 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: |
input · no output |
| 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, p |
input · no output |
| 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. C |
input · no output |
Verify it yourself
npx teppi-check https://jobnimbus.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M3RGE5BWV32GTA3F7MN5QK7V