FieldPulse MCP by usefulapi

WRITE: create a customer (lead or account). Give first_name and/or last_name, or a unique display_name. Creates a new record every call; check fieldpulse_list_customers first to avoid duplicates. POST /customers.

WRITE: create a job for an existing customer. Needs customer_id, job_type and the numeric billing value FieldPulse requires; set a status (1-6) or a custom status_id + status_workflow_id. Creates a new job every call. POST /jobs.

One asset by id. GET /assets/{id}.

One contract by id. GET /contracts/{id}.

One customer by id. GET /customers/{id}.

One contact of a customer. GET /customers/{customerId}/customer-contact/{contactId}.

One estimate by id. GET /estimates/{id}.

One invoice by id. GET /invoices/{id}.

One invoice item by id. GET /items/{id}.

One job by id, optionally with its custom field values. GET /jobs/{id}.

One location by id. GET /locations/{id}.

One payment by id. GET /payments/{id}.

One project by id. GET /projects/{id}.

One purchase order by id. GET /purchase-orders/{id}.

One vendor by id. GET /vendors/{id}.

List asset categories. GET /assets-category.

List or search customer assets (equipment) by install status. GET /assets.

List comments on a record (customer, job, project, subtasks, invoice). GET /comments.

The company profile(s) of this FieldPulse account (name, address, contact details, settings). GET /company-profile.

List contracts (maintenance agreements). GET /contracts.

List custom field definitions, optionally for one object type. GET /custom-fields.

The contacts (people) of one customer. GET /customers/{customerId}/customer-contact.

List or search customers (name, email, phone, address, status, assigned user). GET /customers.

List or search estimates (customer, status, totals, line items). GET /estimates.

List or search invoices (customer, status, totals, due dates). GET /invoices.

List the invoice item catalog (products and services with prices). GET /items.

The job status workflows (use their ids with fieldpulse_list_job_workflow_statuses and when setting a custom job status). GET /jobs/status-workflows.

The custom job statuses of all workflows, with their ids (for filtering jobs or setting a status). GET /jobs/status-workflow-statuses.

List or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids. GET /jobs.

List customer lead sources. GET /lead-source.

List locations (service addresses) of a customer or a job. GET /locations.

List or search payments (amount, method, date, invoice). GET /payments.

List customer pipeline statuses. GET /pipeline-status.

List or search projects (status, completion). GET /projects.

List purchase orders. GET /purchase-orders.

List subtasks (job checklist items) by status or assigned user. GET /subtasks.

List tags for customers or jobs. GET /tags.

List the account's teams. GET /teams.

List timesheet entries (clock in/out), optionally for one user or a time window. GET /timesheets.

List the account's users (team members) with ids for assignments. GET /users.

List vendors (suppliers). GET /vendors.

WRITE: change fields of one customer (only the fields you pass). If FieldPulse asks for a name, include first_name/last_name or display_name. PUT /customers/{customerId}.

WRITE: change a job: status, schedule, notes, assignments, location. FieldPulse requires customer_id, job_type and billing on every update, so this reads the job first and keeps those (and its current status) unless you pass new values. The read and the write are two requests; FieldPulse offers no version check. PUT /jobs/{jobId}.