MCP bridge
Arc
Arc is the spark that closes the gap between driving Lionlight with exclusively human operators and driving it with agentic AI. It gives a client's own agents a clean MCP bridge into knowledge and action.
Standalone by design
Arc is a broker, not an embedded shortcut. It keeps the capability boundary at the edge instead of smearing it into the knowledge or execution planes.
Read from Prism, act through Circuit
Agents read approved context from Prism and every side effect still funnels through Circuit, preserving one auditable path to action.
Bounded by Playbooks
Agents authenticate to Arc, never the Web UI, and operate only within the capabilities, context, and constraints declared in reviewed Playbooks.
More than a DIY MCP server
Many MCP integrations are just another pile of prompt glue and credentials. Arc is different because it preserves the product boundaries: knowledge stays in Prism, side effects stay in Circuit, and the agent boundary stays inspectable.
Why teams add it
Arc lets teams introduce client-owned agents without rebuilding the stack around them. The same reviewed Playbooks, approval gates, and effectors still apply, so adopting agentic AI does not mean starting over from a looser trust model.
Where it fits
Arc sits between understanding and execution. It is the bridge that allows a client's agents to work across Lionlight without turning either Prism or Circuit into a general-purpose bot host.
Ready to put Lionlight to work?
Whether you need a clearer Living Map, a safer execution layer, or an MCP bridge your agents can actually trust, we will help you map the right next step for your organisation.
Book a discovery call