# FieldEdge MCP connector

The FieldEdge connector brings customers, service agreements, invoices, notes and technicians into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can look up and update FieldEdge records as the person who signed in.

Source: https://elaichi.ai/connectors/fieldedge/

## Facts

| | |
| --- | --- |
| Application | FieldEdge |
| Category | CRM |
| AI tools | 59 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once FieldEdge is connected

- Find the customer at 42 Elm Street and show their open invoices.
- Which customers have no active service agreement?
- Add a note to the Patel account about the leaking valve.

## Connect FieldEdge in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick FieldEdge.
2. Optionally set Share with, then press Connect.
3. Paste your FieldEdge app credentials. FieldEdge authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which FieldEdge tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## FieldEdge MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## FieldEdge MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## FieldEdge MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## FieldEdge MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## FieldEdge MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect FieldEdge to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a FieldEdge tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with FieldEdge through Elaichi

### Pull up the caller before they finish

Office. When the phone rings, find the FieldEdge customer by phone number or address and see their notes, agreements and open invoices in one answer.

### Log what the technician found on site

Service. After a visit, add a customer note describing the fault and attach the photo, so the next technician reads it before they arrive.

### Fix an invoice before it goes out

Billing. List the invoices from this week, spot the one with the wrong line, and update it without opening FieldEdge.

### Find customers without a service agreement

Sales. Compare the customer list against agreements, then tag the ones with no plan so the renewal call list builds itself.

### See who sits in each business unit

Management. List business units and the employees in them, so you can answer who covers plumbing in the north branch without asking around.

### Set up a new customer in seconds

Customer service. Create the customer record from the details in an email, tag them with the right campaign, and add the first note.

## Elaichi vs Zapier MCP vs Composio for FieldEdge

All three can connect FieldEdge to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over FieldEdge tools | Allow or restrict single FieldEdge tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per FieldEdge call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect FieldEdge to Claude?

Connect FieldEdge in Elaichi by pasting the app credentials from your FieldEdge account, there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and FieldEdge is available in Claude.

### Does FieldEdge work with ChatGPT and Cursor as well as Claude?

Yes. Once FieldEdge is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect FieldEdge once and every client sees it.

### What can an AI agent actually do with my FieldEdge data?

It can find a FieldEdge customer by name, phone number or address, read their notes and agreements, and check their invoices. It can create a customer, add a note or attachment, tag a customer, update an invoice, and list employees and business units. Short, concrete asks such as "show open invoices for the Patel account" work better than long sentences.

### Does connecting FieldEdge give the AI everything in my account?

No. Every call into FieldEdge runs as the person who signed in, so the agent sees only the customers, invoices and agreements that person can already see in FieldEdge. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one FieldEdge connection?

Yes. One person connects FieldEdge in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names who looked up a customer or changed an invoice.

### Can I stop an agent from deleting or changing things in FieldEdge?

Yes. Restrictions in Elaichi work per action, so you can allow reading FieldEdge customers while restricting updating invoices or deleting tags, set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a FieldEdge connection when someone leaves?

Offboarding that person in Elaichi ends their access to FieldEdge at once, from every client. A FieldEdge connection they shared keeps working for everyone else on the team. If you want FieldEdge gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the FieldEdge MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. FieldEdge is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for FieldEdge?

Yes. Both let Claude, ChatGPT or Cursor use FieldEdge. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every FieldEdge call.

### How is Elaichi different from Composio for FieldEdge?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to FieldEdge: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 59 FieldEdge tools

