Kilawatt Cloud MCP Server
Model Context Protocol (MCP) server for requesting GPU compute capacity from Kilawatt Cloud, with account-based and x402 payment options.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
KILAWATT_API_KEY=<secret> KILAWATT_BASE_URL=<value> KILAWATT_SITE_URL=<value> KILAWATT_X402_PRIVATE_KEY=<secret> KILAWATT_X402_MAX_USD_PER_JOB=<value> KILAWATT_X402_MAX_USD_PER_SESSION=<value> KILAWATT_X402_URL=<value> claude mcp add io.github.kilawattcloud-kilawatt-mcp-server -- npx -y kilawatt-mcp-server@0.3.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.kilawattcloud-kilawatt-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "KILAWATT_API_KEY": "<secret>", "KILAWATT_BASE_URL": "<value>", "KILAWATT_SITE_URL": "<value>", "KILAWATT_X402_PRIVATE_KEY": "<secret>", "KILAWATT_X402_MAX_USD_PER_JOB": "<value>", "KILAWATT_X402_MAX_USD_PER_SESSION": "<value>", "KILAWATT_X402_URL": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดThis server calls the real Kilawatt gateways. Every response is an actual HTTP result from the Kilawatt public API or the x402 endpoint. There are no fabricated responses.
All examples are quote-only. See examples/README.md.
Client setup steps are in docs/clients.md.
The default endpoint is Kilawatt Cloud's gateway: https://www.kilawattcloud.dev/api/public/v1. Change it with the KILAWATT_BASE_URL environment variable.
Install and run via npx:
npx -y kilawatt-mcp-server
Set your Kilawatt API key to use deploy_gpu_node. It is not required to start the server or use the x402 tools:
export KILAWATT_API_KEY=kw_live_YOUR_KEY_HERE
The API key must start with kw_live_. API keys are issued through your Kilawatt Cloud account. Contact [email protected] for assistance if you don't have access to generate keys yet.
Add this configuration to your MCP client settings:
{
"mcpServers": {
"kilawatt": {
"command": "npx",
"args": ["-y", "kilawatt-mcp-server"],
"env": {
"KILAWATT_API_KEY": "kw_live_YOUR_KEY_HERE"
}
}
}
}
Replace kw_live_YOUR_KEY_HERE with your Kilawatt API key when using deploy_gpu_node. For x402-only use, omit KILAWATT_API_KEY.
Using goose? See GOOSE.md.
Start the MCP server:
npm start
Or directly:
node index.js
The server listens on stdio for MCP requests from your agent.
The server exposes four tools: deploy_gpu_node, x402_quote, x402_run_job and x402_job_status.
deploy_gpu_nodeProvision real GPU compute on Kilawatt Cloud. This starts an actual machine and charges the caller's Kilawatt wallet. Set dry_run: true to check pricing and routing without provisioning or charging. Requires KILAWATT_API_KEY.
{
"name": "deploy_gpu_node",
"arguments": { "card_count": 2, "duration_seconds": 1800, "dry_run": true }
}
x402_quoteGet the current price and Base USDC payment details for a GPU job without paying.
The published input schema states a maximum of 16 for card_count. The tighter per-GPU limits above are enforced in code when the call is made.
x402_run_jobQuote and pay for one GPU job in Base USDC. Takes the same parameters as x402_quote, plus:
x402_job_statusGet the status of a job created through x402, using the API key saved locally by x402_run_job.
deploy_gpu_node and the x402 toolsgpu_type is free text (up to 64 characters) in deploy_gpu_node but a fixed list in the x402 tools.card_count allows up to 64 in deploy_gpu_node but at most 16 (less for some GPUs) in the x402 tools.duration_seconds allows 1 to 86400 in deploy_gpu_node but 60 to 86400 in the x402 tools.deploy_gpu_node defaults routing_policy to lowest_cost; the x402 tools send no routing policy unless you set one.Tool results are formatted from the real HTTP response returned by the Kilawatt gateway.
The x402 tools let you request capacity with Base USDC without a Kilawatt account or API key. Spend caps are enforced locally.
The server must be able to read the following environment variables when you use x402 payments:
The returned API key is stored at ~/.config/kilawatt/x402-api-key with restrictive file permissions. It is never shown in tool output. Existing deploy_gpu_node still requires KILAWATT_API_KEY.
Use a separate small wallet for x402, and keep its private key out of prompts and shared configuration. The payer does not need ETH; the facilitator submits the transaction.
For x402 users: Check that your Base wallet has enough USDC and that your spend caps allow the amount.
All errors are descriptive and indicate whether anything was provisioned or charged. Common scenarios:
card_count > 64). Fix and retry.gpu_type or smaller card_count.MIT
Kilawatt Cloud MCP server: request GPU compute with account or x402 payments.
{ "mcpServers": { "io.github.kilawattcloud-kilawatt-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "KILAWATT_API_KEY": "<secret>", "KILAWATT_BASE_URL": "<value>", "KILAWATT_SITE_URL": "<value>", "KILAWATT_X402_PRIVATE_KEY": "<secret>", "KILAWATT_X402_MAX_USD_PER_JOB": "<value>", "KILAWATT_X402_MAX_USD_PER_SESSION": "<value>", "KILAWATT_X402_URL": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: KILAWATT_API_KEY, KILAWATT_BASE_URL, KILAWATT_SITE_URL, KILAWATT_X402_PRIVATE_KEY, KILAWATT_X402_MAX_USD_PER_JOB, KILAWATT_X402_MAX_USD_PER_SESSION, KILAWATT_X402_URL
Kilawatt ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Kilawatt Cloud MCP server: request GPU compute with account or x402 payments.