Get the FREE Ultimate OpenClaw Setup Guide →

safe

An MCP server implementation for interacting with Safe (Gnosis Safe) smart contract wallets

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio 5ajaki-safe-mcp-server node path/to/server.js \
  --env SAFE_API_URL="https://safe-transaction-mainnet.safe.global/api/v1"

How to use

This MCP server provides an integration layer for Safe (formerly Gnosis Safe) smart contract wallets. It exposes tools to query Safe transactions, fetch multisig transaction details, and decode transaction data via the Safe API. The server can be driven by an LLM to look up transactions for a given Safe address, retrieve specific multisig transactions by hash, and decode low-level transaction data to human-readable actions. By default, it points to the Safe Transaction API mainnet endpoint, so most queries will resolve against live Safe wallets on mainnet. To use, run the server and invoke the available tools with the required parameters (for example, a Safe address, a transaction hash, or raw transaction data).

How to install

Prerequisites:

  • Node.js (recommended LTS) and npm installed on your system

Step-by-step:

  1. Install dependencies npm install

  2. Build the project (if applicable) npm run build

  3. Start the server npm start

Notes:

  • The server may run without additional configuration, using the Safe Transaction API mainnet endpoint by default. If you need to point to a different API, set the SAFE_API_URL environment variable before starting the server, e.g.: SAFE_API_URL=https://safe-transaction-goerli.safe.global/api/v1 npm start

Additional notes

Tips:

  • By default, the server uses the Safe Transaction API mainnet endpoint. If you operate on testnets, set SAFE_API_URL to the appropriate endpoint before starting the server.
  • The tools exposed include: getSafeTransactions (lists transactions for a Safe address), getMultisigTransaction (fetches details of a specific multisig transaction by hash), and decodeTransactionData (decodes raw tx data via the Safe API).
  • If you see rate limits or API errors, consider adding a custom SAFE_API_URL to point to a different Safe API deployment or add rate-limiting handling in your client.
  • The LLM should supply a Safe address when calling getSafeTransactions; ensure you pass a valid address in checksummed form.
  • Ensure network access from your deployment environment so the server can reach the Safe Transaction API.

Related MCP Servers

Sponsor this space

Reach thousands of developers