Skip to main content
Glama
deenesjakoruzh
MiguelCarpio

rhoso-accel-mcp

by MiguelCarpio
OverviewSchemaRelated ServersScoreDiscussions
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.

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)

Register with an MCP client, e.g. Claude CLI over stdio:

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

This server cannot be installed

-
license - not tested
-
quality - not tested
C
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

  • Backtest360

    MCP server exposing the Backtest360 engine API as tools for AI agents.

  • microservices.sh

    MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

  • PlanExe

    MCP server for generating rough-draft project plans from natural-language prompts.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MiguelCarpio/rhoso-accel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server