FieldPulse MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

FieldPulse MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 43 tools. Last commit 25 Oct 2026.

Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.

Uptime history 45 hours of history

45 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

276 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 October 2026. No other catalogue keeps this.

25 Oct a tool changed version3 times that day

24 Oct a tool changed version3 times that day

and 4 more, back to 24 October 2026

Nothing serious here today

Today is the operative word: we check FieldPulse MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://fieldpulse.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.fieldpulse]
url = "https://fieldpulse.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 43

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fieldpulse

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_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_get_asset

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

fieldpulse_get_contract

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

fieldpulse_get_customer

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

fieldpulse_get_customer_contact

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

fieldpulse_get_estimate

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

fieldpulse_get_invoice

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

fieldpulse_get_item

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

fieldpulse_get_job

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

fieldpulse_get_location

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

fieldpulse_get_payment

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

fieldpulse_get_project

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

fieldpulse_get_purchase_order

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

fieldpulse_get_vendor

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

fieldpulse_list_asset_categories

List asset categories. GET /assets-category.

fieldpulse_list_assets

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

fieldpulse_list_comments

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

fieldpulse_list_company_profiles

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

fieldpulse_list_contracts

List contracts (maintenance agreements). GET /contracts.

fieldpulse_list_custom_fields

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

fieldpulse_list_customer_contacts

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

fieldpulse_list_customers

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

fieldpulse_list_estimates

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

fieldpulse_list_invoices

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

fieldpulse_list_items

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

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_jobs

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

fieldpulse_list_lead_sources

List customer lead sources. GET /lead-source.

fieldpulse_list_locations

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

fieldpulse_list_payments

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

fieldpulse_list_pipeline_statuses

List customer pipeline statuses. GET /pipeline-status.

fieldpulse_list_projects

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

fieldpulse_list_purchase_orders

List purchase orders. GET /purchase-orders.

fieldpulse_list_subtasks

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

fieldpulse_list_tags

List tags for customers or jobs. GET /tags.

fieldpulse_list_teams

List the account's teams. GET /teams.

fieldpulse_list_timesheets

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

fieldpulse_list_users

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

fieldpulse_list_vendors

List vendors (suppliers). GET /vendors.

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_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; FieldPulse offers no version check. PUT /jobs/{jobId}.

Endpoints

URL	Transport	State	Latency	Checked
https://fieldpulse.usefulapi.io/mcp	streamable-http	answering	335 ms	1 min ago

Alternatives to FieldPulse MCP by usefulapi

same job, measured the same way

Service Fusion MCP by usefulapi

by usefulapi

Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs.

26 tools answering

Orb MCP by usefulapi

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Zenbooker MCP by usefulapi

by usefulapi

Read Zenbooker jobs, customers, invoices and timeslots; add customers and job notes.

21 tools answering

Method CRM MCP by usefulapi

by usefulapi

Query Method CRM customers, leads, activities and invoices; create and update records.

16 tools answering

Paymo MCP by usefulapi

by usefulapi

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

21 tools answering

Harvest MCP by usefulapi

by usefulapi

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

20 tools answering

Merit Aktiva MCP by usefulapi

by usefulapi

Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.

26 tools answering

Invoiced MCP by usefulapi

by usefulapi

Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes.

27 tools answering

FieldPulse MCP by usefulapi — questions

Answers built from our own checks of this server.

What can FieldPulse MCP by usefulapi do?

It exposes 43 tools, read directly from the server on our last check. Among them: fieldpulse_create_customer, fieldpulse_create_job, fieldpulse_get_asset, fieldpulse_get_contract, fieldpulse_get_customer, fieldpulse_get_customer_contact and 37 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is FieldPulse MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 276 ms. The bar chart above shows every period we have measured.

How do I connect FieldPulse MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does FieldPulse MCP by usefulapi need an API key?

No. FieldPulse MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 43 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FieldPulse MCP by usefulapi?

It answers our handshake in 276 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is FieldPulse MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at fieldpulse.usefulapi.io, which runs on its operator's own terms.