commander-mcp

name	commander-mcp
description	Access commander-mcp for ALL infrastructure data, skills, and methodology
disable-model-invocation	false

Commander MCP — Your Single Source of Truth

ALL infrastructure data, methodology, and project context lives in commander-mcp (dev-02:30040). Do NOT hardcode IPs, ports, credentials, or service info. Query at runtime.

MCP Tools Available (86 tools)

Get Skills (replaces local /skill-name loading)

• get_skill(name) — get full skill content by name
• list_skills() — list all available skills
• search_skills(query) — search skills by content

Get Infrastructure Data (replaces config YAML files)

• get_context_servers — server landscape (IPs, specs, status)
• get_context_ports — port allocations
• get_context_databases — database configs and credentials
• get_context_services — service catalog with health
• get_context_repos — git repository list
• get_context_cicd — CI/CD pipeline config
• get_context_environment — env vars for all services

CMDB Queries (live infrastructure graph)

• list_servers, get_server(key) — server details from ArangoDB
• list_services, get_service(key) — service details
• list_ports, get_port(key) — port mappings
• query_dependencies(key, direction) — dependency graph traversal (upstream/downstream/both)
• get_topology() — full infrastructure topology
• search_infra(query) — search across all infrastructure

SDLC / Pipeline (development workflow)

• get_stage_instructions(stage) — what to do at each pipeline stage
• list_pipeline_runs, create_pipeline_run — manage runs
• list_work_items, create_work_item — work items
• list_scenarios, get_scenario — test scenarios
• transition_work_item(id, status) — move items through statuses

Credentials

• list_credentials — list available credentials
• get_credential(name) — get credential value securely

Agent Coordination

• agent_heartbeat — report agent status
• log_agent_event — log events for audit
• log_cost_event — track API costs

Direct REST Endpoints (for SSH/curl access)

When MCP tools aren't available (e.g., on a remote server via SSH):

curl -s 'http://localhost:30040/skill/<name>'
curl -s 'http://localhost:30040/context/<type>'
curl -s 'http://localhost:30040/skill-catalog'
curl -s 'http://localhost:30040/health'

Key Principle

Never hardcode infrastructure data. Always query commander-mcp at runtime. When you need server IPs, port numbers, credentials, or service configs — use the tools above.