Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EOS_MCP_CONFIGNoPath to config file. Discovery order: env var, ./config.ini, ~/.config/eos-mcp/config.ini

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
health_checkA

Report server version and configuration status (lightweight).

Call this at session start (or after a tool-call timeout) to confirm the MCP is up, see which version is running, and verify the device inventory config loads. Lightweight: it only reads and parses config.ini — it does NOT open any eAPI/pyeapi connection to EOS devices, so it is safe to call against a large fleet without touching the network.

Always returns the same keys: status (healthy / degraded / error), service, version, config_path (resolved config.ini path), device_count (EOS hosts in config), tags (sorted distinct tags), and config (ok / error / missing). On a degraded or error result, detail carries the reason.

get_router_listB

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

get_device_factsC

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

get_device_facts_batchA

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

get_versionA

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

get_config_diffA

Show config diff on an EOS device.

rollback_id=1 (default) → diff vs most recent rollback checkpoint. rollback_id=N → diff vs Nth rollback checkpoint. Note: diff vs startup-config requires EOS 4.30+; older versions fall back gracefully.

list_config_sessionsA

List configure sessions and their state on an EOS device.

Shows pending, pendingCommitTimer, and completed sessions. Useful for tracking in-flight push_config operations.

run_commandB

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

run_commandsB

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

run_command_batchA

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

Specify targets via 'hostnames', 'tags', or both.

run_commands_batchA

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

Specify targets via 'hostnames', 'tags', or both. Each device's output is labelled by hostname and command.

get_configC

Retrieve the running-config from an EOS device.

push_configA

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

When dry_run=True (default) shows diffs and aborts — no changes applied. When dry_run=False commits with a rollback timer (default 300 seconds). Call confirm_config_session before the timer expires to finalize.

confirm_config_sessionB

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

abort_config_sessionC

Abort a pending configure session on an EOS device.

collect_tech_supportB

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

daily_briefA

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

Checks environment (temperature, cooling, fans, PSUs), errdisabled interfaces, device uptime, MLAG status, and recent syslog alerts (BGP/OSPF/STP/LACP/MLAG/ link-down) within the last 'since_hours' hours. Returns CRITICAL/WARNING/OK per device with a summary. Specify targets via 'hostnames', 'tags', or both (default: all configured devices).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shigechika/eos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server