rhoso-accel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| devtools_show_configA | Display the current dev-tools deployment configuration. TOOL_NAME=devtools_show_config DISPLAY_NAME=Show dev-tools Config USECASE=Inspect the effective SNO/RHOSO configuration before deploying. INSTRUCTIONS=Call with no arguments. INPUT_DESCRIPTION=none OUTPUT_DESCRIPTION=status, stdout (config dump), stderr, exit_code EXAMPLES=devtools_show_config() PREREQUISITES=configs/sno.local.sh present (optional) RELATED_TOOLS=devtools_validate_config |
| devtools_validate_configA | Validate the dev-tools configuration before deployment. TOOL_NAME=devtools_validate_config DISPLAY_NAME=Validate dev-tools Config USECASE=Confirm required SNO_* variables and BMC credentials are set. INSTRUCTIONS=Call with no arguments; fix any reported missing variables. INPUT_DESCRIPTION=none OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_validate_config() PREREQUISITES=SNO_BMC_HOST, SNO_NODE_MAC set (via configs/sno.local.sh) RELATED_TOOLS=devtools_show_config, devtools_deploy_sno |
| devtools_show_kubeconfigA | Show the kubeconfig location and access instructions for the SNO cluster. TOOL_NAME=devtools_show_kubeconfig DISPLAY_NAME=Show Kubeconfig USECASE=Find how to reach the cluster after deploy_sno completes. INSTRUCTIONS=Call after deploy_sno. INPUT_DESCRIPTION=none OUTPUT_DESCRIPTION=status, stdout (kubeconfig path/instructions), stderr, exit_code EXAMPLES=devtools_show_kubeconfig() PREREQUISITES=deploy_sno has run RELATED_TOOLS=devtools_deploy_sno |
| devtools_deploy_snoA | Deploy Single Node OpenShift via dev-tools TOOL_NAME=devtools_deploy_sno DISPLAY_NAME=Deploy Single Node OpenShift USECASE=Provision the SNO cluster RHOSO installs on. DESTRUCTIVE (bare metal). INSTRUCTIONS=1) Ensure configs/sno.local.sh is set. 2) Call with confirm=true. INPUT_DESCRIPTION=confirm (bool) — must be true; guards against accidental provisioning OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_sno(confirm=True) PREREQUISITES=Valid BMC creds + configs/sno.local.sh RELATED_TOOLS=devtools_validate_config, devtools_show_kubeconfig |
| devtools_install_lvm_operatorA | Install the LVM Storage Operator on the cluster. TOOL_NAME=devtools_install_lvm_operator DISPLAY_NAME=Install LVM Storage Operator USECASE=Provide local storage for RHOSO. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_install_lvm_operator(confirm=True) PREREQUISITES=SNO_OPENSHIFT_VERSION set; cluster reachable RELATED_TOOLS=devtools_configure_lvm_cluster |
| devtools_configure_lvm_clusterA | Configure the LVMCluster device class. TOOL_NAME=devtools_configure_lvm_cluster DISPLAY_NAME=Configure LVMCluster USECASE=Register storage devices with the LVM operator. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_configure_lvm_cluster(confirm=True) PREREQUISITES=SNO_LVM_DEVICES set; LVM operator installed RELATED_TOOLS=devtools_install_lvm_operator |
| devtools_install_gitops_operatorA | Install the OpenShift GitOps (ArgoCD) operator. TOOL_NAME=devtools_install_gitops_operator DISPLAY_NAME=Install OpenShift GitOps Operator USECASE=Install ArgoCD used to deploy RHOSO via GitOps. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_install_gitops_operator(confirm=True) PREREQUISITES=cluster reachable RELATED_TOOLS=devtools_enable_argocd, devtools_configure_openshift_gitops |
| devtools_enable_argocdA | Enable an ArgoCD instance with OpenStack health checks. TOOL_NAME=devtools_enable_argocd DISPLAY_NAME=Enable ArgoCD Instance USECASE=Stand up the ArgoCD instance. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_enable_argocd(confirm=True) PREREQUISITES=GitOps operator installed RELATED_TOOLS=devtools_install_gitops_operator, devtools_configure_openshift_gitops |
| devtools_configure_openshift_gitopsA | Configure ArgoCD with cluster-wide permissions and TLS. TOOL_NAME=devtools_configure_openshift_gitops DISPLAY_NAME=Configure OpenShift GitOps USECASE=Grant ArgoCD the permissions/TLS RHOSO needs. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_configure_openshift_gitops(confirm=True) PREREQUISITES=ArgoCD instance enabled RELATED_TOOLS=devtools_enable_argocd |
| devtools_deploy_openstack_dependenciesA | Deploy OpenStack dependencies (Cert-manager, MetalLB, NMState). TOOL_NAME=devtools_deploy_openstack_dependencies DISPLAY_NAME=Deploy OpenStack Dependencies USECASE=Install the operators RHOSO depends on. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_openstack_dependencies(confirm=True) PREREQUISITES=cluster reachable RELATED_TOOLS=devtools_deploy_openstack_operator |
| devtools_deploy_openstack_operatorA | Deploy the OpenStack operator. TOOL_NAME=devtools_deploy_openstack_operator DISPLAY_NAME=Deploy OpenStack Operator USECASE=Install the RHOSO OpenStack operator. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_openstack_operator(confirm=True) PREREQUISITES=OpenStack dependencies deployed RELATED_TOOLS=devtools_deploy_openstack_operator_cr |
| devtools_deploy_openstack_operator_crA | Deploy the OpenStack operator CR to bootstrap services. TOOL_NAME=devtools_deploy_openstack_operator_cr DISPLAY_NAME=Deploy OpenStack Operator CR USECASE=Bootstrap the RHOSO services via the operator CR. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_openstack_operator_cr(confirm=True) PREREQUISITES=OpenStack operator deployed RELATED_TOOLS=devtools_deploy_openstack_operator |
| devtools_deploy_eso_secrets_operatorA | Deploy the External Secrets Operator (recommended secrets backend). TOOL_NAME=devtools_deploy_eso_secrets_operator DISPLAY_NAME=Deploy External Secrets Operator USECASE=Install ESO to sync secrets from Vault. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_eso_secrets_operator(confirm=True) PREREQUISITES=cluster reachable RELATED_TOOLS=devtools_configure_eso_authentication |
| devtools_deploy_vault_secrets_operatorA | Deploy the Vault Secrets Operator. TOOL_NAME=devtools_deploy_vault_secrets_operator DISPLAY_NAME=Deploy Vault Secrets Operator USECASE=Install the Vault Secrets Operator. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_deploy_vault_secrets_operator(confirm=True) PREREQUISITES=cluster reachable RELATED_TOOLS=devtools_configure_vault_authentication |
| devtools_configure_eso_authenticationA | Configure the ESO SecretStore with Vault AppRole authentication (recommended). TOOL_NAME=devtools_configure_eso_authentication DISPLAY_NAME=Configure ESO Authentication USECASE=Wire ESO to Vault via AppRole. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_configure_eso_authentication(confirm=True) PREREQUISITES=OPENSTACK_NAMESPACE set; ESO deployed RELATED_TOOLS=devtools_deploy_eso_secrets_operator |
| devtools_configure_vault_authenticationA | Configure Vault AppRole authentication. TOOL_NAME=devtools_configure_vault_authentication DISPLAY_NAME=Configure Vault Authentication USECASE=Set up Vault AppRole auth for the deployment. Modifies the cluster. INPUT_DESCRIPTION=confirm (bool) — must be true OUTPUT_DESCRIPTION=status, stdout, stderr, exit_code EXAMPLES=devtools_configure_vault_authentication(confirm=True) PREREQUISITES=OPENSTACK_NAMESPACE set; Vault Secrets Operator deployed RELATED_TOOLS=devtools_deploy_vault_secrets_operator |
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 16 tools
Each tool maps to a distinct deployment stage or resource: config inspection/validation, SNO provisioning, LVM, GitOps/ArgoCD, OpenStack operators, and secrets backends. Even closely related tools like install_gitops_operator, enable_argocd, and configure_openshift_gitops have clear boundaries through their descriptions.
Names consistently follow a devtools_<verb>_<target> snake_case pattern, but there are minor deviations: operator installation uses both 'install' and 'deploy' (install_lvm_operator vs deploy_openstack_operator), and enable_argocd is slightly different in style. Overall the set is still predictable and readable.
At 16 tools, the set is slightly over the ideal 3-15 range but each tool corresponds to a discrete deployment step in a multi-stage RHOSO provisioning workflow. The count feels justified rather than bloated.
The tool surface covers the core deployment lifecycle well: config validation, SNO provisioning, storage, GitOps, OpenStack operators, and secrets backends. Notable gaps include no teardown/rollback tools and no final deployment status verification beyond kubeconfig display, but agents can complete the primary workflow.