@mithung/vunet-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VUNET_BU_ID | Yes | Business Unit ID | 1 |
| VUNET_PASSWORD | Yes | Password for authentication | |
| VUNET_USERNAME | Yes | Username for authentication | |
| VUNET_TENANT_URL | Yes | Vunet tenant URL | |
| VUNET_VERIFY_SSL | No | Verify SSL certificates | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vunet_query_metricB | Query a Vunet data model/metric with flexible time ranges and filters. Automatically uses the configured tenant. |
| vunet_get_statusA | Get the current connection status and tenant information |
| vunet_list_data_modelsB | List common Vunet data models organized by category (APM, Infrastructure, Database, Network, etc.) |
| vunet_fetch_datamodelsA | Fetch the actual live DataModels (signals) configured in this VuNet tenant by calling /api/vuaccel/datamodel/. Returns real signal names, types (Metric/Event/Log), data sources, and column details. Use this to discover what data is available before querying with vunet_query_metric. |
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 4 tools
Both vunet_fetch_datamodels and vunet_list_data_models are about listing data models, with the former fetching live signals from the API and the latter listing common models by category. This overlap could lead to agent confusion despite the distinct descriptions.
All tools follow a consistent vunet_verb_noun pattern (e.g., vunet_fetch_datamodels, vunet_get_status), making the naming predictable and clear.
With 4 tools, the server is well-scoped for its purpose of data discovery and querying, covering essential operations without being too heavy or too thin.
The tools cover basic discovery and querying needs for VuNet data models, but minor gaps exist, such as a dedicated tool for drilling into specific metric details or handling pagination.