FieldPulse MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 79 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 43 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32410 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32410 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 32410 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{