debug_error — mcp klever vm MCP Prompt

debug_error is one of 4 prompts on the mcp klever vm MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke debug_error from your client

• Claude Code mcp klever vm Prompt/debug_error run in your project directory
• Claude Desktop mcp klever vm Prompt/debug_error ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor mcp klever vm Prompt/debug_error ~/.cursor/mcp.json
• VS Code mcp klever vm Prompt/debug_error .vscode/mcp.json
• Zed mcp klever vm Prompt/debug_error ~/.config/zed/settings.json
• Windsurf mcp klever vm Prompt/debug_error ~/.codeium/windsurf/mcp_config.json
• Cline mcp klever vm Prompt/debug_error ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI mcp klever vm Prompt/debug_error ~/.gemini/settings.json
• Grok mcp klever vm Prompt/debug_error .mcp.json (in your project root)
• ChatGPT mcp klever vm Prompt/debug_error Settings → Connectors → Advanced → Developer mode
• Claude.ai mcp klever vm Prompt/debug_error Settings → Connectors → Add custom connector
• LangChain mcp klever vm Prompt/debug_error pip install langchain-mcp-adapters

Other prompts on this server

• create_smart_contract
• add_feature
• review_contract

mcp klever vm also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.