Safe MCP Server

What is Safe MCP Server?

Safe MCP Server is an MCP (Model Context Protocol) server for interacting with Safe (formerly Gnosis Safe) smart contract wallets. It allows AI agents to query transactions, get multisig details, and decode transaction data via the Safe Transaction API.

How to use Safe MCP Server?

Install with npm install, build with npm run build, and start with npm start. No configuration is required; the server uses the Safe Transaction API mainnet endpoint by default. Optionally, set the SAFE_API_URL environment variable to use a different endpoint (e.g., for testnets).

Key features of Safe MCP Server

• Query Safe transactions for any Safe address
• Get multisig transaction details
• Decode transaction data via Safe API
• Safe API integration with default mainnet endpoint
• Configurable API URL via environment variable

Use cases of Safe MCP Server

• Allow an AI assistant to check pending Safe multisig transactions
• Decode raw transaction data during wallet analysis
• Retrieve transaction history for a given Safe address
• Support testnet workflows by switching the API endpoint

FAQ from Safe MCP Server

Does Safe MCP Server require configuration?

No. It uses the Safe Transaction API mainnet endpoint by default. You can optionally change the endpoint via the SAFE_API_URL environment variable.

What tools does Safe MCP Server provide?

It provides three tools: getSafeTransactions, getMultisigTransaction, and decodeTransactionData.

Can I use Safe MCP Server with testnets?

Yes. Set the SAFE_API_URL environment variable to a testnet endpoint (e.g., Goerli) before starting the server.

How does the server determine the Safe address?

The Safe address is determined by the LLM at runtime based on the context of the conversation, not pre-configured.

What are the runtime dependencies?

Node.js and npm are required. Run npm install to install the package.