Lightfield MCP connector
Connecting Lightfield to Elaichi lets Claude, ChatGPT, Cursor 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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Lightfield to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lightfield once
-
Open Connections, choose Add connection, and pick Lightfield.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Lightfield API key. One person generates a token in Lightfield and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
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 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 today. 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.
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.
Use cases
What teams do with Lightfield through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Lightfield gets you
6 screens from the product, each doing one job for your Lightfield account.
The agent
Ask about Lightfield accounts in plain language.
Type a question and get answers from live Lightfield contacts, accounts and lists.
- accounts
- contacts
- lists
- opportunities
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 or Cursor
MCP clients
One endpoint puts Lightfield in every client.
Claude, ChatGPT and Cursor reach Lightfield through one governed endpoint, no SDK, no shared API key.
Copy the endpoint
Tool catalog
87 Lightfield tools, no code to write.
Accounts, contacts, lists and field history, covered without building anything yourself.
- Lightfield auth validate
- Lightfield accounts get definitions
- Lightfield accounts list field history
- Create a Lightfield account
Toolboxes
Every team gets its own Lightfield toolbox.
Sales, Marketing and Customer Success each work from a toolbox scoped to their job.
- Sales
- Marketing
- Customer Success
- Sales Development
Shared connections
Share Lightfield access without sharing the key.
One person connects Lightfield, teammates work through it and never see the API key.
- Sales EMEA
- Sales Americas
- Marketing
- Customer Success
Audit log
Every Lightfield change names who made it.
When, who, what happened and which account or contact, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Lightfield work, a person approves.
New Lightfield accounts are fetched, grouped, drafted into a digest, approved, then posted back.
Lightfield digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Lightfield
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking deletion or updates. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Lightfield in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.