FieldPulse MCP by usefulapi

MCP server · hosted · v1.0.1 · io.usefulapi/fieldpulse

Online · tested 3h agoNEW · 3h agoSeen in the registry 2h ago

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

What it does

FieldPulse MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: invoicing. That makes it a candidate for tasks such as send and chase invoices.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 43 tools

Version1.0.1

PriceNot in the registry

First seen23 Oct 2026

Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)

Hosted endpoint

https://fieldpulse.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http fieldpulse-mcp-by-usefulapi https://fieldpulse.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 3h ago

ONLINE FieldPulse MCP by usefulapi answered an MCP connection on 23 Oct 2026 and introduced itself as fieldpulse-mcp 1.0.1 (MCP protocol 2025-06-18).

43 tools offered to AI assistants

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

Show 31 more

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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers

Send and chase invoices

Invoicing

50%

Similar tools

Listed for the same task: send and chase invoices

FoxyInvoiceREMOTELOCAL
Invoicing tools for AI assistants: clients, draft invoices with computed tax, and email sending
APICK SubagentREMOTELOCAL
Document inventory, extraction, summaries and comparison with source quotes and usage billing
AppDirect MCPREMOTELOCAL
AppDirect marketplace operations with an offline mirror and cross-company billing reconciliation
GetCourier (moved)REMOTELOCAL
Moved to dev.getcourier/getcourier. Email inboxes for AI agents at getcourier.dev/mcp
mcp-serverREMOTELOCAL
MCP server for Hostkey .com (InvAPI): servers, power, order, DNS, S3, billing
Oryah MailREMOTELOCAL
Governed email for agents: Gmail, M365 and IMAP; per-mailbox permissions, send allowlist, audit log

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Booke AI51
$129/mo
Apollo.io90
$49/mo · free plan
Ramp (AI agents)86
$15/mo · free plan

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://fieldpulse.usefulapi.io/mcp	DECLARED	SRC-001 Official MCP Registry	2h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	2h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	2h ago
Website	https://usefulapi.io/fieldpulse/	DECLARED	SRC-001 Official MCP Registry	2h ago
Repository	https://github.com/m190/usefulapi-mcp	DECLARED	SRC-001 Official MCP Registry	2h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	2h ago
Version	1.0.1	DECLARED	SRC-001 Official MCP Registry	2h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	2h ago

Change history

NEW23 Oct 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is FieldPulse MCP by usefulapi still online?

Free alerts · no account

Questions about FieldPulse MCP by usefulapi

How do I connect FieldPulse MCP by usefulapi?

Use the hosted endpoint https://fieldpulse.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does FieldPulse MCP by usefulapi offer?

When Electra Index connected on 23 Oct 2026, it listed 43 tools: fieldpulse_list_customers, fieldpulse_get_customer, fieldpulse_list_customer_contacts, fieldpulse_get_customer_contact, fieldpulse_list_jobs, fieldpulse_get_job, fieldpulse_list_job_status_workflows, fieldpulse_list_job_workflow_statuses and more. The full list is in "Live check" above.

Is FieldPulse MCP by usefulapi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.

What can I use FieldPulse MCP by usefulapi for?

Based on its description, it is most relevant to: send and chase invoices.