# FieldEdge Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## FieldEdge

Look up and create FieldEdge work orders, customers and invoices from Muse.

- Record: https://musedirectory.ai/connector/fieldedge
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/fieldedge/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 633ms, checked 2026-11-06T23:16:03Z
- Endpoint: https://fieldedge.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-06T20:36:14Z)
- Source: Found in the official MCP Registry (io.usefulapi/fieldedge) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ffieldedge

Connects Muse to a FieldEdge field service account. Muse can read work orders, customer records and invoices, and create new customers, notes and work orders, so a contractor can check the day's jobs or add a customer without opening the FieldEdge app.

Example request: "Add a new customer and a work order for a furnace repair at their address in FieldEdge."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use FieldEdge to help me. It is a free service with an MCP server at https://fieldedge.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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-api/v1/work-orders.
- 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.
- 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. Names are 2-50 characters without digits
- 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}.

Screening checks:
- MCP handshake: pass (Answered in 74ms)
- Domain against threat feeds (Cloudflare security DNS): pass (fieldedge.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: n/a (Tools are behind sign-in)
- Inputs asking for passwords, card numbers or seed phrases: n/a (Tools are behind sign-in)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)