Lightfield
by Lightfield
Read and write an agent-native CRM from your AI assistant. Five tools, but two of them are generic verbs onto the whole Lightfield API — 16 resources and 78 documented methods, including deletes and email sends. OAuth grants openid and offline_access only.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Lightfield via MCP
https://mcp.lightfield.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Lightfield Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The tool count does not measure the surface. Five tools front 16 API resources and 78 documented methods, counted from Lightfield's docs index on 2026-08-19. Review the API reference, not the tool list.
- The write surface cannot be enumerated from documentation. No published page states which API methods
write_to_lightfieldwill dispatch. Lightfield describes it as creating or updating; the API documents eight deletes and an email send. We did not test which are reachable. - OAuth offers no least-privilege option. The descriptor advertises
openidandoffline_accessonly. Lightfield's 26 per-object scopes are API-key scopes and have no equivalent in the MCP grant. - We could not verify tool behaviour ourselves. The endpoint returned HTTP 401 to an anonymous request on 2026-08-19, so no schemas and no safety annotations were readable. Every description here is Lightfield's.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. - Meeting transcripts and email bodies are in scope of a read. Both are documented fields on built-in objects, not a separately gated system.
- Email sending is create-only. Lightfield states that direct sends and drafts create new messages only, and that replies and forwards are not yet supported.
- Rate limits are shared with the API. 25 requests per second per organization for each of write, read and search, described as early-launch limits subject to change. A 429 carries
Retry-After. - Custom objects are not available yet. Lightfield lists them as coming soon, so the object model is the nine built-in types.
- Automations are gated and uninterruptible. Lightfield documents them as open beta on the Pro plan, and states a run executes to completion with no mid-run approval; review happens afterwards.
Frequently asked questions
How many things can the Lightfield MCP server actually do?
Far more than its five tools suggest. Two of the five are generic verbs — `read_from_lightfield` and `write_to_lightfield` — and Lightfield's own machine-readable docs index enumerates 16 API resources and 78 methods behind them, covering accounts, contacts, opportunities, meetings, emails, notes, tasks, files and lists. The tool count measures the dispatcher, not the surface.
Can the Lightfield connector delete records or send email?
Lightfield's documentation does not say either way, and that is the honest answer. The MCP page describes `write_to_lightfield` only as creating or updating records. The underlying API documents eight delete methods and an email send method requiring the `emails:create` scope. Whether the dispatcher forwards those is not stated in any published page we found.
What OAuth scopes does Lightfield MCP ask for?
Only two, and neither narrows data access. Lightfield's RFC 9728 descriptor advertises `openid` and `offline_access`, verified live on 2026-08-19. Those cover identity and refresh tokens. The per-object scopes in Lightfield's scope table — 26 of them, like `accounts:read` — apply to API keys, and no equivalent narrowing is offered over the MCP OAuth grant.
Do I need a Lightfield admin to add the connector in Claude?
Only for an organization-wide install. Lightfield's quickstart says an organization admin must add Lightfield as a custom connector before members can use it, and notes that path is unavailable on personal accounts. On a Free, Pro or Max personal account you add it yourself through Settings, Connectors, then complete the OAuth flow in the browser.
Why can a Lightfield agent read my meeting transcripts?
Because transcripts are a field on the Meeting object, not a separate system. Lightfield documents Meeting as a built-in object type carrying participants, meeting URL and a transcript field, retrievable through the API. Any grant broad enough to read meetings is broad enough to read what was said in them. The same holds for synced email bodies and attachments.
What rate limits apply to Lightfield MCP calls?
Lightfield documents 25 requests per second per organization, applied separately to write, read and search categories, and calls these early-launch limits subject to change. Exceeding one returns HTTP 429 with a `Retry-After` header. Every response carries `X-RateLimit-Remaining`. Those are API limits; Lightfield publishes no separate MCP quota, and each tool call consumes from the same buckets.
Sources
- Lightfield MCP quickstart — https://docs.lightfield.app/getting-started/mcp-quickstart/ (fetched 2026-08-19 as Markdown via the
.mdsuffix; this is thedocumentationURL Anthropic's directory publishes) · retrieved 2026-08-19 - Lightfield docs machine index — https://docs.lightfield.app/llms.txt (fetched 2026-08-19; the 16-resource, 78-method count is derived from its API Reference section) · retrieved 2026-08-19
- Lightfield object types — https://docs.lightfield.app/objects-in-lightfield/object-types/ (fetched 2026-08-19) · retrieved 2026-08-19
- Lightfield scopes — https://docs.lightfield.app/using-the-api/scopes/ (fetched 2026-08-19; 26 named per-object API-key scopes) · retrieved 2026-08-19
- Lightfield rate limits — https://docs.lightfield.app/using-the-api/rate-limits/ (fetched 2026-08-19) · retrieved 2026-08-19
- Lightfield emails and attachments — https://docs.lightfield.app/using-the-api/emails-and-attachments/ (fetched 2026-08-19) · retrieved 2026-08-19
- Lightfield automations — https://docs.lightfield.app/automations/overview/ (fetched 2026-08-19; absent from
llms.txt, found via the sitemap) · retrieved 2026-08-19 - Lightfield security and compliance — https://docs.lightfield.app/security/ (fetched 2026-08-19; SOC 2 Type 2, GDPR, HIPAA BAA on request) · retrieved 2026-08-19
- Lightfield docs sitemap — https://docs.lightfield.app/sitemap-index.xml and
sitemap-0.xml(fetched 2026-08-19; 512 URLs, one MCP page) · retrieved 2026-08-19 docs.lightfield.app/robots.txtis a bareAllow: /naming the sitemap, with noContent-Signalheader on any axis (fetched 2026-08-19). The marketing hostlightfield.app/robots.txtallows all but/studio/and/preview· retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://mcp.lightfield.app/.well-known/oauth-protected-resource and the path-append form
…/oauth-protected-resource/mcp(both fetched 2026-08-19, byte-identical; the path-insert form returns 404) · retrieved 2026-08-19 - Live RFC 8414 authorization-server metadata — https://mcp.lightfield.app/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer
https://api.stytch.lightfield.app) · retrieved 2026-08-19 - Live anonymous probe — 2026-08-19:
POSTto the endpoint returns HTTP 401{"error":"Unauthorized"}withwww-authenticate: Bearer resource_metadata="…"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/c1496483-94ab-4a4e-885c-d7d2696e6eeb (snapshot 2026-08-16;
permissionspublished as "Read + Write") · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Lightfield
- Tools
- 5
- Domain
- mcp.lightfield.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.