MCP Server

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Akash MCP Server.

What you get

This project is still under development and not all tools are available. We are working on adding more tools and improving the server. We are open to contributions! See CONTRIBUTING.md for more details.

This server provides a bridge between AI agents and the Akash Network, allowing AI models to deploy applications, create leases, manage deployments, and interact with other Akash services directly through typed tools. It implements the Model Context Protocol, making it compatible with various AI platforms and tools.

• Wallet and Client Management — Handles Akash wallet authentication and client initialization
• Certificate Management — Manages Akash certificates
• Tools for Akash Interaction —
• Account address retrieval
• Deployment creation, querying, updating, and termination
• SDL (Stack Definition Language) operations

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

• GetAccountAddrTool — Retrieve your Akash account address
• GetBalancesTool — Get the AKT (uakt) and other balances for a given Akash account address
• GetBidsTool — Get bids for deployments
• CreateDeploymentTool — Create a new deployment on Akash Network
• GetDeploymentTool — Get deployment details including status, groups, and escrow account
• CloseDeploymentTool — Close/terminate a deployment on Akash Network
• AddFundsTool — Deposit additional AKT (uakt) into a deployment escrow account
• GetSDLsTool — Get a list of available SDLs (from awesome-akash repository)
• GetSDLTool — Get a specific SDL by name
• SendManifestTool — Send a manifest to a provider
• CreateLeaseTool — Create a lease with a provider
• GetServicesTool — Get information about active services

Configuration and credentials

You will need 3 environment variables: AKASH_MNEMONIC, AKASH_PRIVATE_KEY, AKASH_RPC_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v18 or later) - An Akash wallet (a mnemonic or a hex-encoded private key is required for interaction with Akash Network) - Basic knowledge of Akash Network

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — GetAccountAddrTool, GetBalancesTool, GetBidsTool and 10 more — is a fair guide to whether it matches your workflow. It is maintained by akash-network; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.