LoanPro Multi-Agent Loan Servicing Assistant: How Compositional Routing and the MCP Gateway Isolate Tool Access in Regulated Credit Scenarios
LoanPro, in collaboration with Amazon Web Services (AWS), has built a multi-agent loan servicing assistant that uses compositional routing to direct requests to specialized agents and exposes internal APIs as tools via the Model Context Protocol (MCP) through the AgentCore Gateway. This architecture supports loan servicing scenarios requiring the real-time synthesis of approximately 1,400 account fields; the vendor reports call times reduced by up to 15% and account summary generation in under 15 seconds.
When answering borrower calls, loan servicing agents must synthesize approximately 1,400 account fields from eight API endpoints—including payment history, loan terms, open tickets, and available workflow actions—within dozens of seconds to provide meaningful responses. The multi-agent assistant developed by LoanPro in partnership with AWS Generative AI Innovation Center and partner AllCloud is designed around a core decision: rather than having a single large model handle all tasks, it uses a compositional agent to route requests to specialized agents, then isolates tool access through an MCP gateway.
The architecture consists of three layers of collaboration. A composer agent receives requests and determines which specialist agent should handle them: one focused on data retrieval and account summarization, and another on action selection and workflow recommendations. Specialist agents invoke LoanPro’s internal APIs via the AgentCore Gateway using the Model Context Protocol (MCP); the gateway locates tools in a catalog, handles authentication, and manages connections. The rationale for this separation over a monolithic model is evaluability: each specialist agent can be independently tested, tuned, and scaled without requiring a full system redeployment when modifying a single function.
Security boundaries are a critical constraint in regulated scenarios. The AgentCore Gateway isolates LoanPro’s APIs behind a managed boundary, while AWS Lambda functions validate caller signatures against consistency with the single sign-on (SSO) service, and role-based permissions are verified with every request. All AI operations are written to audit logs and attributed to named individuals. The team chose a gateway plus Lambda approach over direct integration for three reasons: authentication is centralized at a managed entry point, internal APIs are isolated behind a managed boundary, and adding new tools does not require redeploying the agents.