Mambu MCP Overview
Mambu MCP is currently available as a Limited Availability feature. To request access or more information, contact your Mambu account executive or your customer success manager.
Mambu MCP connects MCP-compatible agents and AI clients to Mambu's systems, starting with Mambu Core. It provides governed access to the data and operations an AI client needs, without middleware.
It is built, hosted and maintained by Mambu and reached over the network. There is no bridge to build and no upkeep on your side, and it stays current as Mambu's APIs evolve.
What Mambu MCP Provides
Mambu MCP provides four capabilities: connecting clients, configuring access, governing use, and monitoring activity.
Connect
- Connect the AI models and clients you already use. Mambu MCP is model- and client-agnostic.
- Access 300+ Mambu operations through one token-efficient interface.
- A search-and-invoke design: search finds the operation and invoke runs it, mapping to the right API call, so there is no hand-mapping of APIs.
Configure
- Your team configures which operations are available to the tenant, reusable permission templates, and user access, without code.
Govern
- Read operations are enabled by default. Every execute operation is off until you enable it at tenant level.
- Per-user limits and controls are configurable.
Monitor
- See who accessed what, how and when.
- Usage is tracked automatically, and every invocation is traceable and auditable.
How It Works
- Authentication. The MCP client connects to Mambu MCP, and the user signs in via their browser. Agents act in name of real users with their own permissions.
- Resolution. When a user asks a question, the AI model identifies the Mambu operation it needs, using search and invoke.
- Execution. Mambu MCP checks the user's permissions and the tenant's configuration, then calls the relevant Mambu API.
- Response. The Mambu API returns the requested data to Mambu MCP, which passes it back to the AI client.
Mambu MCP is not an AI agent itself, and it stores no banking data. The AI client decides what to do, Mambu MCP resolves each request and calls Mambu. The data remains stored in the underlying Mambu system.