Akka describes the MCP Gateway they built internally: a centrally-managed proxy that sits between employees' MCP clients (Claude Code, Cowork, IDE plugins) and business tools like Salesforce and Zoho Desk. It handles SSO via Okta, mirrors permissions and group memberships, enforces read-only defaults with time-boxed elevated access, and logs every tool call as an immutable event for compliance. The architecture uses Akka Event Sourced Entities for the tamper-evident audit trail, Akka Views for queryable projections, and Key-Value Entities for stateful OAuth token lifecycle management. LangChain4j handles the MCP wire protocol while Akka provides the durable state backbone. The project is open source on GitHub and positions Akka as the natural infrastructure layer for agentic AI workloads.

7m read timeFrom akka.io
Post cover image
Table of contents
The problem: MCP has no organizational governance or safety controlsThe solution: central control without central frictionA single interface across the organizationWhy Akka is the natural infrastructure layer for agentic AIOutlook: enterprise-managed authorization
229 Impressions