Ambari MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEOUT_MS | No | Timeout in milliseconds for requests to Ambari server | 30000 |
| AMBARI_BASE_URL | Yes | The base URL of the Ambari server API, e.g., http://your-ambari-server:8080/api/v1 | |
| AMBARI_PASSWORD | Yes | The password for Ambari authentication | |
| AMBARI_USERNAME | Yes | The username for Ambari authentication |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ambari_clusters_getclustersC | Returns all clusters |
| ambari_clusters_getclusterB | Returns information about a specific cluster |
| ambari_clusters_createclusterC | Creates a cluster |
| ambari_services_getservicesC | Get all services for a cluster |
| ambari_services_getserviceC | Get the details of a service |
| ambari_hosts_gethostsC | Returns a collection of all hosts |
| ambari_hosts_gethostB | Returns information about a single host |
| ambari_alerts_gettargetsC | Returns all alert targets |
| ambari_alerts_getalertsB | Get all alerts for a cluster with filtering options |
| ambari_alerts_getalertsummaryB | Get alert summary in grouped format for a cluster |
| ambari_alerts_getalertdetailsB | Get details for a specific alert definition |
| ambari_alerts_getalertdefinitionsB | Get all alert definitions for a cluster |
| ambari_alerts_updatealertdefinitionB | Update an alert definition (enable/disable or modify properties) |
| ambari_alerts_getalertgroupsB | Get all alert groups for a cluster |
| ambari_alerts_createalertgroupC | Create a new alert group |
| ambari_alerts_updatealertgroupB | Update an existing alert group |
| ambari_alerts_deletealertgroupB | Delete an alert group |
| ambari_alerts_duplicatealertgroupB | Duplicate an existing alert group with a new name |
| ambari_alerts_adddefinitiontogroupB | Add an alert definition to an alert group |
| ambari_alerts_removedefinitionfromgroupB | Remove an alert definition from an alert group |
| ambari_alerts_getnotificationsC | Get all alert notification targets |
| ambari_alerts_createnotificationB | Create a new alert notification target |
| ambari_alerts_updatenotificationB | Update an existing alert notification target |
| ambari_alerts_deletenotificationB | Delete an alert notification target |
| ambari_alerts_addnotificationtogroupB | Add a notification target to an alert group |
| ambari_alerts_removenotificationfromgroupB | Remove a notification target from an alert group |
| ambari_alerts_savealertsettingsB | Save cluster-level alert settings (like repeat tolerance) |
| ambari_services_getserviceswithstaleconfigsA | Get services and components that have stale configurations requiring restart |
| ambari_services_gethostcomponentswithstaleconfigsA | Get host components that need restart due to stale configurations |
| ambari_services_restartserviceC | Restart a specific service on the cluster |
| ambari_services_restartcomponentsB | Restart specific components that have stale configurations |
| ambari_services_getservicestateC | Get detailed state information for a specific service |
| ambari_services_startserviceB | Start a specific service on the cluster |
| ambari_services_stopserviceB | Stop a specific service on the cluster |
| ambari_services_getrollingrestartstatusC | Get the status of rolling restart operations for services |
| ambari_services_enablemaintenancemodeB | Enable maintenance mode for a service or component |
| ambari_services_disablemaintenancemodeB | Disable maintenance mode for a service or component |
| ambari_services_runservicecheckB | Run service check for a specific service to verify it is working correctly |
| ambari_services_isservicechecksupportedC | Check if service check is supported for a specific service in the stack |
| ambari_services_getservicecheckstatusA | Get the status of recent service check operations for a service |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Ambari Clusters | List of all Ambari clusters with basic information |
| Cluster Details | Detailed information about a specific cluster including services and hosts |
| Cluster Services | All services running in a specific cluster with their status |
| Cluster Hosts | All hosts in a specific cluster with their status and components |
| Cluster Alerts | Current alerts for a specific cluster grouped by severity |
| Alert Summary | Summarized alert information for quick cluster health overview |
| Stale Configurations | Services and components that need restart due to configuration changes |
| Service Details | Detailed information about a specific service including components and configurations |
| Service Components | All components of a specific service with their host assignments and status |
| Host Details | Detailed information about a specific host including installed components |
| Recent Operations | Recent operations and their status (restarts, service checks, etc.) |
| Cluster Configurations | Current configuration for all services in the cluster |
TDQS
Scored across 40 tools
Tools are organized by category (alerts, clusters, hosts, services) and most have distinct purposes. However, some alert-related tools like getalertdefinitions, getalertdetails, getalerts, and getalertsummary could cause confusion due to similar names and overlapping functionality.
All tools follow a consistent pattern of ambari_{category}_{action} in snake_case, making it predictable and easy to understand the hierarchy and action.
With 40 tools, the server exceeds the recommended range. While the domain may require many operations, the count feels heavy and could be streamlined by merging some duplicate-like functions.
Covers many operations but has notable gaps: missing cluster update/delete, host add/remove/update, service add/remove, and alert definition delete. CRUD is incomplete for clusters and hosts.