# FieldRoutes MCP connector

The FieldRoutes connector brings appointments, customer contacts, reminders and applied payments into Claude, ChatGPT, Cursor and Microsoft Copilot through one Elaichi endpoint, where every person works inside their own FieldRoutes access.

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

## Facts

| | |
| --- | --- |
| Application | FieldRoutes |
| Category | CRM |
| AI tools | 237 |
| Authentication | Connects with an API key |
| 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 FieldRoutes is connected

- List tomorrow's appointments for the north branch
- Reschedule the Harper account's Thursday appointment to Friday morning
- Which cancellation reasons came up most this month

## Connect FieldRoutes in Elaichi

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

1. Open Connections, choose Add connection, and pick FieldRoutes.
2. Optionally set Share with, then press Connect.
3. Paste a FieldRoutes API key. One person generates a token in FieldRoutes and pastes it once. Everyone else works through Share with, and never sees it.

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

## FieldRoutes 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.

## FieldRoutes 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`.

## FieldRoutes 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.

## FieldRoutes 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.

## FieldRoutes 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 FieldRoutes 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 FieldRoutes 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 FieldRoutes through Elaichi

### Move an appointment while the customer waits

Office. Ask for a customer's upcoming FieldRoutes appointments, shift one to a new slot and record the reschedule reason, all without leaving the call to open the scheduler.

### See what is booked before trucks roll

Dispatch. List today's appointments by branch or technician and spot gaps, overlaps or a stop that should have been canceled before the first truck leaves the yard.

### Keep every contact on the account current

Customer service. After a call, add the property manager as an additional contact or update a phone number so the next technician reaches the right person at the gate.

### Confirm a payment landed on the account

Billing. Pull the applied payments for a customer and see what was paid and when before you send a reminder about an open balance.

### Find out why appointments keep getting canceled

Operations. Review cancellation and reschedule reasons across the month to see which ones come up most and fix the cause behind them.

### Close out completed jobs the same day

Management. Mark appointments complete once technicians report in and set a reminder for the follow-up visit so nothing slips to next week.

## Elaichi vs Zapier MCP vs Composio for FieldRoutes

All three can connect FieldRoutes 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 FieldRoutes tools | Allow or restrict single FieldRoutes 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 FieldRoutes 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 FieldRoutes to Claude?

In Elaichi, choose FieldRoutes and paste the API key from your FieldRoutes account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi login and your FieldRoutes appointments, contacts and payments are available in the conversation.

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

Yes. FieldRoutes is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot or any other MCP client. The Elaichi Agent uses it too, so there is nothing to set up a second time.

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

It can list FieldRoutes appointments for a day, a branch or a customer, book a new one, reschedule, cancel or mark one complete, and set appointment reminders. It can look up and update additional contacts on an account, check applied payments, and pull the cancellation and reschedule reasons behind a month of changes. Short, concrete asks like "tomorrow's appointments for the north branch" work better than long paragraphs.

### Does connecting FieldRoutes give the AI access to every customer and branch?

No. Each person signs in to Elaichi as themselves, so an agent only sees the FieldRoutes appointments, contacts and payments that person could already see. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what FieldRoutes already allows.

### Can my team share one FieldRoutes connection?

Yes. One person connects FieldRoutes with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the actual person who rescheduled an appointment or added a contact.

### Can I stop an agent from canceling or changing things in FieldRoutes?

Yes. Restrictions in Elaichi work per action, so you can restrict canceling, rescheduling or completing FieldRoutes appointments for a role or for one person while leaving lookups open. 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 FieldRoutes connection when someone leaves?

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

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

Yes. FieldRoutes 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 FieldRoutes?

Yes. Both let Claude, ChatGPT or Cursor use FieldRoutes. 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 FieldRoutes call.

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

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 FieldRoutes: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 237 FieldRoutes tools

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

