Bakkt MCP Server is now live
🚀 Bakkt MCP Server is now live! 🎉
AI agents and MCP-compatible clients can now use Bakkt through the Model Context Protocol. Each tool wraps a Bakkt API, so the same API key, users and limits apply.
🔐 How authentication works
- Send your API key in the
x-bakkt-api-keyheader, asAPI-Key <key>, on every request. - To act for a user, send either
x-bakkt-user-uuid(reads that user's data) orx-bakkt-session-id(reads and changes data on the user's behalf). If both are sent, the session ID is used. - The tools and resources an agent sees depend on these headers. With only the API key, it sees merchant-level tools and the tools that sign a user in. A user UUID or session ID adds the user-level tools and resources.
- A session ID comes from signing the user in, either with an email one-time code or with a wallet signature (Sign-In with Ethereum). Sessions expire, so sign the user in again when a call returns
Unauthorized.
⚠️ Keep API keys and session IDs on your server. Never put them in client-side code.
🛠️ What it supports
The server launches with 50+ tools and resources covering the Onboarding, Accounts and Stablecoin APIs, from creating and verifying users to managing Bakkt bank accounts, wallets, beneficiaries and payouts. It is available in Sandbox and Production. We are continuing to build it: more tools and features are planned for the coming weeks, and we will announce them here as they ship.
📖 See the MCP Server documentation for endpoints, connection examples and the full list of tools and resources.
🙌 Let us know if you need help connecting your agent!
