FieldEdge MCP server Let your AI agent run the FieldEdge office work.

ToolWhat it doesAccess

• list_customers Customers, searchable by name, phone, email or address. read

  Returns customers with their ID, contact details and service address. Pass the customer_id to get_customer and create_work_order.

  MCP callfieldedge_read → list_customers

  REST endpointGET https://cotlet.dev/api/v1/fieldedge/customers

  Parameters

  Parameters: list_customers

  Name	Type	Description
  query string	string	Name, phone, email or street address.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "customers": [
      {
        "customer_id": "C-20418",
        "name": "Mark Rivera",
        "phone": "555-0182",
        "email": "mark@example.com",
        "service_address": "42 Oak St, Tampa, FL 33602"
      }
    ],
    "page": 1
  }

• get_customer One customer with equipment, agreements and recent work orders. read

  Returns the customer card: contacts, service locations, equipment on file, service agreements and the last work orders with their status.

  MCP callfieldedge_read → get_customer

  REST endpointGET https://cotlet.dev/api/v1/fieldedge/customers/{customer_id}

  Parameters

  Parameters: get_customer

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.

  Example input

  {
    "customer_id": "customer_8c41d2"
  }

  Example response

  {
    "customer_id": "C-20418",
    "name": "Mark Rivera",
    "equipment": [
      {
        "type": "Furnace",
        "model": "Carrier 59SC5",
        "installed": "2019-10-02"
      }
    ],
    "agreement": "Comfort Club, renews 2027-01-15",
    "recent_work_orders": [
      {
        "work_order_id": "WO-88231",
        "status": "Completed",
        "date": "2026-04-11"
      }
    ]
  }

• create_customer Adds a customer with a service address. write

  Creates the customer and its first service location. Search list_customers first so a repeat caller does not become a duplicate. Reaches no one, so it runs at once.

  MCP callfieldedge_write → create_customer

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/customers

  Parameters

  Parameters: create_customer

  Name	Type	Description
  name string required	string	Customer or company name.
  phone string	string	Phone number.
  email string	string	Email.
  service_address string required	string	Street, city, state and ZIP.

  Example input

  {
    "name": "Jane Doe",
    "service_address": "service address"
  }

  Example response

  {
    "customer_id": "C-20502",
    "name": "Priya Nair",
    "service_address": "18 Cedar Ct, Tampa, FL 33606"
  }

ToolWhat it doesAccess

• list_work_orders Work orders by date, status or technician. read

  Returns work orders with customer, task, technician, scheduled window and status. Filter by status such as Unassigned, Dispatched, In Progress or Completed.

  MCP callfieldedge_read → list_work_orders

  REST endpointGET https://cotlet.dev/api/v1/fieldedge/work-orders

  Parameters

  Parameters: list_work_orders

  Name	Type	Description
  date_from string	string	ISO date.
  date_to string	string	ISO date.
  status string	string	unassigned, dispatched, in_progress or completed.
  technician string	string	Technician name.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "work_orders": [
      {
        "work_order_id": "WO-88310",
        "customer": "Mark Rivera",
        "task": "Furnace tune-up",
        "technician": "Luis",
        "window": "2026-11-12 08:00-10:00",
        "status": "Dispatched"
      }
    ],
    "page": 1
  }

• create_work_order Opens a work order for a customer, unassigned or with a window. write

  Creates the work order with the task, description and an optional time window. It stays unassigned until dispatch_technician. Reaches no customer, so it runs at once.

  MCP callfieldedge_write → create_work_order

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/customers/{customer_id}/work-orders

  Parameters

  Parameters: create_work_order

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  task string required	string	Task or job type as named in your FieldEdge account.
  description string	string	What the customer reported.
  window_start string	string	ISO date and time.
  window_end string	string	ISO date and time.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "task": "task"
  }

  Example response

  {
    "work_order_id": "WO-88342",
    "customer": "Priya Nair",
    "task": "No heat diagnostic",
    "status": "Unassigned"
  }

