MCP server for Klever blockchain smart contract development
MCP Klever Vm MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Klever Vm directly instead of describing what you should do. MCP server for Klever blockchain smart contract development.
A Model Context Protocol (MCP) server tailored for Klever blockchain smart contract development. This server maintains and serves contextual knowledge including code patterns, best practices, and runtime behavior for developers working with the Klever VM SDK.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once MCP Klever Vm is connected, these are the calls the assistant has available:
query_context — Search for relevant Klever development contextadd_context — Add new context to the knowledge baseget_context — Retrieve specific context by IDfind_similar — Find contexts similar to a given contextget_knowledge_stats — Get statistics about the knowledge baseinit_klever_project — Initialize a new Klever smart contract project with helper scriptsenhance_with_context — Automatically enhance queries with relevant Klever VM contextKoperator — Complete CLI reference with argument encodingKSC — Build commands and project setupCursor — The Cursor tool exposed by this serverYou will need one environment variable: REDIS_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Klever Vm's toolset — query_context, add_context, get_context and 7 more — is a fair guide to whether it matches your workflow. It is maintained by klever-io; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Klever Vm's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| query_context | Search for relevant Klever development context |
| add_context | Add new context to the knowledge base |
| get_context | Retrieve specific context by ID |
| find_similar | Find contexts similar to a given context |
| get_knowledge_stats | Get statistics about the knowledge base |
| init_klever_project | Initialize a new Klever smart contract project with helper scripts |
| enhance_with_context | Automatically enhance queries with relevant Klever VM context |
| Koperator | Complete CLI reference with argument encoding |
| KSC | Build commands and project setup |
| Cursor | The Cursor tool exposed by this server. |
{
"mcpServers": {
"klever-vm": {
"command": "npx",
"args": ["-y", "@klever/mcp-server"],
"env": {
"REDIS_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| REDIS_URL | Endpoint or connection string the server talks to. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.