MCP Server

The Bakkt MCP server lets AI agents use Bakkt API through the Model Context Protocol. Each tool wraps the Bakkt APIs described in these docs, so the same API key, users and limits apply.

Endpoints

EnvironmentURL
Sandboxhttps://sandbox.mcp.bakkt.com
Productionhttps://mcp.bakkt.com

The server uses the Streamable HTTP transport and is stateless: send every request as an HTTP POST to the URL above. Server-initiated streams (GET) and OAuth are not supported.

Connect

Point your MCP client or agent platform at the endpoint and send your API key in the x-bakkt-api-key header, in the same API-Key <key> form as the Authorization header of the REST APIs. Use your sandbox key while testing (see the Quick start). For clients that use an mcpServers configuration:

{
  "mcpServers": {
    "bakkt": {
      "url": "https://sandbox.mcp.bakkt.com",
      "headers": {
        "x-bakkt-api-key": "API-Key <YOUR_API_KEY>"
      }
    }
  }
}

To check the connection without a client, list the available tools:

curl -X POST https://sandbox.mcp.bakkt.com \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "x-bakkt-api-key: API-Key $BAKKT_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

No initialize call is needed first. The result arrives as a server-sent event: an event: message line followed by a data: line that contains the JSON-RPC response.

Authentication

The MCP server uses the same credentials as the Bakkt REST APIs, sent as HTTP headers on every request.

HeaderIdentifiesLets the agent
x-bakkt-api-keyYour merchant, as API-Key <key>Use merchant-level data and sign users in. Required on every request.
x-bakkt-user-uuidA user of your merchantRead that user's data.
x-bakkt-session-idA signed-in userRead the user's data and create, change or move anything on the user's behalf.

The tools and resources listed for a request depend on these headers. With only the API key, the list holds merchant-level tools and the tools that sign a user in. A user UUID adds what reads the user's data. A session ID adds everything that changes something or moves money. If both user headers are sent, the session ID is used.

A session ID comes from signing the user in, the same way as in the REST APIs: with an email one-time code, or with a Sign-In with Ethereum signature from the user's wallet. Sign-in needs only the API key. Sessions expire; when a call returns Unauthorized, sign the user in again. See the Authentication guide for both methods.

  • Set the user headers per request, so one connection never mixes users.
  • Keep your API key and session IDs on your server. Never put them in client-side code or share them with end users.

Tools

Onboarding API

ToolDescription
onboardingUserCreateCreate a user.
onboardingSessionCreateWithSiweSign a user in with their custodial wallet and get a session ID.
onboardingAuthLoginStartStart a login: email the user a sign-in code, or sign in with their own wallet.
onboardingAuthOtpSubmitExchange the emailed sign-in code for a session ID.
onboardingUserUpdateUpdate a user's email, phone number or address.
onboardingPhoneOtpSendSend a verification code to the user's phone.
onboardingPhoneOtpCheckVerify the phone code the user received.
onboardingKycApplicationCreateStart a KYC application for the user.
onboardingKycDocumentUploadUpload a KYC document.
onboardingKycVerificationStartSubmit the KYC application for verification.

Accounts API

ToolDescription
accountsAccountGetOrCreateGet the user's bank account in a currency, or open one.
accountsRemittanceStartStart the remittance locked in a quote. A quote can be used once.
accountsTransactionListList the user's transactions with filters and pagination.
accountsAccountCreateOpen a Bakkt bank account in a given currency and type.
accountsAccountListList the user's Bakkt bank accounts and balances.
accountsMicroDepositListList micro-deposits for an account.
accountsRemittanceQuoteCreateQuote a USD remittance from the user's checking account to a beneficiary.
accountsRemittanceListList the user's remittances, newest first.
accountsBillPayPaymentListList bill pay payments for an account.
accountsBillPayPaymentListByAccountTypeList bill pay payments for the user's account of a given type.
accountsBillPayPaymentGetGet a single bill pay payment.
accountsTransferBetweenOwnAccountsMove money between the user's own checking and savings accounts.
accountsAccountBankDetailsGetGet the account and routing number of the user's USD checking account.
accountsDebitCardListList the user's debit cards for a currency.

