Which integrations are available for this server?

Provides tools to enable and configure Argo CD (OpenShift GitOps) for managing deployments on the cluster. Provides tools to deploy and configure OpenStack operators and custom resources on a single-node OpenShift cluster. Provides tools to deploy the HashiCorp Vault secrets operator and configure its authentication for secret management.

How do I use rhoso-accel-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@rhoso-accel-mcp validate the current config, then show me the kubeconfig" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

rhoso-accel-mcp

by MiguelCarpio

Overview Schema Source Related Servers Discussions Admin

Python

Remote

rhoso-accel-mcp

A single MCP server that lets AI agents drive the full RHOSO-to-GPU-validated-VM bring-up end to end

Wraps rhos-vaf/dev-tools — its make targets are exposed as MCP tools — following the Red Hat template-mcp-server conventions.

Tools

Read/safe (auto-run):

Tool	Wraps
`devtools_show_config`	`make show_config`
`devtools_validate_config`	`make validate_config`
`devtools_show_kubeconfig`	`make show_kubeconfig`

Write/destructive (require confirm=True):

Tool	Wraps
`devtools_deploy_sno`	`make deploy_sno`
`devtools_install_lvm_operator`	`make install_lvm_operator`
`devtools_configure_lvm_cluster`	`make configure_lvm_cluster`
`devtools_install_gitops_operator`	`make install_gitops_operator`
`devtools_enable_argocd`	`make enable_argocd`
`devtools_configure_openshift_gitops`	`make configure_openshift_gitops`
`devtools_deploy_openstack_dependencies`	`make deploy_openstack_dependencies`
`devtools_deploy_openstack_operator`	`make deploy_openstack_operator`
`devtools_deploy_openstack_operator_cr`	`make deploy_openstack_operator_cr`
`devtools_deploy_eso_secrets_operator`	`make deploy_eso_secrets_operator`
`devtools_deploy_vault_secrets_operator`	`make deploy_vault_secrets_operator`
`devtools_configure_eso_authentication`	`make configure_eso_authentication`
`devtools_configure_vault_authentication`	`make configure_vault_authentication`

Every tool returns {"status", "command", "stdout", "stderr", "exit_code"} and never raises.

Related MCP server: mcp-makefile-server

Configuration

DEVTOOLS_DIR (in .env) points at your dev-tools checkout. If left empty, the server auto-clones rhos-vaf/dev-tools into DEVTOOLS_CLONE_DIR (/tmp/dev-tools) on first use and refreshes it (git remote update && git checkout origin/main) on later runs — so read-only tools work with zero config. For real deploys, set DEVTOOLS_DIR to your own checkout containing configs/sno.local.sh; the auto-clone has no config, so destructive tools will fail validate_config until one is provided.

Run

cp .env.example .env      # optionally set DEVTOOLS_DIR
make install              # uv venv + deps
make test                 # unit tests (no real make execution)
make local                # run over stdio (local agent)
# make http               # run over HTTP (remote/CI agent)

claude mcp add rhoso-accel --scope user -- uv run --directory /path/to/rhoso-accel-mcp rhoso-accel-mcp

Or over HTTP:

make http   # serves on http://127.0.0.1:5001
claude mcp add --transport http rhoso-accel http://localhost:5001/mcp --scope user

Available Tools

16 tools

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