MCP.so
Sign In

Nornir MCP Server

@yhvh-chen

Basic information

Category

Other

License

MIT license

Transports

stdio

Author

yhvh-chen

Submitted by

Yawei Chen

About Nornir MCP Server

Nornir MCP Server

Nornir MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "nornir_mcp_local": {
      "name": "Nornir MCP Server",
      "type": "sse",
      "url": "http://YOUR_SERVER_IP:8000/sse",
      "command": "DON'T NEED"
    }
  }
}

Nornir MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is 🌐 Nornir MCP Server?

A FastMCP server that provides network automation tools powered by Nornir and NAPALM. It bridges Nornir/NAPALM network operations as MCP (Massively Concurrent Processing) tools, making them accessible from compatible MCP clients. Designed for network engineers and automation practitioners.

How to use 🌐 Nornir MCP Server?

Configure network inventory and device credentials by editing hosts.yaml, groups.yaml, and defaults.yaml in the conf/ directory. Then run docker-compose up --build -d in the project root. The server starts on port 8000 using SSE transport. Connect an MCP client (e.g., FastMCP Web UI) by adding a server with URL http://localhost:8000/sse.

Key features of 🌐 Nornir MCP Server

  • Leverages Nornir for inventory management and concurrent task execution.
  • Uses NAPALM for multi-vendor device interaction and information gathering.
  • Built with FastMCP for seamless integration with MCP clients.
  • Containerized with Docker for easy setup and deployment.
  • Uses uv for fast Python dependency management within the container.
  • Provides tools for sending read-only commands and retrieving device facts.

Use cases of 🌐 Nornir MCP Server

  • Retrieve device facts (facts, interfaces, IP addresses, ARP tables, etc.) from multi-vendor networks.
  • Send read-only commands to network devices and collect output.
  • Perform automated device health checks and generate assessment reports.
  • Integrate network automation into larger MCP-based orchestration workflows.

Frequently asked questions

1

What are the prerequisites to run the server?

Docker and Docker Compose (usually included with Docker Desktop) must be installed on your system.

2

How do I configure device credentials?

Edit `hosts.yaml`, `groups.yaml`, and `defaults.yaml` in the `conf/` directory. Credentials are stored in plaintext by default – for production environments, use Nornir's secrets management features (e.g., environment variables or HashiCorp Vault) instead.

3

What tools does the server expose?

Tools include `list_all_hosts`, numerous NAPALM getters (e.g., `get_facts`, `get_interfaces`, `get_config`, `get_bgp_neighbors`), and `send_command` for read-only command execution. Availability depends on device platform and NAPALM driver support.

4

How do I connect an MCP client to the server?

Ensure the server is running, then add a new MCP Server connection in your client with the URL `http://localhost:8000/sse`. The client will automatically discover the available tools.

5

Is this server suitable for production use?

The default configuration stores credentials in plaintext YAML files, which is only recommended for lab/testing environments. For production, modify `nornir_ops.py` and configuration to use a secrets provider (e.g., environment variables or HashiCorp Vault).

Comments

More Other MCP servers