API-Central
Integrates with Git for version control of the API-Central tooling, with git-ignored configuration files for security and project management.
Provides GitHub integration for cloning the repository, reporting security issues via GitHub Issues, and managing the project's codebase and documentation.
Includes Postman download scripts for API collections, facilitating API testing and integration with HPE Aruba Central's REST API endpoints.
Integrates with Pytest for running unit and integration tests, ensuring code quality and reliability of the HPE Aruba Central automation tools.
Built with Python for network automation tooling, providing CLI tools for batch migration workflows and the underlying implementation of MCP servers.
Uses YAML for credential configuration files (credentials.yaml), providing structured and readable configuration management for HPE Aruba Central API authentication.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@API-Centralshow me all access points at the New York office"
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.
API-Central — Aruba New Central Automation
Python tooling for HPE Aruba Central (New Central) — network device migration, SSID configuration, switch provisioning, and GreenLake Platform management.
Designed to work as a Claude Code MCP server so you can drive network operations conversationally, and as standalone CLI tools for batch migration workflows.
Features
88 MCP tools across three domain servers (monitoring, config, ops)
8-stage migration pipeline — discover devices → verify config → push to New Central
SSID build/delete with scope-map targeting (org-wide, site, or group)
Switch provisioning: VLANs, port profiles, SVIs
GreenLake Platform (GLP) subscription and device management
Async troubleshooting: ping, traceroute, cable test, PoE bounce, reboot
Prerequisites
Python ≥ 3.10
uv(recommended) orpipHPE Aruba Central account with API credentials (OAuth2 client ID + secret)
Setup
# 1. Clone and install dependencies
git clone https://github.com/your-org/API-Central.git
cd API-Central
uv sync
# 2. Configure credentials
cp config/credentials.yaml.example config/credentials.yaml
# Edit config/credentials.yaml — fill in client_id, client_secret, base_url
# 3. Configure MCP servers (for Claude Code integration)
cp .mcp.json.example .mcp.json
# Edit .mcp.json — replace /path/to/API-Central with your actual clone pathSecurity:
config/credentials.yamland.mcp.jsonare git-ignored. Never commit them.
Usage
Claude Code MCP integration
Once .mcp.json is configured, start Claude Code from this directory — the three MCP servers (aruba-monitoring, aruba-config, aruba-ops) will load automatically.
Example prompts:
"List all devices at the Home Lab site"
"Build a WPA3 SSID called Corp-WiFi on VLAN 100 for all APs"
"Ping 8.8.8.8 from switch SN123456"
CLI — Migration pipeline
python run_pipeline.py --input inputs/devices.csvRuns the full 8-stage migration (discover → assign → configure → verify). Idempotent — safe to re-run.
CLI — SSID builder
python run_ssid.pyInteractive SSID build/delete workflow.
Project layout
mcp_servers/
monitoring.py Monitoring tools (health, trends, wireless metrics)
config.py Config tools (SSIDs, VLANs, profiles, webhooks, firmware)
ops.py Ops tools (reboots, ping, cable test, PoE bounce, GLP)
shared.py Shared utilities
pipeline/
clients/ CentralClient, GLPClient, MCPClient, TokenManager
stages/ s1_discover → s8_verify
config.py Credential loader
ssid_underlay.py SSID build/delete logic
config/
credentials.yaml.example Template — copy to credentials.yaml and fill in
resources/ Postman download script (collections git-ignored — see resources/README.md)
inputs/ CSV templates for batch migration
tests/ Unit + integration testsRunning tests
pytest tests/All tests use mock credentials — no real API calls.
Documentation
See CLAUDE.md for:
Full MCP tool reference and verb/noun naming conventions
Scope and device-type translation rules
API endpoint patterns
Token cost optimization tips
Security
Credentials load at runtime from
config/credentials.yaml(git-ignored)No secrets are hardcoded in source files
Token cache files (
.token_cache_*.json) are git-ignoredMCP server config (
.mcp.json) is git-ignored — it contains local paths
Report security issues via GitHub Issues — do not include credentials in bug reports.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/secure-ssid/centralmcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server