Connecting Your Client
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 works with any client that implements the Model Context Protocol. Below are configuration steps for a few commonly used clients. We keep these instructions current to the best of our knowledge, but a client provider can change how their product works at any time, so check their documentation if anything does not match.
We recommend keeping your MCP client, and any bridge it uses such as mcp-remote, in sync with the latest version of the Model Context Protocol.
Configuring the MCP Server in Your Client
Wherever a configuration asks for a URL, use your Mambu MCP URL, shown here as <mcp-url-for-your-tenant>. See Getting Started with Mambu MCP (Connecting Your Client > Step 1) for how to find it. The server name, shown as mambu-core-mcp, can be any label you choose.
Mambu MCP uses a fixed OAuth client ID, mcp-client, and no client secret. The bridge configurations below include it. Clients that connect directly over HTTP, such as VS Code, prompt for it the first time you sign in: enter mcp-client and leave the secret blank.
ChatGPT
ChatGPT connects over HTTP as an OAuth plugin, so there is no configuration file or bridge.
- In ChatGPT, go to Plugins, select Add, and choose Add custom MCP server.
- Enter a name for the connection, for example
mambu-core-mcp. - Enter
<mcp-url-for-your-tenant>as the server URL and choose OAuth as the authentication method. - Open Advanced OAuth settings.
- Set Registration method to User-Defined OAuth Client.
- Enter
mcp-clientas the OAuth client ID, leave the client secret blank, and make sure Token endpoint auth method isnone. - Select Create as a plugin and sign in with your Mambu credentials.
Claude Code
Edit your Claude Code MCP configuration file:
- macOS:
~/.claude.json - Windows:
%USERPROFILE%\.claude.json
{
"mcpServers": {
"mambu-core-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto"
]
}
}
}
Claude Desktop
Edit your Claude Desktop MCP configuration file.
macOS
File location: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mambu-core-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto"
]
}
}
}
Windows
File location: %APPDATA%\Claude\claude_desktop_config.json
On Windows, Claude Desktop launches npx through the command interpreter:
{
"mcpServers": {
"mambu-core-mcp": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto"
]
}
}
}
Codex
Codex connects over HTTP as an OAuth plugin, so there is no configuration file or bridge.
- In Codex, go to Plugins, select Add, and choose Add custom MCP server.
- Enter a name for the connection, for example
mambu-core-mcp. - Enter
<mcp-url-for-your-tenant>as the server URL and choose OAuth as the authentication method. - Open Advanced OAuth settings.
- Set Registration method to User-Defined OAuth Client.
- Enter
mcp-clientas the OAuth client ID, leave the client secret blank, and make sure Token endpoint auth method isnone. - Select Create as a plugin and sign in with your Mambu credentials.
Cursor
Edit your Cursor MCP configuration file:
- macOS:
~/.cursor/mcp.json - Windows:
%USERPROFILE%\.cursor\mcp.json
{
"mcpServers": {
"mambu-core-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto"
]
}
}
}
Junie (JetBrains)
Edit your Junie MCP configuration file:
- macOS:
~/.junie/mcp/mcp.json - Windows:
%USERPROFILE%\.junie\mcp\mcp.json
{
"mcpServers": {
"mambu-core-mcp": {
"type": "com.intellij.ml.llm.matterhorn.core.mcp.McpServerConfiguration.McpServerCommand",
"name": "mambu-core-mcp",
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto"
],
"sourcePath": "~/.junie/mcp/mcp.json",
"enabled": "true"
}
}
}
VS Code
Edit your VS Code MCP configuration file:
- macOS:
~/Library/Application Support/Code/User/mcp.json - Windows:
%APPDATA%\Code\User\mcp.json
{
"servers": {
"mambu-core-mcp": {
"type": "http",
"url": "<mcp-url-for-your-tenant>"
}
}
}
When prompted for client registration details, enter mcp-client as the client ID and leave the secret blank.
Restricting Operations
To limit which operations a client can use, send an enabled-operations header. It is an allow-list of the operations to enable, written in the group/operation_name format. The header can only narrow the access already configured in Agent Studio at the tenant or user level. It cannot widen it. See Configuring Access for how that access is set.
For clients that use the mcp-remote bridge (Claude Desktop, Claude Code, Junie, Cursor), pass it as a --header argument:
"args": [
"-y",
"mcp-remote",
"<mcp-url-for-your-tenant>",
"--static-oauth-client-info",
"{\"client_id\":\"mcp-client\"}",
"--protocol",
"auto",
"--header",
"enabled-operations: clients/list,clients/get_by_id,deposits/list"
]
For clients that connect over HTTP (VS Code), add a headers field to the server instead:
{
"servers": {
"mambu-core-mcp": {
"type": "http",
"url": "<mcp-url-for-your-tenant>",
"headers": {
"enabled-operations": "clients/list,clients/get_by_id,deposits/list"
}
}
}
}
For the operation names you can scope to, see Mambu Core MCP.