Connections & Capabilities
Connects To
Capabilities
Quickstart
Config
{
"servers": {
"pyats": {
"type": "stdio",
"command": "python3",
"args": [
"-u",
"/Users/johncapobianco/pyATS_MCP/pyats_mcp_server.py"
],
"env": {
"PYATS_TESTBED_PATH": "/Users/johncapobianco/pyATS_MCP/testbed.yaml"
}
}
}Exposed MCP Tools (5)
run_show_commandExecutes show commands on network devices and returns the output.
Read-only operation; retrieves information without modifying the device.
run_ping_commandExecutes ping tests on network devices and returns the results.
Read-only operation; tests network connectivity without modifying the device.
apply_configurationApplies configuration commands to network devices.
Modifies the configuration of network devices, potentially disrupting network services.
learn_configFetches the running configuration from a network device.
Read-only operation; retrieves the device configuration without modifying it.
learn_loggingFetches system logs from a network device.
Read-only operation; retrieves log data without modifying the device.
Safety Assessment
The pyATS MCP server offers a relatively safe way to interact with network devices due to its input validation and command restrictions. However, the ability to make configuration changes and the reliance on environment variables for security introduce some risk. It is safest when used in a controlled environment with a well-defined and trusted testbed configuration.
- Input validation using Pydantic schemas.
- Blocks unsafe commands (erase, reload, write).
- Prevents pipe/redirect abuse.
- Operates entirely via STDIO, minimizing attack surface.
- Potential for misconfiguration if testbed.yaml is compromised.
- Configuration changes can impact network devices.
- No built-in authentication beyond environment variables.
- Vulnerable if the underlying pyATS framework has vulnerabilities.