Stablecoin API

ToolDescription
stablecoinWalletCreateCreate a custodial wallet on a chain.
stablecoinWalletGetByChainGet the user's stablecoin deposit address on a chain.
stablecoinTokenPreferencesSetSet the default stablecoin and chain for a fiat currency.
stablecoinLinkedBankAccountProfileCreateCreate the profile needed to link a US bank account.
stablecoinLinkedBankAccountLinkGet a hosted URL where the user links a US bank account.
stablecoinLinkedBankAccountUnlinkUnlink a linked bank account.
stablecoinLinkedBankAccountFundsPullPull USD from the user's linked bank account.
stablecoinOfframpCreateRequest an off-ramp from the user's custodial wallet to a beneficiary.
stablecoinBeneficiaryCreateSave a beneficiary bank account.
stablecoinOfframpConfirmConfirm a requested off-ramp with its one-time password (OTP).
stablecoinBeneficiaryListList saved beneficiaries.
stablecoinBeneficiaryGetGet a single beneficiary.
stablecoinBeneficiaryDeleteDelete a beneficiary.
stablecoinTransactionEstimateEstimate the fee for a payout.
stablecoinTransactionMaxAmountEstimateCalculate the most that can be sent from a budget or balance.
stablecoinTransferValidateCheck balance, fees, limits and bank support before sending.
stablecoinBeneficiaryValidateCheck beneficiary account details for a currency.
stablecoinFeeGetGet fees for an on-ramp or off-ramp amount.
stablecoinExchangeRateConvertConvert an amount between currencies.
stablecoinBeneficiaryFieldsGetGet the required beneficiary fields for each currency.
stablecoinBankListSearch supported banks for a payout currency.
stablecoinWalletBalanceGetCheck a wallet's token balance on chain.

Resources

Read-only data your client can read by URI.

ResourceDescription
bakkt://onboarding/userThe user's profile and onboarding status.
bakkt://onboarding/kyc/applicationKYC application status.
bakkt://onboarding/terms-and-conditionsThe terms and privacy documents.
bakkt://stablecoin/wallet/{walletUuid}Wallet details.
bakkt://stablecoin/linked-bank-account/profileThe user's linked bank account profile.
bakkt://stablecoin/currencies/{direction}On-ramp or off-ramp currencies available to the user.
bakkt://stablecoin/required-transfer-fieldsRequired bank fields by currency.
bakkt://stablecoin/detailed-offramp-currenciesDetailed off-ramp field rules for the user's country.
bakkt://stablecoin/banks/{currency}Supported banks for a currency.

Troubleshooting

ResponseCauseFix
401 The x-bakkt-api-key header is required...API key header missingSend x-bakkt-api-key on every request.
401 Merchant validation failed...API key invalid, sent without the API-Key prefix, or from the other environmentSend API-Key <key> and check the key matches the environment's URL.
401 Unauthorized or User validation failed...The session expired, or the user is unknown for this merchantSign the user in again, or check the UUID.
406 Not Acceptable...Accept header missing a typeSend Accept: application/json, text/event-stream.
415 Unsupported Media Type...Wrong body typeSend Content-Type: application/json.
404GET request or SSE clientUse HTTP POST (Streamable HTTP).
A tool or resource is missing from the list, or a call returns Tool ... not foundThe request does not carry the user header it needs. Such tools are only listed when the request has itSend x-bakkt-user-uuid (reads) or x-bakkt-session-id (changes and money movement), then list again. See Authentication.
200 with a result that starts with [ERROR]The tool failed. Tool errors are returned as a normal result, not as an HTTP errorRead the text after [ERROR].

If your network restricts outbound traffic, allow the MCP host for your environment.


Did this page help you?