MCP SERVER · OFFICIAL PROJECTWrite, analyse and deploy Klever smart contracts with the chain's own knowledge base at hand — and unsigned transactions you sign yourself.
LABSCO SUMMARY
The contract analyser checks for Klever-specific mistakes — a missing contract macro, an unannotated endpoint, a payable handler that ignores call_value — which a general Rust review will not catch, and the knowledge base means the patterns come from Klever's material rather than a model's recollection. The transaction design is the part to plan around: deploy, invoke, transfer and freeze all return unsigned transactions, so your client or wallet has to do the signing and broadcasting step.
A development server for Klever VM smart contracts, combining a searchable knowledge base of Klever patterns with chain reads and transaction building. It never handles private keys: anything that changes state comes back unsigned for you to sign.
No key handed to the server — it builds unsigned transactions and signing happens on your side, so the wallet stays where it is. Reads and the knowledge base need nothing at all. Two ways to connect: the hosted endpoint at https://mcp.klever.org/mcp over Streamable HTTP, or locally as @klever/mcp-server over stdio. The scaffolding and build tools need the Klever SDK — ksc, koperator and the VM library — which check_sdk_status reports on and install_klever_sdk will fetch for macOS or Linux. Every chain tool takes a network argument, so testnet and mainnet are a per-call choice.
One command — npx -y @klever/mcp-server
USE CASES
Ask the documentation how the thing is done, pull the matching example in full, and follow related patterns from there.
Run the source through the analyser, which looks for the Klever-specific omissions rather than general Rust issues.
Check the SDK is installed, install it if not, then scaffold the project with its build, deploy and test scripts.
Build the unsigned deployment from the wasm, sign and broadcast it yourself, then invoke an endpoint the same way.
Run a view call against the deployed contract and read the return data, no transaction involved.
Read an address's balance for KLV or a specific asset, then the full account state with frozen balance and permissions.
Save the pattern or the security note into the knowledge store, so the next question finds it.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_contextAdd a new knowledge entry to the Klever VM context store. Use this to save code examples, best practices, security tips, or documentation that can later be retrieved via query_context or search_documentation. Returns the generated ID of the new entry.
add_helper_scriptsAdd build, deploy, upgrade, query, test, and interact automation scripts to an existing Klever smart contract project. Creates a scripts/ directory with bash scripts and updates .gitignore. Run this from the project root directory (where Cargo.toml is located).
analyze_contractAnalyze Klever smart contract Rust source code for common issues. Checks for missing imports, missing #[klever_sc::contract] macro, missing endpoint annotations, payable handlers without call_value usage, storage mappers without #[storage_mapper], and missing event definitions. Returns findings with severity (error/warning/info) and links to relevant knowledge base entries.
check_sdk_statusCheck whether the Klever SDK is installed and report the status of each component. Returns JSON with installation state and versions for: ksc (smart contract compiler), koperator (blockchain CLI), VM library (libvmexeccapi), and wallet key file. Run this before init_klever_project or install_klever_sdk to verify prerequisites.
deploy_scBuild an unsigned smart contract deployment transaction for the Klever blockchain. Provide either wasmPath (preferred — reads the file server-side) or wasmHex. Returns the unsigned transaction for client-side signing. The MCP server NEVER handles private keys.
enhance_with_contextAugment a natural-language query with relevant Klever VM knowledge base context. Extracts Klever-specific keywords, finds matching entries, and returns the original query combined with relevant code examples and documentation in markdown. Use this to enrich a user prompt before answering Klever development questions.
find_similarFind knowledge base entries similar to a given entry by comparing tags and content. Returns related contexts ranked by similarity score. Useful for discovering related patterns, examples, or documentation after finding one relevant entry.
freeze_klvBuild an unsigned Freeze KLV transaction on the Klever blockchain. Freezing KLV provides energy/bandwidth for network operations and enables staking rewards. Returns the unsigned transaction for client-side signing.
get_accountGet full account details for a Klever blockchain address including nonce, balance, frozen balance, allowance, and permissions. Use this when you need comprehensive account state beyond just the balance.
get_asset_infoGet complete properties and configuration for any asset on the Klever blockchain (KLV, KFI, KDA tokens, NFT collections). Returns supply info, permissions (CanMint, CanBurn, etc.), roles, precision, and metadata. Note: string fields like ID, Name, Ticker are base64-encoded in the raw response.
get_balanceGet the KLV or KDA token balance for a Klever blockchain address. Returns the balance in the smallest unit (for KLV: 1 KLV = 1,000,000 units with 6 decimal places). Optionally specify an asset ID to query a specific KDA token balance instead of KLV.
get_blockGet block information from the Klever blockchain by nonce (block number). If no nonce is provided, returns the latest block. Returns hash, timestamp, proposer, number of transactions, and other block metadata.
get_contextRetrieve a single knowledge base entry by its unique ID. Returns the full entry including content, metadata, tags, and related context IDs. Use this after query_context or find_similar to get complete details for a specific entry.
get_knowledge_statsGet summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.
get_transactionGet transaction details by hash from the Klever blockchain. Returns sender, receiver, status, block info, contracts, and receipts. Uses the API proxy for indexed data.
init_klever_projectScaffold a new Klever smart contract project using the SDK. Creates the Rust project structure via ksc new and generates automation scripts (build, deploy, upgrade, query, test, interact). Requires Klever SDK installed at ~/klever-sdk/. Run check_sdk_status first to verify.
install_klever_sdkDownload and install Klever SDK tools to ~/klever-sdk/. Fetches the latest versions from the Klever CDN, installs binaries, and downloads required VM library dependencies. Supports macOS (arm64/amd64) and Linux. Run check_sdk_status first to see what is already installed.
invoke_scBuild an unsigned smart contract invocation transaction on the Klever blockchain. Calls a state-changing endpoint on a deployed contract. Returns the unsigned transaction for client-side signing. For read-only calls, use query_sc instead.
list_validatorsList active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.
query_contextSearch the Klever VM knowledge base for smart contract development context. Returns structured JSON with matching entries, scores, and pagination. Use this for precise filtering by type or tags; use search_documentation for human-readable "how do I..." answers.
query_scExecute a read-only query against a Klever smart contract (VM view call). Returns the contract function result as base64-encoded return data. Arguments must be base64-encoded. Use this to read contract state without modifying it.
search_documentationSearch Klever VM documentation and knowledge base. Returns human-readable markdown with titles, descriptions, and code snippets. Optimized for "how do I..." questions. Use this instead of query_context when you need formatted developer documentation.
send_transferBuild an unsigned KLV or KDA token transfer transaction on the Klever blockchain. Returns the unsigned transaction data and hash for client-side signing. The MCP server NEVER handles private keys — signing must be done externally.
BEFORE YOU INSTALL
23 tools when we connected. The hosted public endpoint exposes a read-only subset of five: query_context, get_context, find_similar, get_knowledge_stats and enhance_with_context.
CONTEXT COST
Rated by the size of the 23 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @klever/mcp-serverhttps://mcp.klever.org/mcpAdd this hosted endpoint to your MCP client.
claude mcp add klever-vm -- npx -y @klever/mcp-server{
"mcpServers": {
"klever-vm": {
"command": "npx",
"args": [
"-y",
"@klever/mcp-server"
]
}
}
}{
"servers": {
"klever-vm": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@klever/mcp-server"
]
}
}
}claude mcp add -t http klever-vm https://mcp.klever.org/mcp{
"inputs": [],
"servers": {
"klever-vm": {
"type": "http",
"url": "https://mcp.klever.org/mcp"
}
}
}Clone and build the server
# 1. Clone the repository
git clone https://github.com/klever-io/mcp-klever-vm.git
cd mcp-klever-vm
# 2. Install dependencies
pnpm install
# 3. Copy environment configuration
cp .env.example .env
# 4. Install Klever SDK tools (required for transactions)
chmod +x scripts/install-sdk.sh && ./scripts/install-sdk.sh
# 5. Build the project
pnpm run buildAdd this to your client configuration
{
"mcpServers": {
"klever-vm": {
"command": "node",
"args": [
"--experimental-vm-modules",
"<YOUR_PATH_TO_MCP_KLEVER_VM>/dist/index.js"
],
"env": {
"MODE": "mcp",
"STORAGE_TYPE": "memory"
}
}
}
}Clone and build the server
# 1. Clone the repository
git clone https://github.com/klever-io/mcp-klever-vm.git
cd mcp-klever-vm
# 2. Install dependencies
pnpm install
# 3. Copy environment configuration
cp .env.example .env
# 4. Install Klever SDK tools (required for transactions)
chmod +x scripts/install-sdk.sh && ./scripts/install-sdk.sh
# 5. Build the project
pnpm run buildAdd this to your client configuration
{
"inputs": [],
"servers": {
"klever-vm": {
"type": "stdio",
"command": "node",
"args": [
"--experimental-vm-modules",
"<YOUR_PATH_TO_MCP_KLEVER_VM>/dist/index.js"
],
"env": {
"MODE": "mcp",
"STORAGE_TYPE": "memory"
}
}
}
}MCP servers
subsquid-labs
ChainBench
nirholas
RockYuan