A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Jobnimbus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-jobnimbus-mcp https://jobnimbus.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# jobnimbus_get_account_settings, jobnimbus_list_users, jobnimbus_list_contacts and 17 more
Jobnimbus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-jobnimbus-mcp https://jobnimbus.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| field | string | no | Return only this setting, e.g. groups. |
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.
No parameter schema on file.
List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
| sort_field | string | no | Field to sort by (API default date_created), e.g. date_updated. |
| sort_direction | string | no | Sort direction (API default desc). |
| filter | object | no | ElasticSearch-style bool query object, sent as the filter parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{" |
Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The contact's jnid (JobNimbus record id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
| sort_field | string | no | Field to sort by (API default date_created), e.g. date_updated. |
| sort_direction | string | no | Sort direction (API default desc). |
| filter | object | no | ElasticSearch-style bool query object, sent as the filter parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{" |
| related_id | string | no | Only records related to this contact or job jnid (adds a related.id term to the filter). |
Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The job's jnid (JobNimbus record id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
| sort_field | string | no | Field to sort by (API default date_created), e.g. date_updated. |
| sort_direction | string | no | Sort direction (API default desc). |
| filter | object | no | ElasticSearch-style bool query object, sent as the filter parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{" |
| related_id | string | no | Only records related to this contact or job jnid (adds a related.id term to the filter). |
Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The task's jnid (JobNimbus record id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
| sort_field | string | no | Field to sort by (API default date_created), e.g. date_updated. |
| sort_direction | string | no | Sort direction (API default desc). |
| filter | object | no | ElasticSearch-style bool query object, sent as the filter parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{" |
| related_id | string | no | Only records related to this contact or job jnid (adds a related.id term to the filter). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
| sort_field | string | no | Field to sort by (API default date_created), e.g. date_updated. |
| sort_direction | string | no | Sort direction (API default desc). |
| filter | object | no | ElasticSearch-style bool query object, sent as the filter parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{" |
| related_id | string | no | Only records related to this contact or job jnid (adds a related.id term to the filter). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000). |
| from | integer | no | Zero-based offset for pagination (default 0). Next page: from + size. |
Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The invoice's jnid (JobNimbus record id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record_type_name | string | yes | Contact workflow name, e.g. Customer. |
| status_name | string | yes | Status within that workflow, e.g. Lead. |
| first_name | string | no | First name. |
| last_name | string | no | Last name. |
| display_name | string | no | Display name. |
| company | string | no | Company name. |
| string | no | Email address. | |
| home_phone | string | no | Home phone. |
| mobile_phone | string | no | Mobile phone. |
| work_phone | string | no | Work phone. |
| fax_number | string | no | Fax number. |
| website | string | no | Website. |
| description | string | no | Description / notes on the contact record. |
| address_line1 | string | no | Street address, line 1. |
| address_line2 | string | no | Street address, line 2. |
| city | string | no | City. |
| state_text | string | no | State, e.g. UT. |
| zip | string | no | Postal code. |
| country_name | string | no | Country, e.g. United States. |
| source_name | string | no | Lead source name, e.g. Referral — must be one of the account's lead sources. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The contact's jnid (JobNimbus record id). |
| record_type_name | string | no | Move to this contact workflow. |
| status_name | string | no | New workflow status name. |
| first_name | string | no | First name. |
| last_name | string | no | Last name. |
| display_name | string | no | Display name. |
| company | string | no | Company name. |
| string | no | Email address. | |
| home_phone | string | no | Home phone. |
| mobile_phone | string | no | Mobile phone. |
| work_phone | string | no | Work phone. |
| fax_number | string | no | Fax number. |
| website | string | no | Website. |
| description | string | no | Description / notes on the contact record. |
| address_line1 | string | no | Street address, line 1. |
| address_line2 | string | no | Street address, line 2. |
| city | string | no | City. |
| state_text | string | no | State, e.g. UT. |
| zip | string | no | Postal code. |
| country_name | string | no | Country, e.g. United States. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Job name, e.g. Smith Roof Replacement. |
| record_type_name | string | yes | Job workflow name. |
| status_name | string | yes | Status within that workflow. |
| description | string | no | Job description. |
| address_line1 | string | no | Street address, line 1. |
| address_line2 | string | no | Street address, line 2. |
| city | string | no | City. |
| state_text | string | no | State, e.g. UT. |
| zip | string | no | Postal code. |
| country_name | string | no | Country, e.g. United States. |
| source_name | string | no | Lead source name — must be one of the account's lead sources. |
| sales_rep | string | no | jnid of the user who is the sales rep. |
| primary_contact_id | string | no | jnid of the job's primary contact (sent as primary.id). |
| date_start | integer | no | Start date, unix seconds. |
| date_end | integer | no | End date, unix seconds. |
| custom_fields | object | no | Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored. |
| actor | string | no | Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The job's jnid (JobNimbus record id). |
| name | string | no | New job name. |
| record_type_name | string | no | Job workflow name. |
| status_name | string | no | New workflow status name. |
| description | string | no | Job description. |
| address_line1 | string | no | Street address, line 1. |
| address_line2 | string | no | Street address, line 2. |
| city | string | no | City. |
| state_text | string | no | State, e.g. UT. |
| zip | string | no | Postal code. |
| country_name | string | no | Country, e.g. United States. |
| source_name | string | no | Lead source name — must be one of the account's lead sources. |
| sales_rep | string | no | jnid of the user who is the sales rep. |
| primary_contact_id | string | no | jnid of the job's primary contact (sent as primary.id). |
| date_start | integer | no | Start date, unix seconds. |
| date_end | integer | no | End date, unix seconds. |
| custom_fields | object | no | Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored. |
| actor | string | no | Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Task title. |
| date_start | integer | yes | Start (or due) time, unix seconds. |
| record_type_name | string | yes | Task type name, e.g. Task or Appointment. |
| related_id | string | yes | jnid of the contact or job this task belongs to (sent as related: [{id}]). |
| date_end | integer | no | End time, unix seconds. |
| description | string | no | Task details. |
| priority | integer | no | Priority: 0 none, 1 high, 2 medium, 3 low. |
| estimated_time | integer | no | Estimated minutes. |
| owner_ids | array | no | jnids of the users to assign (sent as owners: [{id}]). |
| actor | string | no | Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jnid | string | yes | The task's jnid (JobNimbus record id). |
| title | string | no | New title. |
| date_start | integer | no | New start time, unix seconds. |
| date_end | integer | no | New end time, unix seconds. |
| description | string | no | New details. |
| priority | integer | no | Priority: 0 none, 1 high, 2 medium, 3 low. |
| is_completed | boolean | no | true marks the task done; false reopens it. |
| estimated_time | integer | no | Estimated minutes. |
| actual_time | integer | no | Minutes logged. |
| owner_ids | array | no | jnids of the users to assign (sent as owners: [{id}]). |
| actor | string | no | Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| primary_id | string | yes | jnid of the contact or job the note belongs to (sent as primary.id). |
| note | string | yes | The note text. |
| record_type_name | string | no | Activity type name. Defaults to Note. |
| is_private | boolean | no | Mark the note private. |
| actor | string | no | Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jobnimbus or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Jobnimbus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.