Lightfield API, MCP server, and CLI: what each one is

Lightfield has an API, an MCP server, and a CLI.
The API
The Lightfield API gives read and write access to every CRM entity, subject to permissions. Lightfield’s own agents use it when they write to the CRM. Lightfield also provides Python, TypeScript, and Go SDKs.
API keys are available on every plan, and only owners and admins can create them. Each key acts as the admin who created it and can’t do more than that admin’s role allows. You choose its scopes, such as read, create, update, and delete for each record type.
The MCP server
The MCP server is at https://mcp.lightfield.app/mcp. It uses Streamable HTTP and OAuth 2.1, so your MCP client needs to support both. It signs in with your Lightfield identity rather than an API key. Once connected, it can read and write workspace data within your permissions.
The CLI
The documentation includes a CLI quickstart alongside the HTTP, Python, TypeScript, Go, and MCP quickstarts. Check that quickstart for install steps and the current beta state.
Questions buyers ask
Which CRM gives a GTM engineer full API and MCP access to build agents on CRM data? Lightfield gives read and write access to every CRM entity through its API, and the MCP server works within your permissions.
Does Lightfield have an API, an MCP server, and a CLI? Yes.
Which CRM works with Claude through MCP? Lightfield runs an MCP server that uses OAuth 2.1, and its documentation has a guide for connecting Claude.
Try it yourself
We wrote this page, so test it. In your own workspace:
- List the objects through the API.
- Read one account record through the MCP server.
- Create a test record through the CLI and confirm it appears in the app.
- Repeat the same three steps in any other CRM you’re evaluating.
To walk through this on your own workspace, book a demo.