• dispatch_technician Assigns a work order to a technician and a time window. writeasks first

  Puts the work order on the technician's row of the dispatch board. Your FieldEdge notification settings decide whether the customer and technician get a message. By default you confirm each call; you can switch that off for this tool.

  MCP callfieldedge_write → dispatch_technician

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/work-orders/{work_order_id}/technician/dispatch

  Parameters

  Parameters: dispatch_technician

  Name	Type	Description
  work_order_id string required	string	Work order number from list_work_orders.
  technician string required	string	Technician name.
  window_start string required	string	ISO date and time.
  window_end string required	string	ISO date and time.

  Example input

  {
    "work_order_id": "WO-88342",
    "technician": "Carlos",
    "window_start": "2026-11-13T13:00",
    "window_end": "2026-11-13T15:00"
  }

  Example response

  {
    "work_order_id": "WO-88342",
    "technician": "Carlos",
    "window": "2026-11-13 13:00-15:00",
    "status": "Dispatched"
  }

ToolWhat it doesAccess

• list_invoices Invoices by status, date or customer, with balances. read

  Returns invoices with total, balance and status. Use status unpaid and older_than_days to build a collections list.

  MCP callfieldedge_read → list_invoices

  REST endpointGET https://cotlet.dev/api/v1/fieldedge/invoices

  Parameters

  Parameters: list_invoices

  Name	Type	Description
  status string	string	unpaid, paid or all. Default: all.
  older_than_days integer	integer	Only invoices older than this.
  customer_id string	string	One customer only.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "invoices": [
      {
        "invoice_id": "INV-55120",
        "customer": "Mark Rivera",
        "total": "612.00",
        "balance": "612.00",
        "date": "2026-10-02",
        "status": "Unpaid"
      }
    ],
    "page": 1
  }

• create_invoice Builds the invoice for a completed work order. write

  Creates the invoice from the work order's items and labor. It stays a draft you can edit until send_invoice. Reaches no customer, so it runs at once.

  MCP callfieldedge_write → create_invoice

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/work-orders/{work_order_id}/invoices

  Parameters

  Parameters: create_invoice

  Name	Type	Description
  work_order_id string required	string	Work order number from list_work_orders.

  Example input

  {
    "work_order_id": "work_order_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-55210",
    "work_order_id": "WO-88231",
    "total": "389.00",
    "status": "Draft"
  }

• send_invoice Emails an invoice to the customer. writeasks first

  Sends the invoice with your FieldEdge email template to the customer's billing email, or the addresses you pass. By default you confirm each call; you can switch that off for this tool.

  MCP callfieldedge_write → send_invoice

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/invoices/{invoice_id}

  Parameters

  Parameters: send_invoice

  Name	Type	Description
  invoice_id string required	string	Invoice number from list_invoices.
  to string[]	string[]	Recipient emails. Default: the customer's billing email.

  Example input

  {
    "invoice_id": "invoice_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-55210",
    "status": "Sent",
    "sent_to": [
      "mark@example.com"
    ],
    "total": "389.00"
  }

• record_payment Logs a check, cash or other manual payment on an invoice. writeasks first

  Adds the payment and lowers the balance. No card is charged; card payments stay in FieldEdge. By default you confirm each call; you can switch that off for this tool.

  MCP callfieldedge_write → record_payment

  REST endpointPOST https://cotlet.dev/api/v1/fieldedge/invoices/{invoice_id}/payments

  Parameters

  Parameters: record_payment

  Name	Type	Description
  invoice_id string required	string	Invoice number from list_invoices.
  amount string required	string	Amount, e.g. 612.00.
  method string required	string	check, cash or other.
  reference string	string	Check number or note.

  Example input

  {
    "invoice_id": "invoice_8c41d2",
    "amount": "amount",
    "method": "method"
  }

  Example response

  {
    "invoice_id": "INV-55120",
    "payment": {
      "method": "Check",
      "amount": "612.00",
      "reference": "4471"
    },
    "balance": "0.00"
  }