Every tool below is callable through https://api.elaichi.ai/mcp once FieldEdge is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single FieldEdge agreement by ID** (Get). Retrieve agreement by id. Get a single agreement by id. Scope: workorders:read. Required: id.
- **List all FieldEdge agreements** (List). Retrieve list of agreements. Get a paginated list of agreements with optional filters. Scope: workorders:read. The connector pages by offset; limit = page size (max 200); records at data.
- **Get single FieldEdge business unit by ID** (Get). Retrieve business unit by id. Get a single business unit by its ID. Scope: business-units:read. Required: id.
- **List all FieldEdge business units** (List). Retrieve list of business units. Get list of business units with filters, pagination, and sort. Scope: business-units:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Get single FieldEdge company by ID** (Get). Retrieve company name by ID. Returns the company name for the given company ID. Scope: company:read. Required: id.
- **Create a FieldEdge customer attachment** (Create). Upload a file attachment to a customer record. Uploads a file and associates it with the specified customer record. The file is stored in Azure Blob Storage and the attachment is immediately visible within the FieldEdge customer record. Scope: customers:write. Required: customer_id, file, fileName.
- **List all FieldEdge customer attachments** (List). Retrieve attachments for a customer. Returns a paginated list of file attachments associated with the specified customer record. Each item includes the blob URL required to download or view the file. Supports offset and limit for pagination and a sort parameter to control ordering. Default sort is createdAt descending (newest first). Scope: customers:read. Required: customer_id. The connector pages by offset; limit = page size (max 200); records at data.
- **Create a FieldEdge customer note** (Create). Create a note on a customer record. Creates a free-text note attached to the specified customer. The note is immediately visible to office staff within the FieldEdge customer record. Scope: customers:write. Required: customer_id, note.
- **List all FieldEdge customer notes** (List). Retrieve all notes for a customer. Returns a paginated list of notes attached to the specified customer record. Supports offset and limit for pagination and a sort parameter to control ordering. Default sort is createdAt descending (newest first). Scope: customers:read. Required: customer_id. The connector pages by offset; limit = page size (max 100); records at notes.
- **Update a FieldEdge customer note by ID** (Update). Update an existing customer note. Updates the text content of an existing note on a customer record. The updated note is immediately visible in the FieldEdge customer record. Only the note field can be modified. Scope: customers:write. Required: id, customer_id.
- **Create a FieldEdge customer tag** (Create). Associate a tag with a customer. Associates an existing tag with the specified customer record. The tag becomes visible on the FieldEdge customer record. Scope: customers:write. Required: customer_id, tagId.
- **Delete a FieldEdge customer tag by ID** (Delete). Remove a tag from a customer. Removes the association between a tag and a customer. The tag itself remains available via GET /v1/tags. Scope: customers:write. Required: id, customer_id.
- **Create a FieldEdge customer** (Create). Creates a new customer. Creates a new customer record with primary contact details, address information, preferred contact methods, and marketing opt-in preferences. Scope: customers:write.
- **Get single FieldEdge customer by ID** (Get). Retrieve customer details by ID. Retrieves details for a customer or job using its unique identifier. The response indicates whether the record is a job or a billing customer. Scope: customers:read. Required: id.
- **List all FieldEdge customers** (List). Search customers with optional filters. Retrieves customers matching the provided search criteria. All filters are optional — supply any combination of phone, email, firstName, updatedAfter/updatedBefore, or hasServiceAgreement to narrow results. When no filters are provided, all customers are returned. Scope: customers:read. The connector pages by offset; limit = page size (max 100); records at customers.
- **Update a FieldEdge customer by ID** (Update). Updates an existing customer. Updates an existing customer using the customerId provided in the URL. Allows modification of name, company, primary contact details (email/phone), address information, preferred contact methods (Email, Phone, SMS), and marketing opt-in preferences. Scope: customers:write. Required: id.
- **List all FieldEdge customers by address** (List). Retrieve customers based on address details. Search and retrieve customers by address information. Supports pagination via query parameters offset (default 0) and limit (default 20). Scope: customers:read. Required: addressLine1, city, stateOrRegion, postalCode. The connector pages by offset; limit = page size (max 100); records at customers.
- **Get single FieldEdge customers by phone by ID** (Get). Retrieve customer by phone number. Retrieves a customer record matching the provided phone number. Scope: customers:read. Required: id.
- **Get single FieldEdge employee by ID** (Get). Retrieve an employee by ID. Retrieves a single employee record. Scope: employees:read. Required: id.
- **List all FieldEdge employees** (List). Retrieve a paginated list of employees. Retrieves a paginated list of employees. Supports filtering by active status and sorting. Scope: employees:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Get single FieldEdge invoice by ID** (Get). Retrieve an invoice by ID. Retrieves the invoice associated with a FieldEdge work order. The invoice ID is the same as the work order ID. Returns 404 if no work order is found or if the work order has no invoice. Scope: invoices:read. Required: id.
- **List all FieldEdge invoices** (List). Retrieve a paginated list of invoices. Returns a paginated list of invoices for the authenticated partner account, sorted by invoice date. Line-item details are not included; use GET /v1/invoices/{invoiceId} to retrieve full invoice detail. Scope: invoices:read. The connector pages by offset; limit = page size (max 200); records at data.
- **Update a FieldEdge invoice by ID** (Update). Create or update the invoice on a work order. Creates or updates the invoice on a work order and recalculates totals from the submitted items. Send the complete item list each time — this replaces all items, not just the ones that changed. Scope: invoices:write. Required: id, items.
- **Create a FieldEdge item category** (Create). Create a new item category. Creates a new item category. Optionally nest it under a parent category by providing a non-empty parentId. ChildTreeLevel and FullName are computed server-side. Scope: item-categories:write. Required: active.
- **Get single FieldEdge item category by ID** (Get). Retrieve item category by id. Get single item category by id. Scope: item-categories:read. Required: id.
- **List all FieldEdge item categories** (List). Retrieve list of item categories. Get list of itemCategories with filters and sort parameter. Scope: item-categories:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Update a FieldEdge item category by ID** (Update). Partially update an item category. Applies a partial update to an item category by its ID. Only the fields included in the request body are updated; omitted fields retain their existing values. ChildTreeLevel, FullName, and QboID are computed/managed server-side. Scope: item-categories:write. Required: id.
- **FieldEdge items bulk update** (Update). Bulk update inventory items. Updates up to 50 inventory items in a single request. Items are fetched, patched in memory, and written to FieldEdge in a single batch call. Partial success is possible — the response always returns 207 Multi-Status with a per-item result for every submitted item. Scope: items:write. One call for up to 50 items, not a record update: the connector names a PATCH without a trailing id bulk_update. Answers 207 with a result per item; a call where every item failed comes back as an error.
- **Create a FieldEdge item** (Create). Creates a new inventory item. Creates a new inventory item with name, cost, rate, optional category, image, and tax information. Scope: items:write.
- **Get single FieldEdge item by ID** (Get). Retrieve an inventory item by ID. Retrieves a single inventory item using its unique identifier. Scope: items:read. Required: id.
- **List all FieldEdge items** (List). Retrieve a paginated list of inventory items with optional filters. Retrieves a paginated list of items. Supports filtering by category, active status, and sorting. Scope: items:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Update a FieldEdge item by ID** (Update). Updates an existing inventory item. Updates an inventory item by itemId. Only mutable fields such as name, description, cost, rate, category, image, and tax information can be updated. Scope: items:write. Required: id.
- **Get single FieldEdge lead source by ID** (Get). Retrieve lead source by id. Get a single lead source by its ID. Scope: lead-sources:read. Required: id.
- **List all FieldEdge lead sources** (List). Retrieve list of lead sources. Get list of lead sources with filters, pagination, and sort. Scope: lead-sources:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Create a FieldEdge lead** (Create). Creates a new lead with customer details, appointment preferences, and service information. Creates a new lead record in the system. Customer resolution (priority order): 1. customer.existingCustomerId provided → system looks up the customer by FieldEdge ID and uses their stored details; all other customer fields are ignored. 2. Scope: leads:write. Required: source, customer, isExistingCustomer, appointment, serviceRequest.
- **Get single FieldEdge lead by ID** (Get). Fetches lead details based on the provided lead identifier. Retrieves the details of a lead by its unique identifier. Scope: leads:read. Required: id.
- **Get single FieldEdge quote by ID** (Get). Retrieve a quote by ID. Retrieves the quote associated with a FieldEdge work order. The quote ID is the same as the work order ID. Returns 404 if no work order is found or if the work order has no quote. Scope: workorders:read. Required: id.
- **List all FieldEdge quotes** (List). Retrieve a paginated list of quotes. Returns a paginated list of quotes for the authenticated partner account. Available filters are id, customerId, className, and classId; customerId reflects the underlying work order's customer/location and may differ from the quote's billing entity. Scope: workorders:read. The connector pages by offset; limit = page size (max 200); records at data.
- **List all FieldEdge sales tax codes** (List). Retrieve list of sales tax codes. Get a paginated list of sales tax codes with sort support. Scope: items:read. The connector pages by offset; limit = page size (max 200); records at data.
- **Create a FieldEdge tag** (Create). Create a reusable customer tag. Creates a reusable tag that can later be associated with customer records (e.g. "VIP Customer"). Scope: customers:write. Required: name.
- **List all FieldEdge tags** (List). Retrieve tags. Returns a paginated list of customer tags for the account. Supports offset/limit pagination, an optional name filter, and a sort parameter (default name ascending). Scope: customers:read. The connector pages by offset; limit = page size (max 200); records at data.
- **Get single FieldEdge task bundle by ID** (Get). Retrieve a task bundle by ID. Returns the task record together with its resolved department and skill. Scope: tasks:read. Required: id.
- **List all FieldEdge tasks** (List). Retrieve a list of tasks. Returns a list of tasks. Scope: tasks:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Create a FieldEdge warehouse** (Create). Create a new warehouse. Creates a new warehouse with the provided details. Scope: warehouses:write. Required: name.
- **Get single FieldEdge warehouse by ID** (Get). Retrieve a warehouse by ID. Retrieves a single warehouse using its unique identifier. Scope: warehouses:read. Required: id.
- **List all FieldEdge warehouses** (List). Retrieve a paginated list of warehouses. Retrieves a paginated list of warehouses. Supports filtering by name, active status, and sorting. Scope: warehouses:read. The connector pages by offset; limit = page size (max 100); records at data.
- **Update a FieldEdge warehouse by ID** (Update). Update an existing warehouse. Updates the specified warehouse with the provided details. Only the supplied fields will be updated. Scope: warehouses:write. Required: id.
- **FieldEdge webhooks bulk delete** (Delete). Delete the registered webhook for the authenticated account. Removes the webhook registration for the authenticated account. Subsequent events will no longer be delivered to the callback URL. Scope: webhooks:delete. The account has one webhook registration: this deletes it (no id).
- **Create a FieldEdge webhook** (Create). Register a webhook endpoint to receive event notifications. Registers a callback URL that will receive real-time event notifications for work orders, invoices, item categories, customers, quotes, and leads. Once registered, FieldEdge will POST a JSON payload to your callback URL whenever a supported event occurs. Scope: webhooks:write. Required: callbackUrl.
- **FieldEdge webhooks rotate secret** (Rotate). Rotate the HMAC signing secret for the registered webhook. Generates a new HMAC-SHA256 secret for the authenticated account's webhook. The new secret replaces the previous one immediately. Store the returned secret securely — it cannot be retrieved again. Scope: webhooks:write.
- ...and 9 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
