lvke-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LVKE_MCP_PROFILE | No | The profile name for the MCP server. | default |
| LVKE_MCP_TMP_DIR | No | The temporary directory for the MCP server. Defaults to ~/.lvke/tmp. | ~/.lvke/tmp |
| LVKE_MCP_DATA_DIR | No | The data directory for the MCP server. Defaults to ~/.lvke/. | ~/.lvke |
| LVKE_MCP_TAVILY_API_KEY | No | The Tavily API key used for web search. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoB | 示例工具:原样回显 message 参数。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlap between tools. Every tool has a clearly distinct purpose by default.
With a single tool, there is no pattern to violate. The name 'echo' is simple, clear, and directly describes its behavior.
The server has only one trivial tool (echo), which is far too few to provide any useful functionality. This is an extreme mismatch between the tool count and any conceivable practical scope.
The server only echoes input and offers no other operations. The surface is severely incomplete, lacking any meaningful domain coverage or lifecycle support.