io.usefulapi由 usefulapi.io 发布官方发布者v1.1.4更新于 Nov 7, 2026
Read work orders, customers and invoices; create customers, notes and work orders in FieldEdge.
发布方自己的服务：Ably MCP by usefulapi
将助手连接到 FieldEdge 现场服务账户，读取工单、客户、发票和库存，并可创建客户、备注和工单。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.usefulapi%2Ffieldedge/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"fieldedge-by-usefulapi": {
"type": "http",
"url": "https://fieldedge.usefulapi.io/mcp"
}
}
}Use your FieldEdge account from Claude, Cursor, or any MCP client. Read work orders, customers, invoices and agreements, and create customers, notes and work orders. Hosted, no local install: connect with your own credentials.
Live endpoint: https://fieldedge.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://fieldedge.usefulapi.io/mcp.claude mcp add --transport http fieldedge https://fieldedge.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your FieldEdge credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/fieldedge/
On first connect you provide your Client ID and Client secret from a FieldEdge Marketplace app, and your Tenant ID from the FieldEdge web portal. The server validates it and stores it per user. No keys go in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with fieldedge_upgrade (it returns a Stripe Checkout link). Cancel any time with fieldedge_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fieldedge_upgrade before then undoes the cancel. Or write to [email protected].
MIT — see LICENSE. Documentation only; the server is hosted.
来源：servers/fieldedge/README.md，提交 2450437
List work orders
List work orders (jobs) of the company with status, service address, customer, primary technician and linked invoice. Filters combine with AND; assigned=false cannot be combined with primary_tech_id. Needs scope workorders:read. GET /open-api/v1/work-orders.
sortlimitoffsetassignedcompletedcustomer_idinvoice_addedprimary_tech_idGet a work order
One work order: status, assignments, service address, task, tags and linked invoice. Needs scope workorders:read. GET /open-api/v1/work-orders/{work_order_id}.
work_order_id必填Find work orders at an address
Work orders at a service address, most recent first, each with its customer's name. All of address_line_1, city, state and postal_code are required. Needs scope workorders:read. GET /open-api/v1/work-orders/search/by-address.
city必填limitstate必填offsetpostal_code必填address_line_1必填address_line_2List a work order's technician assignments
Technician assignments (schedule, status) on one work order. Needs scope workorders:read. GET /open-api/v1/work-orders/{workOrderId}/assignments.
sortlimitoffsetstatusschedule_toschedule_fromtechnician_idwork_order_id必填Search customers
Search customers (personal data). With no filter all customers are listed. Needs scope customers:read. GET /open-api/v1/customers/search.
sortemaillimitphoneoffsetfirst_nameupdated_afterupdated_beforehas_service_agreementGet a customer
One customer (or job location) by id, with contact details and address (personal data). The reply says whether the record is a job or a billing customer. Needs scope customers:read. GET /open-api/v1/customers/id/{customer_id}.
customer_id必填Find a customer by phone number
The customer with this phone number (personal data). Needs scope customers:read. GET /open-api/v1/customer/{phone}.
phone必填Find customers at an address
Customers at a street address (personal data). address_line_1, city, state and postal_code are required. Needs scope customers:read. GET /open-api/v1/customers/by-address.
city必填sortlimitstate必填offsetpostal_code必填address_line_1必填address_line_2List a customer's notes
Notes on a customer record, newest first by default. Needs scope customers:read. GET /open-api/v1/customers/{customerId}/notes.
sortlimitoffsetcustomer_id必填List a customer's file attachments
File attachments on a customer record, each with the blob URL to view or download it. Needs scope customers:read. GET /open-api/v1/customers/{customerId}/attachments.
sortlimitoffsetcustomer_id必填List customer tags
Reusable customer tags of the account. Needs scope customers:read. GET /open-api/v1/tags.
namesortlimitoffsetList invoices
Invoices by invoice date, without line items (use fieldedge_get_invoice for those). Needs scope invoices:read. GET /open-api/v1/invoices.
sortlimitoffsetGet an invoice
One invoice with its line items; the invoice id equals its work order id. Needs scope invoices:read. GET /open-api/v1/invoices/{invoice_id}.
invoice_id必填List quotes
Quotes, without line items (use fieldedge_get_quote for those). Prefer class_id over class_name. Needs scope workorders:read. GET /open-api/v1/quotes.
idlimitoffsetclass_idclass_namecustomer_idGet a quote
One quote with its line items; the quote id equals its work order id. Needs scope workorders:read. GET /open-api/v1/quotes/{quote_id}.
quote_id必填List service agreements
Service agreements (recurring maintenance contracts) with plan, dates and customer. Needs scope workorders:read. GET /open-api/v1/agreements.
sortlimitactiveoffsetplan_namecustomer_idagreement_numbernext_service_afternext_invoice_beforenext_service_beforeGet a service agreement
One service agreement by id. Needs scope workorders:read. GET /open-api/v1/agreements/{agreement_id}.
agreement_id必填List employees
Employees (technicians, dispatchers, CSRs, admins). Needs scope employees:read. GET /open-api/v1/employees.
rolesortlimitactiveoffsetGet an employee
One employee record. Needs scope employees:read. GET /open-api/v1/employees/{employee_id}.
employee_id必填List business units
Business units (needed to create a work order). Needs scope business-units:read. GET /open-api/v1/business-units.
namesortlimitactiveoffsetGet a business unit
One business unit by id. Needs scope business-units:read. GET /open-api/v1/business-units/{business_unit_id}.
business_unit_id必填List lead sources
Lead sources (needed to create a work order). Needs scope lead-sources:read. GET /open-api/v1/lead-sources.
namesortlimitactiveoffsetbusiness_unit_idGet a lead source
One lead source by id. Needs scope lead-sources:read. GET /open-api/v1/lead-sources/{lead_source_id}.
lead_source_id必填List tasks (service types)
Tasks (service types, needed to create a work order). Needs scope tasks:read. GET /open-api/v1/tasks.
sortclasslimitactiveoffsetGet a task with department and skill
One task together with its resolved department and skill. Needs scope tasks:read. GET /open-api/v1/tasks/{task_id}/bundle.
task_id必填List inventory items
Inventory items (parts, services) with cost and rate. Needs scope items:read. GET /open-api/v1/items.
sortlimitactiveoffsetcategoryupdated_afterupdated_beforeGet an inventory item
One inventory item by id. Needs scope items:read. GET /open-api/v1/items/{item_id}.
item_id必填List item categories
Inventory item categories (tree: childTreeLevel, parent). Needs scope item-categories:read. GET /open-api/v1/item-categories.
limitoffsetGet an item category
One item category by id. Needs scope item-categories:read. GET /open-api/v1/item-categories/{item_category_id}.
item_category_id必填List sales tax codes
Sales tax codes. Needs scope items:read. GET /open-api/v1/sales-tax-codes.
sortlimitactiveoffsetis_taxableList warehouses
Inventory warehouses. Needs scope warehouses:read. GET /open-api/v1/warehouses.
namesortlimitactiveoffsetGet a warehouse
One warehouse by id. Needs scope warehouses:read. GET /open-api/v1/warehouses/{warehouse_id}.
warehouse_id必填Get a lead
One lead by id (lead-provider integrations). Needs scope leads:read. GET /open-api/v1/leads/{lead_id}.
lead_id必填Get a company name
The company name for a company id (the tenant id). Needs scope company:read. GET /open-api/v1/companies/{company_id}.
company_id必填Create a customer
WRITE: create a customer record in FieldEdge, visible to the office staff at once. Needs an e-mail or a phone number (international format, e.g. +14155552671); marketing_email_opt_in needs an e-mail and marketing_sms_opt_in a phone number. Names are 2-50 characters without digits. Check fieldedge_search_customers first so you do not create a duplicate. Needs scope customers:write. POST /open-api/v1/customers.
zipcityemailstateaddress_1address_2last_name必填first_name必填company_namephone_numbermarketing_sms_opt_inmarketing_email_opt_in另有 1 个Add a note to a customer
WRITE: add a free-text note to a customer record; office staff see it in FieldEdge at once. Needs scope customers:write. POST /open-api/v1/customers/{customerId}/notes.
note必填customer_id必填Edit a customer note
WRITE: replace the text of an existing customer note (the old text is lost). Get the note id from fieldedge_list_customer_notes. Needs scope customers:write. PATCH /open-api/v1/customers/{customerId}/notes/{noteId}.
note必填note_id必填customer_id必填Create a customer tag
WRITE: create a reusable customer tag (e.g. "VIP Customer"). Check fieldedge_list_tags first. Needs scope customers:write. POST /open-api/v1/tags.
name必填Tag a customer
WRITE: attach an existing tag to a customer; it shows on the customer record in FieldEdge. Needs scope customers:write. POST /open-api/v1/customers/{customerId}/tags.
tag_id必填customer_id必填Remove a tag from a customer
WRITE: detach a tag from a customer (the tag itself stays). Needs scope customers:write. DELETE /open-api/v1/customers/{customerId}/tags/{tagId}.
tag_id必填customer_id必填Create a work order
WRITE: create a work order for a customer location. business_unit_id, lead_source_id and task_id are required: get them from fieldedge_list_business_units, fieldedge_list_lead_sources and fieldedge_list_tasks. Scheduling, invoice lines and equipment are separate steps (fieldedge_assign_technician for scheduling). Needs scope workorders:write. POST /open-api/v1/work-orders.
notestask_id必填customer_id必填document_typelead_source_id必填primary_tech_idbusiness_unit_id必填work_descriptionrequire_equipmentwork_order_numberUpdate a work order
WRITE: partially update a work order; only the fields you pass change. Can reassign the primary technician, change description/notes, and mark it completed (with a resolution) or cancel it (cancel_note). Look at fieldedge_get_work_order first. Needs scope workorders:write. PATCH /open-api/v1/work-orders/{workOrderId}.
notescompletedresolutioncancel_notepriority_idwork_order_id必填lead_source_idprimary_tech_idbusiness_unit_idwork_descriptionAssign a technician to a work order
WRITE: schedule a technician on a work order. The assignment appears on the Dispatch Board at once and FieldEdge returns no assignment id: list the assignments afterwards to find it. Needs scope workorders:write. POST /open-api/v1/work-orders/{workOrderId}/assignments.
technician_id必填work_order_id必填schedule_date_time必填est_complete_date_timeChange a technician assignment's status
WRITE: move an assignment to pending, traveling, working, paused, completed or canceled. It triggers the same customer notifications and dispatch-board updates as a change on the dispatch board and is timestamped now. Canceling needs cancel_note; it fails once the assignment is completed, canceled or finalized. Get the assignment id from fieldedge_list_work_order_assignments. Needs scope workorders:write. PATCH /open-api/v1/work-orders/{workOrderId}/assignments/{assignmentId}/status.
status必填cancel_noteassignment_id必填work_order_id必填Remove a technician from a work order
WRITE: unassign one technician (by assignment id) from a work order; other technicians on it stay. Get the assignment id from fieldedge_list_work_order_assignments. Needs scope workorders:write. DELETE /open-api/v1/work-orders/{workOrderId}/assignments/{assignmentId}.
assignment_id必填work_order_id必填已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
io.usefulapi官方发布者
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
io.usefulapi官方发布者
托管式只读 MCP 服务器，让助手查询 Woffu 公司的用户、劳动合同、部门和办公地点。
io.usefulapi官方发布者
面向 White Label Loyalty 的托管 MCP 服务器：浏览奖励、查看客户积分钱包与等级进度，并用积分购买奖励。
io.usefulapi官方发布者
托管的 Weekdone 连接器，让助手读取周报、团队、目标与 KPI，并新增报告条目、评论和 KPI 数值。
io.usefulapi官方发布者
托管式只读 MCP 服务器，让助手列出 WebinarKit 的网络研讨会、场次时间、系列、会议以及白标子账户。
{ "mcpServers": { "fieldedge": { "url": "https://fieldedge.usefulapi.io/mcp" } }}