FieldPulse MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://fieldpulse.usefulapi.io/mcp

claude mcp add --transport http fieldpulse https://fieldpulse.usefulapi.io/mcp

{
  "mcpServers": {
    "fieldpulse": {
      "url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "fieldpulse": {
      "type": "http",
      "url": "https://fieldpulse.usefulapi.io/mcp"
    }
  }
}

https://fieldpulse.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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.

• fieldpulse_list_estimates

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

• fieldpulse_get_estimate

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

• fieldpulse_list_invoices

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

• fieldpulse_get_invoice

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

• fieldpulse_list_payments

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

• fieldpulse_get_payment

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

• fieldpulse_list_assets

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

• fieldpulse_get_asset

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

• fieldpulse_list_asset_categories

  List asset categories. GET /assets-category.

• fieldpulse_list_locations

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

• fieldpulse_get_location

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

• fieldpulse_list_projects

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

• fieldpulse_get_project

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

• fieldpulse_list_contracts

  List contracts (maintenance agreements). GET /contracts.

• fieldpulse_get_contract

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

• fieldpulse_list_items

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

• fieldpulse_get_item

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

• fieldpulse_list_purchase_orders

  List purchase orders. GET /purchase-orders.

• fieldpulse_get_purchase_order

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

• fieldpulse_list_vendors

  List vendors (suppliers). GET /vendors.

• fieldpulse_get_vendor

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

• fieldpulse_list_company_profiles

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

• fieldpulse_list_users

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

• fieldpulse_list_teams

  List the account's teams. GET /teams.

• fieldpulse_list_tags

  List tags for customers or jobs. GET /tags.

• fieldpulse_list_lead_sources

  List customer lead sources. GET /lead-source.

• fieldpulse_list_pipeline_statuses

  List customer pipeline statuses. GET /pipeline-status.

• fieldpulse_list_custom_fields

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

• fieldpulse_list_comments

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

• fieldpulse_list_subtasks

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

• fieldpulse_list_timesheets

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

• fieldpulse_create_customer

  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.

• fieldpulse_update_customer

  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}.

• fieldpulse_create_job

  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.

• fieldpulse_update_job

  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; Fi

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 79 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 43 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32398 servers in this category
• Published to the registry more recently than 97% of the other 32398 servers in this category
• Basic checks equal to or better than 100% of the other 32398 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{