- **Get single FieldRoutes access control by ID** (Get). Get one Access Controls record by id (/api/accessControl/get, sent as employeeID). Retrieves a single access control record by employee ID. Required: id.
- **List all FieldRoutes access controls** (List). Search Access Controls (/api/accessControl/search): returns the full records. Returns a list of employee IDs (and optionally full access control records) matching the supplied filters. All filters are combined with AND logic. The connector sends includeData=1 and pages by employeeIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then employeeIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Create a FieldRoutes additional contact** (Create). Create a Additional Contacts record (/api/additionalContact/create). Creates a new additional contact record associated with a customer. The customer must belong to the office(s) authorized by your API credentials. Returns the newly created additionalContactID. Required: customerID, additionalContactTypeID.
- **Get single FieldRoutes additional contact by ID** (Get). Get one Additional Contacts record by id (/api/additionalContact/get, sent as additionalContactID). Retrieves a single additional contact record by its primary key. The contact must belong to a customer within the authenticated office(s). Required: id.
- **List all FieldRoutes additional contacts** (List). Search Additional Contacts (/api/additionalContact/search): returns the full records. Returns a list of additional contact IDs (and optionally full records) that match the supplied filters. All filters are combined with AND logic. Results are ordered by additionalContactID ASC and limited to 50,000 rows. The connector sends includeData=1 and pages by additionalContactIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then additionalContactIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Update a FieldRoutes additional contact by ID** (Update). Update a Additional Contacts record (/api/additionalContact/update, id sent as additionalContactID). Updates an existing additional contact record. Only the fields supplied are modified; omitted fields are left unchanged. Returns the updated additionalContactID. Required: id.
- **Get single FieldRoutes application method by ID** (Get). Get one Application Methods record by id (/api/applicationMethod/get, sent as applicationMethodID). Retrieves a single application method record by ID. Required: id.
- **List all FieldRoutes application methods** (List). Search Application Methods (/api/applicationMethod/search): returns the full records. Returns a list of application method IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. The connector sends includeData=1 and pages by applicationMethodIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then applicationMethodIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes applied payment by ID** (Get). Get one Applied Payments record by id (/api/appliedPayment/get, sent as appliedPaymentID). Retrieves a single applied payment record by ID. Required: id.
- **List all FieldRoutes applied payments** (List). Search Applied Payments (/api/appliedPayment/search): returns the full records. Returns a list of applied payment IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. The connector sends includeData=1 and pages by appliedPaymentIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then appliedPaymentIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes appointment cancellation reason by ID** (Get). Get one Appointment Cancellation Reasons record by id (/api/appointmentCancellationReason/get, sent as cancellationReasonID). Retrieves a single appointment cancellation reason record by ID. Required: id.
- **List all FieldRoutes appointment cancellation reasons** (List). Search Appointment Cancellation Reasons (/api/appointmentCancellationReason/search): returns the full records. Returns a list of cancellation reason IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. The connector sends includeData=1 and pages by cancellationReasonIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then cancellationReasonIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Create a FieldRoutes appointment reminder** (Create). Create a Appointment Reminders record (/api/appointmentReminder/create). Creates a new appointment reminder record. The officeID is automatically set from the authenticated session. If the appointment referenced by appointmentID does not belong to the authenticated office, the request is rejected. Required: appointmentID, text, dateSent, emailSent, status.
- **Get single FieldRoutes appointment reminder by ID** (Get). Get one Appointment Reminders record by id (/api/appointmentReminder/get, sent as reminderIDs). Retrieves one or more reminder records by ID. Returns full record data for each requested reminder that belongs to the authenticated office(s). Required: id.
- **List all FieldRoutes appointment reminders** (List). Search Appointment Reminders (/api/appointmentReminder/search): returns the full records. Returns a list of reminder IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. Results are ordered by reminderID ASC and limited to 50,000 IDs. The connector sends includeData=1 and pages by reminderIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then reminderIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Update a FieldRoutes appointment reminder by ID** (Update). Update a Appointment Reminders record (/api/appointmentReminder/update, id sent as reminderID). Modifies an existing appointment reminder. Pass the reminderID along with only the fields you wish to change. All parameters (except reminderID) are optional for updates. Required: id.
- **Get single FieldRoutes appointment reschedule reason by ID** (Get). Get one Appointment Reschedule Reasons record by id (/api/appointmentRescheduleReason/get, sent as rescheduleReasonID). Retrieves a single appointment reschedule reason record by ID. Required: id.
- **List all FieldRoutes appointment reschedule reasons** (List). Search Appointment Reschedule Reasons (/api/appointmentRescheduleReason/search): returns the full records. Returns a list of reschedule reason IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. The connector sends includeData=1 and pages by rescheduleReasonIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then rescheduleReasonIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **FieldRoutes appointments cancel** (Cancel). Appointments: 8. Cancel (/api/appointment/cancel). Cancels an existing appointment. This is the preferred way to cancel (rather than setting status=-1 on /update) because it allows you to supply a cancellation reason and a specific employee. Required: appointmentID.
- **FieldRoutes appointments complete** (Complete). Appointments: 9. Complete (/api/appointment/complete). Completes an appointment with full service details, including technician notes, chemical usage, weather conditions, GPS coordinates, and signatures. This endpoint mirrors the mobile completion workflow and triggers all associated business logic (invoicing, subscription next-service-date updates, etc.). Required: appointmentID.
- **Create a FieldRoutes appointment** (Create). Create a Appointments record (/api/appointment/create). Creates a new appointment for a customer. The appointment is placed on a route based on the spotID (preferred) or routeID provided. Default values for duration, time window, and other properties are derived from the service type and subscription configuration when not explicitly supplied. Required: customerID, type.
- **Get single FieldRoutes appointment by ID** (Get). Get one Appointments record by id (/api/appointment/get, sent as appointmentIDs). Retrieves full appointment records by their IDs. Results are limited to 1,000 records per request. Required: id.
- **FieldRoutes appointments reschedule** (Action). Appointments: 10. Reschedule (/api/appointment/reschedule). Reschedules an existing appointment to a new spot or time. Internally this creates a new appointment and marks the original as rescheduled (status = -2), preserving an audit link via the new appointment's originalAppointmentID. Use this in preference to /update when moving an appointment, because it carries forward the reschedule reason and keeps the original record intact for... Required: appointmentID, spotID.
- **List all FieldRoutes appointments** (List). Search Appointments (/api/appointment/search): returns the full records. Returns a list of appointment IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. By default, only appointments with status 0 (Pending) or 1 (Completed) are returned unless you explicitly pass the status filter. The connector sends includeData=1 and pages by appointmentIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then appointmentIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Update a FieldRoutes appointment by ID** (Update). Update a Appointments record (/api/appointment/update, id sent as appointmentID). Modifies an existing appointment. All parameters from /create are accepted but are optional — only the fields you send will be updated (piecewise update). Additionally, you can update completion data and change the appointment status. Required: id.
- **Create a FieldRoutes bundle subscription** (Create). Create a Bundle Subscriptions record (/api/bundleSubscription/create). Creates a new bundle subscription linking a subscription to a bundle template. Returns the newly created bundleSubscriptionID. Required: subscriptionID, serviceBundleTemplateID.
- **Delete a FieldRoutes bundle subscription by ID** (Delete). Delete a Bundle Subscriptions record (/api/bundleSubscription/delete, id sent as bundleSubscriptionID). Permanently removes a bundle subscription record. The deletion is performed by looking up the underlying subscriptionID and removing the bundle link row. The other fields go in the query; the connector sends them in the JSON body. Required: id.
- **Get single FieldRoutes bundle subscription by ID** (Get). Get one Bundle Subscriptions record by id (/api/bundleSubscription/get, sent as bundleSubscriptionIDs). Retrieves full bundle subscription records for the given IDs. Returns the fields described in Data Model. Results are limited to 1,000 records per request and ordered by bundleSubscriptionID ASC. Required: id.
- **List all FieldRoutes bundle subscriptions** (List). Search Bundle Subscriptions (/api/bundleSubscription/search): returns the full records. Returns a list of bundle subscription IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. Results are ordered by bundleSubscriptionID ASC and limited to 50,000 IDs per request. The connector sends includeData=1 and pages by bundleSubscriptionIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then bundleSubscriptionIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Update a FieldRoutes bundle subscription by ID** (Update). Update a Bundle Subscriptions record (/api/bundleSubscription/update, id sent as bundleSubscriptionID). Modifies an existing bundle subscription. Pass only the fields you wish to change along with the required bundleSubscriptionID. Fields not included in the request are left unchanged. Required: id.
- **Get single FieldRoutes cancellation reason by ID** (Get). Get one Cancellation Reasons record by id (/api/cancellationReason/get, sent as reasonIDs). Retrieves one or more cancellation reason records by their IDs. This endpoint is used to fetch full record data for specific reason IDs, typically those obtained from a prior /search call. Required: id.
- **List all FieldRoutes cancellation reasons** (List). Search Cancellation Reasons (/api/cancellationReason/search): returns the full records. Returns a list of cancellation reason IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. Results are ordered by reasonID ASC with a maximum of 50,000 IDs returned. The connector sends includeData=1 and pages by reasonIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then reasonIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes changelog by ID** (Get). Get one Changelogs record by id (/api/changelog/get, sent as changeIDs). Retrieves one or more changelog records by their IDs. Limited to 1,000 records per request. Required: id.
- **List all FieldRoutes changelogs** (List). Search Changelogs (/api/changelog/search): returns the full records. Returns a list of changelog IDs (and optionally full records) that match the supplied filters. All filters are combined with AND logic. The search is limited to 50,000 IDs. The connector sends includeData=1 and pages by changeIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then changeIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes chargeback by ID** (Get). Get one Chargebacks record by id (/api/chargeback/get, sent as gatewayChargebackIDs). Retrieves one or more chargeback records by their IDs. Limited to 1,000 records per request. Required: id.
- **List all FieldRoutes chargebacks** (List). Search Chargebacks (/api/chargeback/search): returns the full records. Returns a list of chargeback IDs (and optionally full records) that match the supplied filters. All filters are combined with AND logic. The search is limited to 50,000 IDs. The connector sends includeData=1 and pages by gatewayChargebackIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then gatewayChargebackIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes chemical US by ID** (Get). Get one Chemical Uses record by id (/api/chemicalUse/get, sent as chemicalUseIDs). Retrieves one or more full chemical use records by their IDs. Returns up to 1,000 records per request. The response shape matches the data block in the /search response when includeData=1. Required: id.
- **List all FieldRoutes chemical uses** (List). Search Chemical Uses (/api/chemicalUse/search): returns the full records. Returns a list of chemical use IDs (and optionally full records) that match the supplied filters. All filters are combined with AND logic. Results are ordered by chemicalUseID ASC and capped at 50,000 IDs. The connector sends includeData=1 and pages by chemicalUseIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then chemicalUseIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes chemical by ID** (Get). Get one Chemicals record by id (/api/chemical/get, sent as chemicalIDs). Retrieves one or more chemical records by their IDs. Returns full record data including the nested targetIssues array and activeIngredients array for each chemical. Required: id.
- **List all FieldRoutes chemicals** (List). Search Chemicals (/api/chemical/search): returns the full records. Returns a list of chemical IDs (and optionally full records) that match the supplied filters. All filters are combined with AND logic. Results are ordered by chemicalID ASC and limited to 50,000 IDs per request. The connector sends includeData=1 and pages by chemicalIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then chemicalIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Get single FieldRoutes collection stage by ID** (Get). Get one Collection Stages record by id (/api/collectionStage/get, sent as stageID). Retrieves one or more full collection stage records by their IDs. Records are filtered to the offices associated with the current API session. Only stages with stageType = 'COLLECTION' are returned. Required: id.
- **List all FieldRoutes collection stages** (List). Search Collection Stages (/api/collectionStage/search): returns the full records. Returns a list of collection stage IDs (and optionally full records) matching the supplied filters. All filters are combined with AND logic. Results are ordered by stageID ASC and limited to 50,000 rows. The connector sends includeData=1 and pages by stageIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then stageIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Update a FieldRoutes collection stage by ID** (Update). Update a Collection Stages record (/api/collectionStage/update, id sent as stageID). Modifies an existing collection stage record. Only the fields you include in the request body will be updated; omitted fields retain their current values. The update is scoped to stages with stageType = 'COLLECTION'. Required: id.
- **Get single FieldRoutes compass customer by ID** (Get). Get one Compass Customers record by id (/api/compassCustomer/get, sent as customerIDs). Retrieves one or more compass customer records by their IDs. Limited to 1,000 records per request. Results include lead source attribution data. Required: id.
- **List all FieldRoutes compass customers** (List). Search Compass Customers (/api/compassCustomer/search): returns the full records. Returns a list of customer IDs (and optionally full records) for customers attributed via the Compass marketing platform. Results are gathered from all service centers associated with the specified offices. The connector sends includeData=1 and pages by customerIDs (FieldRoutes' primary-key paging: up to 1,000 records a page, then customerIDs &gt; the last id). Filters take a value, a list, or a JSON operator object ({"operator": "&gt;=", "value": ...}; operators =, !=, &gt;, &lt;, &gt;=, &lt;=, LIKE, IN, NOT IN, BETWEEN).
- **Create a FieldRoutes condition** (Create). Create a Conditions record (/api/condition/create). Creates a new condition for a customer. The condition is stamped with the current server time as dateFound and begins in the open state (resolved=0). Required: customerID, description, appointmentAdded.
- **FieldRoutes conditions create encoded image** (Create). Conditions: 11.2 Upload Image (Base64) (/api/condition/createEncodedImage). Uploads an image using a Base64-encoded payload submitted through standard POST parameters — an alternative to the multipart createImage endpoint for integrations that cannot produce multipart requests. Required: conditionID, encodedFile, filename.
- **FieldRoutes conditions create image** (Create). Conditions: 11.1 Upload Image (Multipart) (/api/condition/createImage). Uploads an image file for a condition using multipart/form-data. The file must be sent under the form field name uploadFile. Multipart upload: the file goes in uploadFile; 1 / 0 flags. Required: conditionID, uploadFile.
- **FieldRoutes conditions create recommended service** (Create). Conditions: 10.2 Add a Recommended Service (/api/condition/createRecommendedService). Links an existing service type to a condition. Both the condition and the service must belong to an office associated with your API credentials. Required: conditionID, serviceID.
- **Delete a FieldRoutes condition by ID** (Delete). Delete a Conditions record (/api/condition/delete, id sent as conditionID). Permanently removes a condition. The other fields go in the query; the connector sends them in the JSON body. Required: id.
- ...and 187 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
