FieldEdge
Look up and create FieldEdge work orders, customers and invoices from Muse.
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.
Try asking Muse: "Add a new customer and a work order for a furnace repair at their address in FieldEdge."
See the most upvoted connectors
Source: Found in the official MCP Registry (io.usefulapi/fieldedge) · First listed November 6, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 4 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://fieldedge.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
FieldEdge is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://fieldedge.usefulapi.io/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 633ms. Worked in 100% of checks over 30 days.
Screening · November 6, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 40
fieldedge_list_work_ordersList 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_orderOne 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_addressWork 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_assignmentsTechnician assignments (schedule, status) on one work order. Needs scope workorders:read. GET /open-api/v1/work-orders/{workOrderId}/assignments.fieldedge_search_customersSearch customers (personal data). With no filter all customers are listed. Needs scope customers:read. GET /open-api/v1/customers/search.fieldedge_get_customerOne 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_phoneThe customer with this phone number (personal data). Needs scope customers:read. GET /open-api/v1/customer/{phone}.fieldedge_search_customers_by_addressCustomers 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_notesNotes on a customer record, newest first by default. Needs scope customers:read. GET /open-api/v1/customers/{customerId}/notes.fieldedge_list_customer_attachmentsFile 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_tagsReusable customer tags of the account. Needs scope customers:read. GET /open-api/v1/tags.fieldedge_list_invoicesInvoices by invoice date, without line items (use fieldedge_get_invoice for those). Needs scope invoices:read. GET /open-api/v1/invoices.fieldedge_get_invoiceOne 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_quotesQuotes, 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_quoteOne 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_agreementsService agreements (recurring maintenance contracts) with plan, dates and customer. Needs scope workorders:read. GET /open-api/v1/agreements.fieldedge_get_agreementOne service agreement by id. Needs scope workorders:read. GET /open-api/v1/agreements/{agreement_id}.fieldedge_list_employeesEmployees (technicians, dispatchers, CSRs, admins). Needs scope employees:read. GET /open-api/v1/employees.fieldedge_get_employeeOne employee record. Needs scope employees:read. GET /open-api/v1/employees/{employee_id}.fieldedge_list_business_unitsBusiness units (needed to create a work order). Needs scope business-units:read. GET /open-api/v1/business-units.fieldedge_get_business_unitOne business unit by id. Needs scope business-units:read. GET /open-api/v1/business-units/{business_unit_id}.fieldedge_list_lead_sourcesLead sources (needed to create a work order). Needs scope lead-sources:read. GET /open-api/v1/lead-sources.fieldedge_get_lead_sourceOne lead source by id. Needs scope lead-sources:read. GET /open-api/v1/lead-sources/{lead_source_id}.fieldedge_list_tasksTasks (service types, needed to create a work order). Needs scope tasks:read. GET /open-api/v1/tasks.fieldedge_get_task_bundleOne task together with its resolved department and skill. Needs scope tasks:read. GET /open-api/v1/tasks/{task_id}/bundle.fieldedge_list_itemsInventory items (parts, services) with cost and rate. Needs scope items:read. GET /open-api/v1/items.fieldedge_get_itemOne inventory item by id. Needs scope items:read. GET /open-api/v1/items/{item_id}.fieldedge_list_item_categoriesInventory item categories (tree: childTreeLevel, parent). Needs scope item-categories:read. GET /open-api/v1/item-categories.fieldedge_get_item_categoryOne item category by id. Needs scope item-categories:read. GET /open-api/v1/item-categories/{item_category_id}.fieldedge_list_sales_tax_codesSales tax codes. Needs scope items:read. GET /open-api/v1/sales-tax-codes.fieldedge_list_warehousesInventory warehouses. Needs scope warehouses:read. GET /open-api/v1/warehouses.fieldedge_get_warehouseOne warehouse by id. Needs scope warehouses:read. GET /open-api/v1/warehouses/{warehouse_id}.fieldedge_get_leadOne lead by id (lead-provider integrations). Needs scope leads:read. GET /open-api/v1/leads/{lead_id}.fieldedge_get_companyThe company name for a company id (the tenant id). Needs scope company:read. GET /open-api/v1/companies/{company_id}.fieldedge_create_customerWRITE: 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 digitsfieldedge_create_customer_noteWRITE: 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_noteWRITE: 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_tagWRITE: 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_tagWRITE: 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_tagWRITE: detach a tag from a customer (the tag itself stays). Needs scope customers:write. DELETE /open-api/v1/customers/{customerId}/tags/{tagId}.Recent checks
Link
https://fieldedge.usefulapi.io/mcpQuestions about FieldEdge in Muse
How do I connect FieldEdge to Muse?
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.
Is FieldEdge working right now?
At the last check (November 6, 2026, 23:16 UTC) the endpoint was working, answering in 633ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
Is FieldEdge safe to connect to Muse?
It was screened on November 6, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can FieldEdge do in Muse?
It exposes 40 tools, including fieldedge_list_work_orders, fieldedge_get_work_order, fieldedge_search_work_orders_by_address, fieldedge_list_work_order_assignments. For example, you could ask Muse: "Add a new customer and a work order for a furnace repair at their address in FieldEdge."
Follow FieldEdge
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/fieldedge)). If you build FieldEdge, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/fieldedge"><img src="https://musedirectory.ai/badge/fieldedge.svg" alt="FieldEdge on musedirectory.ai" width="236" height="40"></a>