Lightfield MCP connector
Connecting Lightfield to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent read and update your Lightfield accounts, contacts and lists as the signed-in person, with every action recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
Update the Acme account: owner is Priya, stage is proposal.
Working in Lightfield with Elaichi
-
Lightfield accounts get definitions
-
Lightfield accounts list field history
-
Get single Lightfield account by ID
How to connect Lightfield to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lightfield 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.
Lightfield 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.
Lightfield 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.
Lightfield 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.
Lightfield 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 Lightfield 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 Lightfield through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lightfield is logged.
-
Sales
Catch the account up after a call
Describe what changed on the call and the Lightfield account and contact records are updated for you, without clicking through every field.
-
Sales
Check who is on a target list
Ask which accounts, contacts and opportunities sit on a Lightfield list before a territory review or an outreach push.
-
Marketing
Build a list for the next campaign
Create a new Lightfield list and fill it with the contacts that match a plain description, such as everyone at manufacturing accounts in the Northeast.
-
Customer Success
See how an account changed over time
Pull the field history for a Lightfield account to see when the owner, stage or renewal date changed and what the value was before.
-
Revenue Operations
Clean up duplicate contacts safely
Find duplicate contacts in Lightfield, remove the extra copies, and restore one if a deletion turns out to be a mistake.
-
Sales Development
Add new prospects without leaving the chat
Paste the details from an inbound email and a new Lightfield contact and account are created with the right fields filled, based on how your Lightfield fields are defined.
Try asking
- “Update the Acme account: owner is Priya, stage is proposal.”
- “Which contacts are on the Q3 enterprise list?”
- “Show the field history for the Northwind account this month.”
What connecting Lightfield gets you
6 screens from Elaichi, each doing one job for your Lightfield account.
Ask Elaichi to work across your apps.
Update the Acme account: owner is Priya, stage is proposal.
Which contacts are on the Q3 enterprise list?
Show the field history for the Northwind account this month.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Lightfield accounts in plain language.
Type a question and get answers from live Lightfield contacts, accounts and lists.
Copy the endpoint
AI apps
One endpoint puts Lightfield in every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lightfield through one governed endpoint, no SDK, no shared API key.
Tool catalog
87 Lightfield tools, no code to write.
Accounts, contacts, lists and field history, covered without building anything yourself.
Toolboxes
Every team gets its own Lightfield toolbox.
Sales, Marketing and Customer Success each work from a toolbox scoped to their job.
Shared connections
Share Lightfield access without sharing the key.
One person connects Lightfield, teammates work through it and never see the API key.
Audit log
Every Lightfield change names who made it.
When, who, what happened and which account or contact, 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.
Lightfield digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Lightfield
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
Lightfield
Queued
Workflows
A schedule starts Lightfield work, a person approves.
New Lightfield accounts are fetched, grouped, drafted into a digest, approved, then posted back.
Lightfield health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales Americas 27%
Marketing 21%
Customer Success 18%
Collections and dashboards
Lightfield numbers arrive before anyone asks.
Accounts created over 14 days, broken down by team, refreshed on a schedule with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lightfield
All three can connect Lightfield 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 Lightfield tools | Allow or restrict single Lightfield 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 Lightfield 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.
Lightfield tools for your AI agents
87 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lightfield, 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 Lightfield to Claude?
In Elaichi, choose Lightfield and paste your Lightfield API key when asked. 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 Elaichi and Lightfield is ready to use in Claude.
Does Lightfield work with ChatGPT and Cursor as well as Claude?
Yes. Once Lightfield is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Lightfield once and every client gets it.
What can an AI agent actually do with my Lightfield data?
An AI agent connected through Elaichi can look up Lightfield accounts and contacts, create new ones, update them after a call, and remove or restore records. It can build Lightfield lists, show which accounts, contacts and opportunities are on a list, and pull the history of how a field changed over time. Short, concrete asks such as "update the Acme account owner to Priya" work better than long paragraphs.
Does connecting Lightfield give the AI access to everything in my CRM?
The AI can only reach what the Lightfield API key you connected can reach, and each person still signs in to Elaichi as themselves, so every Lightfield action is tied to a named person. Elaichi can then narrow that access further with roles and restrictions. It never widens what Lightfield itself allows.
Can I stop an agent from deleting or changing things in Lightfield?
Yes. Restrictions in Elaichi work per action, so you can allow reading Lightfield accounts and contacts while restricting deletion or updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Lightfield connection when someone leaves?
Offboarding a person in Elaichi ends their access to Lightfield through every client at once. A Lightfield connection they shared keeps working for everyone else on the team. If you want to remove Lightfield entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Lightfield MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lightfield 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 Lightfield?
Yes. Both let Claude, ChatGPT or Cursor use Lightfield. 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 Lightfield call.
How is Elaichi different from Composio for Lightfield?
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 Lightfield: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lightfield 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