
fireblocks/fireblocks-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
A Model Context Protocol (MCP) server implementation for the Fireblocks API, enabling AI assistants to interact with Fireblocks services through a standardized protocol.
概要
A Model Context Protocol (MCP) server implementation for the Fireblocks API, enabling AI assistants to interact with Fireblocks services through a standardized protocol. This MCP server provides secure access to Fireblocks functionality, allowing AI assistants to: - Query and create transactions - Retrieve and manage vault accounts and assets - Access exchange account information - Query network connections and policies - Query blockchain information and whitelisted IP addresses - Query external and internal wallets - Query and filter workspace users To get started, you'll need a and its corresponding . 1. Follow the Fireblocks guide on creating an API key. 🔒 Security Note: When configuring an API user for the MCP server, it is critical to grant only the minimum permissions required for its specific tasks. For example, for read-only tasks like viewing transaction history, the "Viewer" role is the most secure option.
README
以下は原文 README の抜粋です。原文を見る。
Fireblocks MCP Server
A Model Context Protocol (MCP) server implementation for the Fireblocks API, enabling AI assistants to interact with Fireblocks services through a standardized protocol.
Overview
This MCP server provides secure access to Fireblocks functionality, allowing AI assistants to:
- Query and create transactions
- Retrieve and manage vault accounts and assets
- Access exchange account information
- Query network connections and policies
- Query blockchain information and whitelisted IP addresses
- Query external and internal wallets
- Query and filter workspace users
Prerequisites
Node.js (v18 or higher) - Download here
Installation
Step 1: Create an API key
To get started, you’ll need a Fireblocks API Key and its corresponding secret key file.
- Follow the Fireblocks guide on creating an API key.
🔒 Security Note: When configuring an API user for the MCP server, it is critical to grant only the minimum permissions required for its specific tasks. For example, for read-only tasks like viewing transaction history, the “Viewer” role is the most secure option. For a detailed guide on user roles, please refer to the best practices for choosing user roles.
- Once created, securely store both the API Key and the secret key file (e.g.,
fireblocks-secret.key). You will need both for the next steps.
Step 2: Configure your MCP Client
For Claude Desktop
- Open Claude Desktop.
- Go to Settings → Developer → Edit Config to open the
claude_desktop_config.jsonfile. - Add a new server with this configuration:
{
"mcpServers": {
"fireblocks": {
"command": "npx",
"args": ["@fireblocks/mcp-server"],
"env": {
"FIREBLOCKS_API_KEY": "your-api-key",
"FIREBLOCKS_PRIVATE_KEY_PATH": "your-fireblocks-api-secret-key-filepath",
"ENABLE_WRITE_OPERATIONS": "false",
"FIREBLOCKS_API_BASE_URL": "https://api.fireblocks.io/v1"
}
}
}
}
For Cursor
- Open Cursor.
- Go to Settings → Cursor Settings → Tools & Integrations.
- Select MCP Tools and click Add Custom MCP to open the
mcp.jsonfile. - Add a new server with this configuration:
{
"mcpServers": {
"fireblocks": {
"command": "npx",
"args": ["@fireblocks/mcp-server"],
"env": {
"FIREBLOCKS_API_KEY": "your-api-key",
"FIREBLOCKS_PRIVATE_KEY_PATH": "your-fireblocks-api-secret-key-filepath",
インストール
npx @fireblocks/mcp-server設定
{
"mcpServers": {
"fireblocks": {
"command": "npx",
"args": ["@fireblocks/mcp-server"],
"env": {
"FIREBLOCKS_API_KEY": "your-api-key",
"FIREBLOCKS_PRIVATE_KEY_PATH": "your-fireblocks-api-secret-key-filepath",
"ENABLE_WRITE_OPERATIONS": "false",
"FIREBLOCKS_API_BASE_URL": "https://api.fireblocks.io/v1"
}
}
}
}