mcp-clickvisual
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CV_BASE_URL | Yes | ClickVisual web address, e.g. http://your-clickvisual:19001 | |
| CV_PASSWORD | Yes | ClickVisual login password (plain text; hashed with MD5 automatically before being sent) | |
| CV_USERNAME | Yes | ClickVisual login username |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsB | Search ClickVisual logs. Requires a numeric table_id and a time range. The query parameter uses SQL WHERE clause syntax, e.g. logtext LIKE '%error%'. |
| resolve_table_idB | Resolve a numeric tableId from instance ID, database name and table name. |
| list_instancesB | List all ClickVisual (ClickHouse) log instances. |
| list_databasesC | List databases under an instance. |
| list_tablesC | List log tables under a database. |
| get_log_chartsB | Get log histogram data (log count distribution over time). |
| check_authB | Verify the ClickVisual login state. |
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 7 tools
Each tool maps to a distinct action/resource: discovery hierarchy (instances/databases/tables), table ID resolution, log querying, histogram aggregation, and auth check. search_logs and get_log_charts both use table_id but clearly differ by returning raw logs versus count distribution.
All names follow a consistent verb_noun snake_case pattern (list_*, search_logs, resolve_table_id, get_log_charts, check_auth). There are no mixed conventions or vague verbs.
Seven tools is well-scoped for a read-only log exploration server. The discovery, search, histogram, and auth pieces all serve the same purpose without bloat.
The set covers the core workflow end-to-end: authenticate, discover instances/databases/tables, resolve the required numeric table_id, then search raw logs or view histograms. The only notable gap is schema/field discovery, which agents may need to construct meaningful search_logs queries.