Summary

It knows Klever's own conventions, and it never asks for your key.

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.

What it is

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.

What you get

search_documentation answers "how do I…" questions with markdown, titles and code snippets; query_context is the structured form with filters on type, tags and contract type
get_context fetches one entry in full, find_similar walks to related patterns, and get_knowledge_stats shows what the knowledge base actually contains
enhance_with_context takes a plain question, pulls the Klever-specific material behind it, and hands back the query with that context attached
add_context saves your own code examples, best practices or security tips into the store for later retrieval
analyze_contract checks Rust source for the mistakes that bite Klever contracts: missing imports, a missing #[klever_sc::contract] macro, missing endpoint annotations, payable handlers that never use call_value, storage mapper problems
Chain reads: get_balance for KLV or a KDA asset, get_account for nonce, frozen balance, allowance and permissions, get_asset_info for supply, roles and permissions, get_transaction, get_block and list_validators
query_sc runs a read-only view call against a deployed contract, with base64 arguments and results
Unsigned transactions built for you to sign elsewhere: send_transfer, deploy_sc from a wasm path or hex, invoke_sc for state-changing endpoints, and freeze_klv for energy and staking
Project scaffolding: init_klever_project creates the Rust project through ksc with build, deploy, upgrade, query, test and interact scripts, and add_helper_scripts adds those scripts to a project that already exists
check_sdk_status reports which SDK components are installed and at what version, and install_klever_sdk fetches them into ~/klever-sdk/ on macOS or Linux

Requirements

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.

Setup effort

One command — npx -y @klever/mcp-server