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.
- App credentials
- Free 14-day trial
- No credit card
Find the customer at 42 Elm Street and show their open invoices.
Working in FieldEdge with Elaichi
-
Get single FieldEdge agreement by ID
-
List all FieldEdge agreements
-
Get single FieldEdge business unit by ID
How to connect FieldEdge to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
FieldEdge MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
FieldEdge MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
FieldEdge MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- 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 FieldEdge to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 FieldEdge through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in FieldEdge is logged.
-
Office
Pull up the caller before they finish
When the phone rings, find the FieldEdge customer by phone number or address and see their notes, agreements and open invoices in one answer.
-
Service
Log what the technician found on site
After a visit, add a customer note describing the fault and attach the photo, so the next technician reads it before they arrive.
-
Billing
Fix an invoice before it goes out
List the invoices from this week, spot the one with the wrong line, and update it without opening FieldEdge.
-
Sales
Find customers without a service agreement
Compare the customer list against agreements, then tag the ones with no plan so the renewal call list builds itself.
-
Management
See who sits in each business unit
List business units and the employees in them, so you can answer who covers plumbing in the north branch without asking around.
-
Customer service
Set up a new customer in seconds
Create the customer record from the details in an email, tag them with the right campaign, and add the first note.
Try asking
- “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.”
What connecting FieldEdge gets you
6 screens from Elaichi, each doing one job for your FieldEdge account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any FieldEdge customer in plain words.
Three starter prompts pull live customers, agreements and invoices straight from FieldEdge.
Copy the endpoint
AI apps
One endpoint puts FieldEdge in every client.
Claude, ChatGPT and Cursor reach FieldEdge through one governed endpoint, no SDK, no shared key.
Tool catalog
59 FieldEdge tools, ready without writing code.
Customers, agreements, invoices, notes, employees and business units, covered without custom code.
Toolboxes
Every team gets its own FieldEdge toolbox.
Billing works with invoices, dispatch with customers and notes, each scoped to the team.
Shared connections
Share a FieldEdge connection, never a credential.
One person connects FieldEdge, teams work through it and nobody else handles the credential.
Audit log
Every FieldEdge change is logged with a name.
When, who, what happened and which customer or invoice, in an append-only log.
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.
FieldEdge digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
FieldEdge
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
FieldEdge
Queued
Workflows
A schedule starts the FieldEdge work itself.
Invoices are fetched, grouped and drafted into a digest, approved, then posted to FieldEdge.
FieldEdge health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Agreements
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
HVAC 34%
Plumbing 27%
Electrical 21%
Billing 18%
Collections and dashboards
FieldEdge health, computed without asking a model.
Four metrics, 14 days of customers created and a team breakdown, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
FieldEdge tools for your AI agents
59 tools are ready to call through Elaichi's MCP endpoint the moment you connect FieldEdge, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put FieldEdge 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