GetAccountAddrToolLABSCO SUMMARY
Wallet handling and the deployment lifecycle for Akash, in a project its authors call unfinished.
The tools follow the path a deployment actually takes: write the SDL, create the deployment, look at the bids, add funds, close it, with wallet and certificate setup done for you. The authors say directly that not all tools are available yet and more are being added, so treat the current set as the floor rather than the ceiling.
What it is
A TypeScript server for the Akash Network that handles wallet and certificate setup, then exposes deployment, bid and SDL operations as typed tools.
What you get
- A deployment created from an SDL, and closed again when it is no longer needed (CreateDeploymentTool, CloseDeploymentTool)
- A deployment's current state read back (GetDeploymentTool)
- The bids providers have placed against your deployment (GetBidsTool)
- One SDL fetched, or the available ones listed (GetSDLTool, GetSDLsTool)
- Your account address, your balances, and funds added to a deployment (GetAccountAddrTool, GetBalancesTool, AddFundsTool)
- Wallet authentication, client initialization and certificate management handled by the server
Requirements
Node.js v18 or later and an Akash wallet: a mnemonic or a hex-encoded private key. The repository is cloned and built with npm run build, then the built dist/index.js is pointed at from your client config.
Setup effort
Build from source — git clone https://github.com/akash-network/mcp.git
USE CASES
01
Getting an app onto Akash without leaving the conversation
Fetch the SDL you want, then create the deployment from it.
02
Choosing which provider to run on
Read the bids placed against your deployment and compare them before you lease.
03
Checking you can afford to run before you start
Read your account address and balances first, so a deployment does not stall on funds.
04
Topping up a deployment before it lapses
Add funds to the running deployment rather than recreating it.
05
Shutting down what you no longer need
Check the deployment state, then close it so it stops drawing funds.
13 tools
Listed in project docs. Your client may show a different list.
GetBalancesToolGetBidsToolCreateDeploymentToolGetDeploymentToolCloseDeploymentToolAddFundsToolGetSDLsToolGetSDLToolSendManifestToolCreateLeaseToolGetServicesToolUpdateDeploymentToolBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation. The project says it is still under development, so not every documented tool may register. Six tools spend real AKT from your configured wallet: CreateDeploymentTool, UpdateDeploymentTool, CloseDeploymentTool, AddFundsTool, CreateLeaseTool and SendManifestTool.
Requires
- Node.js
- AKASH_MNEMONIC or AKASH_PRIVATE_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/akash-network/mcp.git
cd mcp
npm install
npm run buildAdd the mcpServers block below to claude_desktop_config.json or .cursor/mcp.json, pointing args at the built dist/index.js and supplying AKASH_MNEMONIC (or AKASH_PRIVATE_KEY)
MCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"Akash": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DIST_INDEX_JS>"
],
"env": {
"AKASH_MNEMONIC": "<YOUR_AKASH_MNEMONIC>",
"AKASH_RPC_URL": "https://rpc.akashnet.net:443"
}
}
}
}To use a private key instead of a mnemonic, use an "AKASH_PRIVATE_KEY" line, set to your 64-character hex string, instead of the AKASH_MNEMONIC line; set one or the other. AKASH_RPC_URL is optional and defaults to https://rpc.akashnet.net:443.
