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
Available Tools
9 toolsadd_helper_scriptsTry in Inspector
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_contractTry in Inspector
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_contextTry in Inspector
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_similarTry in Inspector
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_contextTry in Inspector
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_statsTry in Inspector
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 | |||
init_klever_projectTry in Inspector
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 |
query_contextTry in Inspector
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. |
search_documentationTry in Inspector
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. |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- 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
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.