Skip to content

CRM

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

List tomorrow's appointments for the north branch

Working in FieldRoutes with Elaichi

  • Get single FieldRoutes access control by ID
  • List all FieldRoutes access controls
  • Get single FieldRoutes additional contact by ID
Ask anything…
Governance / Audit log Last 24 hours
FieldRoutes Get single FieldRoutes additional contact by ID Emily Carter · ChatGPT · 9:41 AM Done
FieldRoutes List all FieldRoutes access controls Emily Carter · ChatGPT · 9:41 AM Done
FieldRoutes Get single FieldRoutes access control by ID Emily Carter · ChatGPT · 9:41 AM Done
FieldRoutes Create a FieldRoutes additional contact Megan Brooks · Claude · 9:38 AM Done
FieldRoutes List all FieldRoutes additional contacts Ryan Hayes · Cursor · 9:35 AM Done

How to connect FieldRoutes to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

FieldRoutes MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ 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

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

FieldRoutes MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

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

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with FieldRoutes through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in FieldRoutes is logged.

  • Office

    Move an appointment while the customer waits

    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.

  • Dispatch

    See what is booked before trucks roll

    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.

  • Customer service

    Keep every contact on the account current

    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.

  • Billing

    Confirm a payment landed on the account

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

  • Operations

    Find out why appointments keep getting canceled

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

  • Management

    Close out completed jobs the same day

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

Try asking

  • “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”

See all 237 FieldRoutes tools →

What connecting FieldRoutes gets you

6 screens from Elaichi, each doing one job for your FieldRoutes account.

Elaichi Agent

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about today's appointments in plain language.

Type a question and get answers from live FieldRoutes appointments, contacts and payments.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint connects FieldRoutes to every client.

Claude, ChatGPT and Cursor reach FieldRoutes through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
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 > the last id). Filters take a value, a list, or a JSON operator object ({"operator": ">=", "value": ...}; operators =, !=, >, <, >=, <=, 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 > the last id). Filters take a value, a list, or a JSON operator object ({"operator": ">=", "value": ...}; operators =, !=, >, <, >=, <=, LIKE, IN, NOT IN, BETWEEN).

Tool catalog

237 FieldRoutes tools ready with no code.

Appointments, reminders, contacts and applied payments, covered without writing a line of code.

ElaichiToolboxes
Name Source template Tools Created

Office toolbox

FieldRoutes · appointments and reminders

FieldRoutes starter 18 Mar 4, 2026

Dispatch toolbox

FieldRoutes · routes and reschedules

— 9 Mar 2, 2026

Customer service toolbox

FieldRoutes · contacts and cancellations

— 24 Feb 27, 2026

Billing toolbox

FieldRoutes · applied payments

FieldRoutes starter 6 Feb 19, 2026

Operations toolbox

FieldRoutes · cancellation and reschedule reasons

— 31 Jan 30, 2026

Sales toolbox

FieldRoutes · new accounts and contacts

— 12 Jan 22, 2026

Toolboxes

Every team gets its own FieldRoutes toolbox.

Dispatch, billing and the office each see the FieldRoutes tools their work needs.

ElaichiConnections
Connection Scope Status Access
FI

FieldRoutes (Office)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FI

FieldRoutes (Dispatch)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FI

FieldRoutes (Billing)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FI

FieldRoutes (Customer service)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
FI

FieldRoutes (North branch)

Connected by Ryan Hayes

Personal • Active Not shared
FI

FieldRoutes (South branch)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates book appointments without seeing the key.

One person connects FieldRoutes, shares it with teams, and nobody else touches the API key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

FieldRoutes Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

FieldRoutes Appointments Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

FieldRoutes Appointments List Toolbox

Audit log

Know who rescheduled every FieldRoutes appointment.

Each call records when, who, what happened and which appointment or contact it touched.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

FieldRoutes digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch appointments

    FieldRoutes

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    FieldRoutes

    Queued

Workflows

A schedule drafts the daily route digest.

Appointments are fetched, grouped by technician, drafted, approved by a person, then posted to FieldRoutes.

FieldRoutes health

Refreshed 4 minutes ago · every 15 minutes · from the appointments collection

Live

Appointments

1,284 ↓ 12%

Contacts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Appointments created

Last 14 days

By team

Share of activity

Office 34%

Dispatch 27%

Billing 21%

Customer service 18%

Collections and dashboards

FieldRoutes appointment numbers refresh on their own.

Four metrics, 14 days of appointments created and a breakdown by team, no model involved.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for FieldRoutes, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

FieldRoutes tools for your AI agents

237 tools are ready to call through Elaichi's MCP endpoint the moment you connect FieldRoutes, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 149 of 237 FieldRoutes tools here. Connect FieldRoutes and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

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.

Put FieldRoutes in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot