MCP Bamm MCP Server

MCP server for bamm (borrow automated market maker). The mcp bamm mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

The BAMM MCP Server enables AI agents to interact with Borrow Automated Market Maker (BAMM) contracts on the Fraxtal blockchain. This server provides comprehensive access to BAMM positions, lending, borrowing, and collateral management operations.

• Position Management — View and manage your active BAMM positions across all pools
• Lending Operations — Lend Fraxswap LP tokens to BAMM contracts to earn yield
• Borrowing — Borrow tokens against your collateral from BAMM positions
• Collateral Management — Add or remove collateral from your BAMM positions
• Pool Analytics — Access statistics for all BAMM pools

Its toolset

Everything the assistant can do here goes through one of these:

• ADD_COLLATERAL — The ADD_COLLATERAL tool exposed by this server
• BORROW — The BORROW tool exposed by this server
• LEND — The LEND tool exposed by this server
• REMOVE_COLLATERAL — The REMOVE_COLLATERAL tool exposed by this server
• REPAY — The REPAY tool exposed by this server
• WITHDRAW — Withdraw LP tokens from a BAMM contract by redeeming BAMM tokens

Adding it to your client

@iqai/mcp-bamm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need one environment variable: WALLET_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Bamm's toolset — ADD_COLLATERAL, BORROW, LEND and 3 more — is a fair guide to whether it matches your workflow. It is maintained by IQAIcom; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp bamm mcp server does with a few real requests.