Server Details
MCP server for Klever blockchain smart contract development.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- klever-io/mcp-klever-vm
- GitHub Stars
- 3
See and control every tool call
Available Tools
16 toolsadd_helper_scriptsInspect
Add 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). NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.
| Name | Required | Description | Default |
|---|---|---|---|
| contractName | No | The contract name to embed in scripts (e.g. "my-token"). If omitted, auto-detected from the `name` field in Cargo.toml. |
analyze_contractInspect
Analyze 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.
| Name | Required | Description | Default |
|---|---|---|---|
| sourceCode | Yes | The full Rust source code of the Klever smart contract to analyze. Must be valid Rust code using klever_sc imports. | |
| contractName | No | Human-readable name for the contract (used in output labeling). Defaults to "contract" if omitted. |
enhance_with_contextInspect
Augment 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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The user's natural-language question or prompt to enhance (e.g. "How do I handle KLV payments in my contract?"). | |
| autoInclude | No | When true (default), automatically appends the most relevant knowledge base entries to the response. Set to false to only return metadata without injecting context. |
find_similarInspect
Find 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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The context ID to find similar entries for. Obtain from query_context or get_context results. | |
| limit | No | Maximum number of similar entries to return. Typical range is 1-20; higher values may be slower. Default: 5. |
get_accountInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Klever address (klv1... bech32 format). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_asset_infoInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
| assetId | Yes | Asset identifier (e.g. "KLV", "KFI", "USDT-A1B2", "MYNFT-XY78"). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_balanceInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Klever address (klv1... bech32 format). | |
| assetId | No | Optional KDA token ID (e.g. "USDT-A1B2", "LPKLVKFI-3I0N"). Omit for KLV balance. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_blockInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
| nonce | No | Block number (nonce). Omit to get the latest block. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
get_contextInspect
Retrieve 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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The unique context ID (UUID format). Obtain IDs from query_context or find_similar results. |
get_knowledge_statsInspect
Get 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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_transactionInspect
Get transaction details by hash from the Klever blockchain. Returns sender, receiver, status, block info, contracts, and receipts. Uses the API proxy for indexed data.
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | Transaction hash (hex string). | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
init_klever_projectInspect
Scaffold 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. NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The contract project name in kebab-case (e.g. "my-token", "nft-marketplace"). Used as the Cargo package name and directory name. | |
| noMove | No | When true, keeps the project in the SDK output directory instead of moving it to the current working directory. Default: false. | |
| template | No | Project template to scaffold from. "empty" creates a blank contract with just an init function. "adder" creates a simple counter example. Default: "empty". | empty |
list_validatorsInspect
List active validators on the Klever blockchain network. Returns validator addresses, names, commission rates, delegation info, and staking amounts.
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). |
query_contextInspect
Search 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.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Filter by tags (e.g. ["storage", "mapper"], ["tokens", "KLV"], ["events"]). Tags are matched with OR logic — any matching tag includes the entry. | |
| limit | No | Maximum number of results to return (1-100). Default: 10. | |
| query | No | Free-text search query. Use Klever-specific terms for best results (e.g. "storage mapper SingleValueMapper", "payable endpoint KLV", "deploy contract testnet"). | |
| types | No | Filter results by context type. Omit to search all types. Common combinations: ["code_example", "documentation"] for learning, ["error_pattern"] for debugging, ["security_tip", "best_practice"] for reviews. | |
| offset | No | Number of results to skip for pagination. Use with limit to page through results. Default: 0. | |
| contractType | No | Filter by contract type (e.g. "token", "nft", "defi", "dao"). Only returns entries tagged for this contract category. |
query_scInspect
Execute 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.
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | Optional base64-encoded arguments. For addresses, encode the hex-decoded bech32 bytes. For numbers, use big-endian byte encoding. | |
| caller | No | Optional caller address (klv1... bech32 format). Some view functions use the caller to look up address-keyed storage mappers. | |
| network | No | Network to query. Options: "mainnet", "testnet", "devnet", "local". Defaults to server default (mainnet). | |
| funcName | Yes | Function name to call (must be a #[view] function on the contract). | |
| scAddress | Yes | Smart contract address (klv1... bech32 format). |
search_documentationInspect
Search 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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query in natural language (e.g. "how to use storage mappers", "deploy contract to testnet", "handle KDA token transfers"). | |
| category | No | Narrow results to a specific knowledge category. Available: core, storage, events, tokens, modules, tools, scripts, examples, errors, best-practices, documentation. |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.