infra-tak-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketplace_listA | Catalog of infra-TAK marketplace module keys this MCP knows how to drive. |
| marketplace_callA | Call /api// on the infra-TAK console. action: status | log | logs | version | update-status | start | stop | restart | deploy | uninstall | raw raw body_json: {"method":"GET","path":"deployment-config","json":{}} confirm=true required for deploy, uninstall, start, stop, restart. |
| marketplace_deployB | Start a marketplace deploy job. Poll marketplace_call(module, 'log'). |
| marketplace_controlC | Start, stop, or restart a marketplace module. |
| marketplace_uninstallB | Uninstall a marketplace module. Requires confirm=true. |
| nodered_infoA | Node-RED settings, diagnostics, and palette from the loopback Admin API. |
| nodered_list_flowsB | GET /flows from Node-RED Admin API on 127.0.0.1:1880. |
| nodered_deploy_flowsB | POST /flows and replace the running Node-RED document. confirm=true required. |
| nodered_add_flowB | Append nodes to the current flows and redeploy. confirm=true required. |
| nodered_install_nodeC | Install a palette package such as node-red-contrib-tak. |
| nodered_injectC | Trigger an inject node by id. |
| stack_healthB | Probe MediaMTX, Node-RED Admin, TAK Marti, and infra-TAK console. |
| mediamtx_pathsB | List MediaMTX paths. infra-TAK binds the control API on :9898. |
| mediamtx_infoC | MediaMTX server info. |
| docker_psA | List Docker containers (ALLOW_DOCKER=1). |
| docker_logsC | Tail logs for a Docker container. |
| tak_list_videosB | List TAK Server Video Manager feeds. |
| tak_publish_videoC | Register a MediaMTX path on TAK Video Manager with decomposed fields. |
| advertise_ready_streamsB | POST every ready MediaMTX path into TAK Video Manager. |
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 19 tools
The domain-prefixed tools mostly target distinct resources, but marketplace_call is a generic escape hatch that explicitly supports deploy/start/stop/restart/uninstall, directly overlapping marketplace_deploy, marketplace_control, and marketplace_uninstall. nodered_deploy_flows vs nodered_add_flow also sit close together (replace vs append the flow document). An agent could reasonably pick the wrong tool for marketplace operations.
Strong, predictable snake_case with domain prefixes (marketplace_*, nodered_*, mediamtx_*, docker_*, tak_*). Two outliers lack a prefix (stack_health, advertise_ready_streams), which is a minor deviation but still readable.
19 tools is on the heavy side but justified by spanning five subsystems (marketplace, Node-RED, MediaMTX, Docker, TAK). The count is slightly inflated by the redundant marketplace_call umbrella overlapping three dedicated marketplace tools.
Covers lifecycle across its domains: marketplace list/call/deploy/control/uninstall, Node-RED flows and palette, MediaMTX listing, Docker listing/logs, and TAK video publish/advertise. Minor gaps exist (no Docker container start/stop or MediaMTX path mutation), but core workflows are reachable.