CONNECTION_UPDATELABSCO SUMMARY
The audit tool is the reason to install it.
Anyone can wire an assistant to a multisig; what is unusual here is a scoring pass that tells you whether the configuration is safe before you fund it — separation of INITIATE, EXECUTE and VOTE roles, threshold ratios against member counts, and time locks matched to what the account holds. Treat the numbers as a checklist, not a guarantee, and keep the signing key on hardware for anything that matters.
What it is
An MCP server for Squads multisig management on Solana. It covers the whole lifecycle: create or import a multisig, propose a transaction, collect approvals or rejections, execute or cancel, and move assets in and out of the vault. Private keys are stored locally and signing happens in your environment against Solana RPC directly, with no delegated signer in between.
What you get
- Set up and inspect:
CREATE_SQUADS_MULTISIG,IMPORT_SQUADS_MULTISIG,GET_MULTISIG_ACCOUNT, plusCONNECTION_UPDATEandSHOW_CONFIGto switch networks and see the current settings AUDIT_MULTISIG_SECURITY— score a multisig configuration out of 100 against 15+ risk factors, flagging concentrated permissions, thresholds that are too low and time locks that are too short, with findings graded Critical through Low and machine-readable JSON output- Proposal flow:
CREATE_PROPOSAL,APPROVE_PROPOSAL,REJECT_PROPOSAL,CANCEL_PROPOSAL,GET_PROPOSALandGET_PROPOSALS - Execution:
EXECUTE_CONFIG_TRANSACTIONfor configuration changes andEXECUTE_VAULT_TRANSACTIONfor vault transactions - Assets:
GET_ASSETSfor SOL and token balances in a vault,FUND_VAULTandTRANSFER_SOL_FROM_VAULT - Threshold and time-lock guidance built into the audit — 6+ members with a 4+ threshold for reserve and program-upgrade multisigs, 3+ members with a 2+ threshold for operations, and time locks of 3600 seconds for reserve, 600 for upgrades and 300 for operations
Requirements
A Solana wallet with a private key held locally — a hardware wallet is the recommendation for production use. Node.js v16 or higher; the package is squads-mcp (0.1.0 in package.json), installed with npm install squads-mcp and launched by pointing the client at node_modules/squads-mcp/dist/index.js. Solana CLI tools are optional. Every action requires explicit invocation; nothing runs on its own.
Setup effort
One command — npm install squads-mcp
USE CASES
01
Checking whether a multisig is set up safely
Score the configuration, read the graded findings, and fix concentrated permissions or missing time locks before funding it.
02
Moving a proposal through approval
Create the proposal, gather approvals from the members, and execute it once the threshold is met.
03
Seeing what a treasury holds
Read the SOL and token balances in the vault and the history of open proposals against it.
04
Testing on devnet before production
Switch the connection to a test network, rehearse the whole flow, then switch back.
17 tools
Listed in project docs. Your client may show a different list.
SHOW_CONFIGCREATE_SQUADS_MULTISIGIMPORT_SQUADS_MULTISIGGET_MULTISIG_ACCOUNTAUDIT_MULTISIG_SECURITYCREATE_PROPOSALAPPROVE_PROPOSALREJECT_PROPOSALCANCEL_PROPOSALGET_PROPOSALGET_PROPOSALSEXECUTE_CONFIG_TRANSACTIONEXECUTE_VAULT_TRANSACTIONGET_ASSETSFUND_VAULTTRANSFER_SOL_FROM_VAULTBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- node on PATH
- Node.js v16 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install squads-mcpMCP Clients
Claude Desktop
node_modules/squads-mcp/dist/index.js is relative to the folder where you ran npm install squads-mcp. Claude Desktop does not start the server from that folder, so write that folder's full path followed by /node_modules/squads-mcp/dist/index.js.
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"squads-mcp": {
"command": "node",
"args": [
"node_modules/squads-mcp/dist/index.js"
]
}
}
}
