Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Read and write an agent-native CRM.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Lightfield MCP server connects the Lightfield CRM to Claude, ChatGPT and any MCP-compatible agent. It ships five tools, but two of them are generic verbs that dispatch onto Lightfield's whole REST API — 16 resources and 78 documented methods covering accounts, contacts, opportunities, meetings, emails, notes and tasks. Sign-in is OAuth, granting openid and offline_access.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
write_to_lightfield will dispatch. Lightfield describes it as creating or updating; the API documents eight deletes and an email send. We did not test which are reachable.openid and offline_access only. Lightfield's 26 per-object scopes are API-key scopes and have no equivalent in the MCP grant.prompts/list, so we cannot say whether the server serves any.Retry-After.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.
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.
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.
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.
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.
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.
.md suffix; this is the documentation URL Anthropic's directory publishes) · retrieved 2026-08-19llms.txt, found via the sitemap) · retrieved 2026-08-19sitemap-0.xml (fetched 2026-08-19; 512 URLs, one MCP page) · retrieved 2026-08-19docs.lightfield.app/robots.txt is a bare Allow: / naming the sitemap, with no Content-Signal header on any axis (fetched 2026-08-19). The marketing host lightfield.app/robots.txt allows all but /studio/ and /preview · retrieved 2026-08-19…/oauth-protected-resource/mcp (both fetched 2026-08-19, byte-identical; the path-insert form returns 404) · retrieved 2026-08-19https://api.stytch.lightfield.app) · retrieved 2026-08-19POST to the endpoint returns HTTP 401 {"error":"Unauthorized"} with www-authenticate: Bearer resource_metadata="…" · retrieved 2026-08-19permissions published as "Read + Write") · retrieved 2026-08-16Connect Lightfield once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.