Bridge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_API_KEY | Yes | Your Bridge API key | |
| BRIDGE_BASE_URL | No | Optional base URL for sandbox environment (e.g., https://api.sandbox.bridge.xyz/v0) | https://api.bridge.xyz/v0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_create_customerA | Create a new customer (individual or business) for KYC/KYB onboarding |
| bridge_get_customerA | Get a customer by ID |
| bridge_list_customersB | List all customers with optional pagination |
| bridge_create_walletA | Create a custodial wallet for a customer on a specific blockchain |
| bridge_get_walletC | Get a wallet by ID |
| bridge_list_walletsA | List all wallets for a customer |
| bridge_create_virtual_accountB | Create a virtual account (fiat deposit address) that auto-converts to stablecoins |
| bridge_get_virtual_accountA | Get a virtual account by ID |
| bridge_list_virtual_accountsA | List all virtual accounts for a customer |
| bridge_create_transferC | Create a transfer to move money (fiat-to-crypto, crypto-to-fiat, or crypto-to-crypto) |
| bridge_get_transferB | Get a transfer by ID |
| bridge_list_transfersB | List transfers with optional filtering by customer |
| bridge_create_external_accountB | Link an external bank account to a customer for payouts |
| bridge_get_external_accountA | Get an external account by ID |
| bridge_list_external_accountsA | List all external accounts for a customer |
| bridge_create_webhookA | Create a webhook endpoint to receive Bridge events |
| bridge_list_webhooksA | List all webhook endpoints |
| bridge_get_exchange_ratesA | Get current exchange rates between currencies |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action (create/get/list per entity). There is no overlap between customers, wallets, virtual accounts, transfers, external accounts, webhooks, and exchange rates, making selection unambiguous.
All tools follow a consistent bridge_verb_noun pattern. Verbs are limited to create, get, and list, and nouns are consistently singular for get/create and plural for list operations, except for exchange_rates which is naturally plural.
With 18 tools, the server is slightly above the typical 3-15 range but each tool corresponds to a necessary operation across seven distinct resource types. The count is justified for a payment-focused API, though it feels a bit heavy.
Core create/get/list operations are covered for most resources, but update and delete actions are missing across the board. Notably, webhooks only have create and list, lacking get and delete. These gaps could hinder full lifecycle management for an agent.