About this integration
MCP server for Arista EOS device operations via eAPI
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.3.0
- Package
- eos-mcp
- Last compatibility test
- Not independently tested
Connect your agent
eos-mcpPublisher README and Python manifest reviewed at their pinned hashes; not runtime tested or security audited. This is not read-only: configuration tools can change devices, and command-runner tools pass arbitrary enable-mode commands without a whitelist or the configuration tool's dry-run safeguard. Device-account privilege is the controlling boundary.
Capabilities: Inspect EOS device facts and running configuration, Run commands on individual devices or tagged batches, Stage, confirm, or abort configuration sessions, Collect tech-support output and daily health briefs
Connected profiles
Additional details
io.github.shigechika/eos-mcp
Source ↗ · Checked 2026-09-171.3.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17eos-mcp
Source ↗ · Checked 2026-09-191.3.0
Source ↗ · Checked 2026-09-19Publisher documentation gives a direct command for starting the stdio MCP server; the server and device connections were not started in this review.
Source ↗ · Checked 2026-09-19The documented device connection uses an EOS username and password from config.ini. Basic username/password authentication is outside the native catalog taxonomy, so authentication is classified as unknown with credential setup required.
Source ↗ · Checked 2026-09-19Publisher client configuration launches eos-mcp over stdio and optionally points EOS_MCP_CONFIG to the device inventory and credential file.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19