FieldEdge MCP by usefulapi

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

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

Read work orders, customers and invoices; create customers, notes and work orders in FieldEdge.

What it does

FieldEdge 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). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 45 tools

Version1.0.1

PriceNot in the registry

First seen06 Nov 2026

Last checked2h ago

How to connect

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

Hosted endpoint

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

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

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

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

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE FieldEdge MCP by usefulapi answered an MCP connection on 06 Nov 2026 and introduced itself as fieldedge-mcp 1.0.1 (MCP protocol 2025-06-18).

45 tools offered to AI assistants

fieldedge_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-a
fieldedge_get_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}.
fieldedge_search_work_orders_by_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.
fieldedge_list_work_order_assignments · Technician assignments (schedule, status) on one work order. Needs scope workorders:read. GET /open-api/v1/work-orders/{workOrderId}/assignments.
fieldedge_search_customers · Search customers (personal data). With no filter all customers are listed. Needs scope customers:read. GET /open-api/v1/customers/search.
fieldedge_get_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}.
fieldedge_get_customer_by_phone · The customer with this phone number (personal data). Needs scope customers:read. GET /open-api/v1/customer/{phone}.
fieldedge_search_customers_by_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.
fieldedge_list_customer_notes · Notes on a customer record, newest first by default. Needs scope customers:read. GET /open-api/v1/customers/{customerId}/notes.
fieldedge_list_customer_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.
fieldedge_list_tags · Reusable customer tags of the account. Needs scope customers:read. GET /open-api/v1/tags.
fieldedge_list_invoices · Invoices by invoice date, without line items (use fieldedge_get_invoice for those). Needs scope invoices:read. GET /open-api/v1/invoices.

Show 33 more

fieldedge_get_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}.
fieldedge_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.
fieldedge_get_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}.
fieldedge_list_agreements · Service agreements (recurring maintenance contracts) with plan, dates and customer. Needs scope workorders:read. GET /open-api/v1/agreements.
fieldedge_get_agreement · One service agreement by id. Needs scope workorders:read. GET /open-api/v1/agreements/{agreement_id}.
fieldedge_list_employees · Employees (technicians, dispatchers, CSRs, admins). Needs scope employees:read. GET /open-api/v1/employees.
fieldedge_get_employee · One employee record. Needs scope employees:read. GET /open-api/v1/employees/{employee_id}.
fieldedge_list_business_units · Business units (needed to create a work order). Needs scope business-units:read. GET /open-api/v1/business-units.
fieldedge_get_business_unit · One business unit by id. Needs scope business-units:read. GET /open-api/v1/business-units/{business_unit_id}.
fieldedge_list_lead_sources · Lead sources (needed to create a work order). Needs scope lead-sources:read. GET /open-api/v1/lead-sources.
fieldedge_get_lead_source · One lead source by id. Needs scope lead-sources:read. GET /open-api/v1/lead-sources/{lead_source_id}.
fieldedge_list_tasks · Tasks (service types, needed to create a work order). Needs scope tasks:read. GET /open-api/v1/tasks.
fieldedge_get_task_bundle · One task together with its resolved department and skill. Needs scope tasks:read. GET /open-api/v1/tasks/{task_id}/bundle.
fieldedge_list_items · Inventory items (parts, services) with cost and rate. Needs scope items:read. GET /open-api/v1/items.
fieldedge_get_item · One inventory item by id. Needs scope items:read. GET /open-api/v1/items/{item_id}.
fieldedge_list_item_categories · Inventory item categories (tree: childTreeLevel, parent). Needs scope item-categories:read. GET /open-api/v1/item-categories.
fieldedge_get_item_category · One item category by id. Needs scope item-categories:read. GET /open-api/v1/item-categories/{item_category_id}.
fieldedge_list_sales_tax_codes · Sales tax codes. Needs scope items:read. GET /open-api/v1/sales-tax-codes.
fieldedge_list_warehouses · Inventory warehouses. Needs scope warehouses:read. GET /open-api/v1/warehouses.
fieldedge_get_warehouse · One warehouse by id. Needs scope warehouses:read. GET /open-api/v1/warehouses/{warehouse_id}.
fieldedge_get_lead · One lead by id (lead-provider integrations). Needs scope leads:read. GET /open-api/v1/leads/{lead_id}.
fieldedge_get_company · The company name for a company id (the tenant id). Needs scope company:read. GET /open-api/v1/companies/{company_id}.
fieldedge_create_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.
fieldedge_create_customer_note · 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.
fieldedge_update_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}.
fieldedge_create_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.
fieldedge_add_customer_tag · 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.
fieldedge_remove_customer_tag · WRITE: detach a tag from a customer (the tag itself stays). Needs scope customers:write. DELETE /open-api/v1/customers/{customerId}/tags/{tagId}.
fieldedge_create_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
fieldedge_update_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 fir
fieldedge_assign_technician · 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-orde
fieldedge_update_assignment_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
fieldedge_remove_assignment · 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}

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
Artil — Email, SMS & Messaging for AI AgentsREMOTELOCAL
Give AI agents own email inbox, SMS numbers, and workspace accounts to receive and send messages
QuoAPIREMOTELOCAL
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing
getpepprREMOTELOCAL
Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices
KvickdREMOTELOCAL
Bookkeeping for Swedish small businesses: AB, enskild firma, handelsbolag. Invoices, VAT, payroll
XSDHub XML validationREMOTELOCAL
Validate XML, XSD and e-invoices with XSDHub. Includes error explanations and source URLs

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 · Prices & score →
Xelix32
On quote · Prices & score →
Apollo.io90
$49/mo · free plan · Prices & score →
Digits86
$65/mo · Prices & score →

All AI agents to send and chase invoices, ranked →

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://fieldedge.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/fieldedge/	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

NEW06 Nov 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 FieldEdge MCP by usefulapi still online?

Free alerts · no account▲ 0

Do you run FieldEdge MCP by usefulapi? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor FieldEdge MCP by usefulapiLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about FieldEdge MCP by usefulapi

How do I connect FieldEdge MCP by usefulapi?

Use the hosted endpoint https://fieldedge.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 FieldEdge MCP by usefulapi offer?

When Electra Index connected on 06 Nov 2026, it listed 45 tools: fieldedge_list_work_orders, fieldedge_get_work_order, fieldedge_search_work_orders_by_address, fieldedge_list_work_order_assignments, fieldedge_search_customers, fieldedge_get_customer, fieldedge_get_customer_by_phone, fieldedge_search_customers_by_address and more. The full list is in "Live check" above.

Is FieldEdge MCP by usefulapi online?

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

What can I use FieldEdge MCP by usefulapi for?

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