How to add Klever MCP Server to Claude Desktop

Context-aware knowledge base for Klever blockchain smart-contract development on the Klever VM SDK. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 31★ · stdio · no auth

Claude Desktop config for Klever MCP Server

npx -y @klever/mcp-server

{
  "mcpServers": {
    "klever-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@klever/mcp-server"
      ]
    }
  }
}

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Klever MCP Server config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Klever MCP Server's tools appear under the 🔌 tools menu.

Before you start

Node.js with npx (for the npx-based install)
Optional: Klever SDK tools installed locally (required for transaction/deployment scripts)
Optional: Redis (only if using STORAGE_TYPE=redis instead of in-memory storage)

What Klever MCP Server can do in Claude Desktop

query_context

Search the Klever VM knowledge base for relevant development context, filterable by type, tags, and contract type.

add_context

Add new context entries to the knowledge base (disabled in public hosted mode).

get_context

Retrieve a specific context entry by its 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 (build/deploy/upgrade/query/test/interact); disabled in public mode.

enhance_with_context

Automatically enhance a query with relevant Klever VM context by extracting keywords and searching the knowledge base.

Security

The public hosted server at https://mcp.klever.org/mcp exposes only a read-only subset of tools; write operations (add_context) and shell-based tools (init_klever_project, add_helper_scripts) are disabled in public mode. Self-hosted public mode supports CORS allow-list, per-IP rate limiting (RATE_LIMIT_MCP / RATE_LIMIT_API), and a configurable request body size limit. The local stdio server's init_klever_project tool runs shell scripts that create project files on disk.

Klever MCP Server + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Klever MCP Server config there under the "mcpServers" key and restart the client.

Is Klever MCP Server safe to use with Claude Desktop?

Do I need to run the server myself?

No. You can connect to the official hosted public server with `claude mcp add -t http klever-vm https://mcp.klever.org/mcp`, or run it locally via `npx -y @klever/mcp-server`.

What is the difference between local and public mode?

The public hosted mode exposes a read-only subset of tools (query_context, get_context, find_similar, get_knowledge_stats, enhance_with_context). Write operations and shell-based tools like init_klever_project are only available when self-hosting.

What storage backends are supported?

In-memory (default; auto-loads the knowledge base on startup) or Redis (persistent, requires running `pnpm run ingest` once before starting).

View repo Full Klever MCP Server page