FieldPulse MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/fieldpulse and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 23 Oct 2026. Not supplied by the maker.

• fieldpulse_list_customers

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

• fieldpulse_get_customer

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

• fieldpulse_list_customer_contacts

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

• fieldpulse_get_customer_contact

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

• fieldpulse_list_jobs

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

• fieldpulse_get_job

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

• fieldpulse_list_job_status_workflows

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

• fieldpulse_list_job_workflow_statuses

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