Akash Network MCP for AI. Manage decentralized GPU clusters from natural language.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Akash Network MCP connects your AI client directly to decentralized cloud resources. You can create and manage compute deployments using standard SDL manifests, secure GPU capacity through provider bids and leases, and monitor escrow funds—all programmatically.
It lets you run high-performance AI workloads without being locked into a single centralized vendor.
What your AI can do
Add deposit
Adds specified USD funds directly to a deployment's escrow account.
Close deployment
Stops and removes an active compute deployment, releasing associated resources.
Create deployment
Launches a new workload by processing a provided Stack Definition Language (SDL) manifest.
Create new, fully defined compute deployments by referencing a standard Stack Definition Language (SDL) manifest.
Poll for bids from network providers and finalize the acquisition of resources by creating formal leases.
Monitor deployment escrow balances and add USD deposits to ensure continuous service operation.
Enable auto top-up settings so your decentralized infrastructure scales automatically as usage increases.
Retrieve full details on active deployments, leases, and provider information to maintain operational visibility.
Ask an AI about this
Waiting for input…
Akash Network (Decentralized GPU & Cloud API) with 13 Tools
These tools let you control every aspect of a decentralized cloud deployment lifecycle: from listing providers and checking bids, to creating deployments and managing funds.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Akash Network (Decentralized GPU & Cloud API) on VinkiusAdd Deposit
Adds specified USD funds directly to a deployment's escrow account.
Close Deployment
Stops and removes an active compute deployment, releasing associated resources.
Create Deployment
Launches a new workload by processing a provided Stack Definition Language (SDL)...
Create Lease
Accepts provider bids and formally creates a lease to guarantee compute resources...
Enable Auto Top Up
Configures the deployment settings so that services can automatically replenish...
Get Deployment Settings
Fetches the current auto-top-up and billing configuration rules for an active deployment.
Get Deployment
Retrieves complete status details for a specific, existing workload or deployment.
Get Provider
Gets specific technical details about a known cloud provider within the network.
List Bids
Checks the network to see what bids are available from providers for your current...
List Deployments
Retrieves a list of all currently active and paused deployments under your account.
List Providers
Lists every available provider node connected to the Akash network.
Update Deployment Settings
Modifies the non-core operational settings, such as auto top-up policies or billing limits.
Update Deployment
Makes changes directly to an active deployment's core configuration parameters.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Akash Network (Decentralized GPU & Cloud API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Akash Network. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually managing cloud deployments is a constant headache.
Today, provisioning high-end GPU clusters means logging into several separate provider dashboards. You have to copy-paste manifests, manually check the escrow balance every few hours, and if your usage spikes unexpectedly, you're stuck clicking through billing tabs just to add funds or adjust scaling limits.
With this MCP, those manual steps disappear. Your agent takes over. You define your needs once, and we handle the coordination—securing bids with `list_bids`, creating leases with `create_lease`, and keeping the lights on by managing deposits through `add_deposit`. It's pure programmatic control.
Control Your Resources With The `create_deployment` Tool
Before, starting a new workload meant hours of manual configuration: generating the correct manifest file, ensuring all dependencies were met, and then manually submitting that data to the provider's API endpoint. It was slow, error-prone work.
Now, you simply prompt your agent with the required details. The `create_deployment` tool handles the entire submission process using the SDL manifest, getting you from concept to active cluster in minutes. You just tell it what you need; it gets it running.
What your AI can actually do with this
Running demanding applications used to mean dealing with opaque dashboards and complex billing cycles from massive cloud providers. You'd spend time clicking through menus just to provision or check resource status. This MCP changes that. Your agent can now orchestrate the entire lifecycle of your compute cluster using natural language commands.
You write a manifest, tell your AI client to deploy it, and watch the resources spin up across a decentralized network of providers. You'll manage everything from monitoring escrow balances for unexpected costs to creating leases when you need guaranteed capacity. Because this MCP is hosted on Vinkius, you connect once through your preferred agent—whether that’s in VS Code or Cursor—and gain immediate access to the entire catalog of APIs needed for advanced infrastructure management.
019e5cf9-6004-730c-a8e5-cb8d26c93f85 Here's how it actually works
The bottom line is that you manage complex infrastructure provisioning through conversation, not clicking through dashboards.
Subscribe to this MCP in Vinkius and provide your Akash API Key.
Direct your AI client (like Cursor or Claude) to execute a deployment task, providing the necessary SDL manifest details.
Your agent interacts with the network endpoints, creating resources, securing leases, and updating status via simple chat prompts.
Who is this actually for?
This MCP targets the DevOps engineer who hates manual click-ops and the AI researcher needing massive GPU compute without vendor lock-in. If your job involves managing persistent, highly technical infrastructure in a decentralized way, this is for you.
Manages full deployment lifecycles, using the MCP to initiate deployments with create_deployment and ensure clean tear-down via close_deployment.
Spins up specialized GPU resources for model training or inference by polling bids using list_bids and securing capacity with a lease.
Builds dApps that require persistent, decentralized hosting. They use the MCP to monitor balances via get_deployment_settings and fund services using add_deposit.
What Changes When You Connect
You avoid manual resource management. Instead of jumping between billing and compute dashboards, you can use get_deployment or list_deployments to check status instantly via your agent.
Resource bidding is simple. You don't need to wait for emails; just run list_bids to poll available provider costs and decide when to commit resources with create_lease.
Billing anxiety vanishes. By using get_deployment_settings, you can check the auto-top-up status, or use add_deposit if you know your service's run time is about to expire.
You maintain control over infrastructure changes. Need to adjust how scaling works? Use update_deployment_settings instead of touching core deployment logic with update_deployment.
It simplifies complex deployments. You can initiate an entire workload using the create_deployment tool just by giving it your SDL manifest, bypassing manual CLI setup.
See it in action
Scaling a Live AI Model
An AI researcher needs their model to run 24/7. They first check the current resource limits using get_deployment_settings. When they see usage climbing, they instruct their agent to use enable_auto_top_up and then monitor the continuous funding via add_deposit.
Quickly Testing Provider Availability
A developer is building a new service. They start by running list_providers to see who's online, then use get_provider on a specific name to verify its hardware type before drafting the create_deployment manifest.
Shutting Down Test Clusters
A Web3 developer finishes testing a temporary dApp. Instead of logging into three different consoles, they tell their agent to run close_deployment, which cleans up all associated resources and prevents unexpected charges.
Mid-Cycle Configuration Changes
A team needs to shift resource allocation for a running service. They use the MCP to call update_deployment_settings first, ensuring they change the scaling rules before calling update_deployment to commit the final changes.
The honest tradeoffs
Trying to update resources without checking funding.
The user assumes their deployment is funded and runs update_deployment. The system fails mid-process because the escrow balance dropped below the necessary threshold, causing downtime.
Always check the status first. Run get_deployment or list_deployments to verify current health, and if funds are low, run add_deposit before attempting any updates.
Confusing core changes with policy changes.
The user wants to change the billing schedule and incorrectly calls update_deployment. This risks modifying fundamental resource parameters instead of just changing a setting.
If you are only adjusting policies (like auto-top-up), use update_deployment_settings. Use update_deployment only when you must fundamentally change the workload manifest itself.
Leaving clusters running indefinitely.
A temporary test cluster is forgotten in the network, continuing to incur small charges because no one manually terminated it.
When testing is complete, always use close_deployment immediately. This ensures all associated resources are released and prevents billing surprises.
When It Fits, When It Doesn't
Use this MCP if your workflow requires managing the full lifecycle of high-performance infrastructure—from initial provisioning (create_deployment) through continuous scaling and funding (using add_deposit or enable_auto_top_up), to eventual teardown (close_deployment). It's perfect for AI researchers and DevOps teams who need programmatic control over resources. Don't use this if you only need a single, quick status check; in that case, simply calling list_deployments is sufficient without the complexity of managing deposits or leases.
This toolset is designed to handle the state of your compute environment. If you are dealing with stateless operations or general data retrieval outside of resource management (e.g., pulling a single user record), this MCP isn't for you; look into other data-focused tools in the Vinkius catalog.
Questions you might have
How do I keep my deployment funded without manually topping up? (add_deposit) +
You use the enable_auto_top_up tool to set the policy. This allows your deployed service to automatically replenish its funds when the escrow balance dips below a defined threshold.
What is the best way to check available GPU power? (list_bids) +
You run list_bids on your deployment. This polls the network and shows you real-time pricing from multiple providers, letting you compare costs before committing to a lease.
Can I update my cluster settings after it's running? (update_deployment_settings) +
Yep. Use update_deployment_settings for changes like adjusting the auto-top-up limits or changing billing rules without altering the core definition of your workload.
I finished testing, how do I stop and clean up my resources? (close_deployment) +
Always use close_deployment. This safely terminates the active workload, releases all associated provider resources, and ensures any remaining escrow balance is returned to your account.
What does `list_providers` show me about network availability? +
It returns a list of all available compute providers on the Akash Network. You can use this to compare specs, check geographic locations, and assess current capacity before you decide where to deploy your workload.
What information must I provide when I use `create_deployment`? +
You need a full Stack Definition Language (SDL) manifest. This file is essential because it defines the entire resource stack, including replicas and hardware requirements for your application.
If I run `get_deployment`, what details can I retrieve about a live workload? +
You get comprehensive data on the deployment's current status, total resource usage, and active lease information. This is critical for monitoring high availability in production.
How do I change an active workload using `update_deployment`? +
Simply specify the existing deployment identifier along with the new settings you want to apply. The MCP then manages updating those resources without needing a full recreation of the stack.
How do I check for available provider bids after creating a deployment? +
Use the list_bids tool with your deployment's DSEQ. It typically takes 30-60 seconds for providers to submit bids for your workload.
Can I update a running deployment with a new SDL manifest? +
Yes! Use the update_deployment tool. Provide the existing DSEQ and your revised SDL string to apply changes to your active resources.
How do I prevent my deployment from closing due to insufficient funds? +
You can use add_deposit to manually add USD to the escrow, or use enable_auto_top_up to configure automatic funding based on your deployment's needs.
We've already built the connector for Akash Network. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.