Mcp Klever Vm
Give your agent Klever VM smart-contract tooling so you can scaffold, inspect, and iterate on-chain logic without leaving the MCP client.
Overview
mcp-klever-vm is a MCP server for the Build phase that exposes Klever blockchain smart contract development tools to coding agents.
What is this MCP server?
- MCP server tailored to Klever blockchain smart contract development (v1.3.0)
- Remote streamable-http endpoint at https://mcp.klever.org/mcp
- Local stdio option via npm package @klever/mcp-server
- Dual transport lets you choose hosted remote or npm stdio in agent config
- Server version 1.3.0
- 1 remote streamable-http endpoint
- 1 npm stdio package @klever/mcp-server
Community signal: 31 GitHub stars.
What problem does it solve?
Building on Klever means constantly context-switching between docs, CLIs, and chain APIs while your agent lacks first-class contract actions.
Who is it for?
Indie developers already targeting Klever who want agent-driven contract scaffolding and chain integration during active build sprints.
Skip if: Builders on other L1/L2 stacks only, or teams that need managed mainnet ops/monitoring without any Klever footprint.
What do I get? / Deliverables
After registration, your agent can call Klever VM-oriented MCP tools locally via npm stdio or against the hosted https://mcp.klever.org/mcp endpoint while you implement contracts.
- Agent-invokable Klever smart contract development tools over MCP
- Optional zero-install remote access via https://mcp.klever.org/mcp
- Local stdio workflow via @klever/mcp-server v1.3.0
Recommended MCP Servers
Journey fit
Blockchain contract work is core product construction, so the canonical shelf is Build where integrations and backend-adjacent tooling live. Integrations subphase fits an MCP bridge to Klever’s VM and remote contract APIs rather than generic frontend polish.
How it compares
Klever-specific MCP integration, not a generic Ethereum Hardhat skill or wallet UI component.
Common Questions / FAQ
Who is mcp-klever-vm for?
Solo builders and small teams writing Klever smart contracts who want Claude Code, Cursor, or similar agents to use Klever-native MCP tools instead of manual CLI copy-paste.
When should I use mcp-klever-vm?
Use it in the build phase while you implement and refine Klever VM contracts and need repeated agent-assisted integration with Klever tooling.
How do I add mcp-klever-vm to my agent?
Either add the remote MCP URL https://mcp.klever.org/mcp (streamable-http) in your client, or install @klever/mcp-server from npm and configure stdio transport in your MCP settings.