AI agent for LCL API
Connect LCL API to your AI agent through the WorkAist MCP server. FR banking
The WorkAist LCL API connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write LCL API data — banking — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The LCL API connector authenticates via OAuth 2.0.
WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.
Frequently paired with LCL API
FAQ
Can a WorkAist AI agent really automate LCL API end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the LCL API API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents LCL API as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for LCL API's own API costs (if any) and the LLM tokens your agent consumes.
Is my LCL API data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from LCL API → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if LCL API changes its API?▼
The connector is versioned and published openly. When LCL API ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.