MCP.Market

EOS MCP server

by shigechika·io.github.shigechika/eos-mcp·v1.4.0
No reviews yet

MCP server for Arista EOS device operations via eAPI

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars75 downloads/wk

Reviews

Write one

Nobody has reviewed EOS MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

EOS MCP tools (17, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • abort_config_session

    Abort a pending configure session on an EOS device.

  • collect_tech_support

    Collect show tech-support from an EOS device (large output, 30+ seconds).

  • confirm_config_session

    Confirm (finalize) a pending configure session commit timer on an EOS device.

  • daily_briefwrite action

    Run health checks on EOS devices and return a Markdown daily brief.

  • get_config

    Retrieve the running-config from an EOS device.

  • get_config_diff

    Show config diff on an EOS device.

  • get_device_facts

    Return structured device facts: hostname, model, serial, EOS version, uptime, memory.

  • get_device_facts_batch

    Return device facts (model, serial, EOS version, uptime) for multiple devices in parallel.

  • get_router_list

    List EOS devices registered in config, optionally filtered by tags.

  • get_version

    Return EOS version string for a device (quick connectivity check).

  • health_check

    Report server version and configuration status (lightweight).

  • list_config_sessions

    List configure sessions and their state on an EOS device.

  • push_config

    Push configuration to an EOS device via a named configure session.

  • run_commandwrite action

    Run a single enable-mode command on an EOS device and return text output.

  • run_command_batchwrite action

    Run an enable-mode command on multiple EOS devices in parallel.

  • run_commandswrite action

    Run multiple enable-mode commands on one EOS device and return labelled output.

  • run_commands_batchwrite action

    Run multiple enable-mode commands on multiple EOS devices in parallel.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How EOS MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
17
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
75
more than 56% of 12,191 servers with a package

What its tools let an agent do: 12 read · 1 change · 4 run or deploy

Release history: 2 versions in the registry since 2026-08-15, latest 2026-09-29, typically one every 45 days.

Install EOS MCP in Claude Code, Cursor or VS Code

claude mcp add eos-mcp -- uvx eos-mcp
Add to Cursor

What the publisher says

From the EOS MCP repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.shigechika/eos-mcp -->

eos-mcp

English | 日本語

MCP server for Arista EOS device operations via eAPI.

Exposes EOS show commands, running-config retrieval, configuration push (via configure session with commit timer), and tech-support collection to MCP-compatible AI assistants.

Documentation:

Installation

pip install eos-mcp

Configuration

Copy config.ini.example to ~/.config/eos-mcp/config.ini and fill in credentials:

[DEFAULT]
username = admin
password = yourpassword
transport = https
verify = false

[switch1.example.com]
tags = main,dc1

[switch2.example.com]
tags = main,dc1

Config file discovery order:

  1. EOSMCPCONFIG environment variable
  2. ./config.ini (current directory)
  3. ~/.config/eos-mcp/config.ini

(Individual MCP tool calls may also override the path via a config_path parameter.)

Write operations

Three tools change device state through a guarded path:

Give the config.ini account for a device a lower-privilege, show-only role and these three tools fail against the EOS API instead of writing; every read-only tool for that device keeps working.

runcommand, runcommands, runcommandbatch, and runcommandsbatch are not restricted to show ... commands, despite being documented and grouped as command runners. Nothing in the server validates or whitelists the command text — it is passed to the eAPI Command API verbatim — so these tools can execute arbitrary enable-mode EOS commands, including configure terminal ... or reload, on any configured device (a single host, or fleet-wide via tags in the batch variants). This is gated by the same EOS account privilege as pushconfig, but without pushconfig's dryrun / commit-timer safety net — a de facto second write path worth remembering when deciding how privileged a device's config.ini account should be.

Usage

Claude Code (plugin)

This repository doubles as a single-plugin marketplace, so Claude Code can install the server for you:

/plugin marketplace add shigechika/eos-mcp
/plugin install eos-mcp@eos-mcp

The plugin launches uvx eos-mcp and reads EOSMCPCONFIG, the same variable described in Configuration. Leave it unset and the server falls through to its normal discovery order (./config.ini, then ~/.config/eos-mcp/config.ini). /plugin install only wires up the server process — it cannot create the config.ini file or the per-device eAPI credentials it holds; that file must already exist on the machine running the plugin before any tool but health_check will succeed.

uvx must be on the PATH of the process that runs Claude Code — a login shell usually has it, but a GUI-launched app may not; install uv system-wide if the plugin fails to start.

Claude Code (manual)

In .mcp.json:

{
  "mcpServers": {
    "eos-mcp": {
      "type": "stdio",
      "command": "eos-mcp"
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

EOS MCP: common questions

Is EOS MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the EOS MCP safety report
How do I install EOS MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does EOS MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is EOS MCP maintained?
The last commit was 3 days ago (2026-11-01). The latest release is v1.4.0.
How does EOS MCP compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 17 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from shigechika →