Skip to main content
Glama

Juniper Mist MCP Server

⚠️ Juniper now offers an official MCP server for Mist.

Juniper has released their own MCP server at https://mcp.ai.juniper.net/mcp/mist with native integration for Claude Desktop.

We recommend using the official upstream server instead of this project. See the Juniper Mist MCP documentation for setup instructions.

This community project remains available for use cases that require multi-org MSP routing, write tools, or HTTP transport — features not yet covered by the upstream server. However, for standard single-org monitoring and troubleshooting, the official server is the better choice going forward.

MCP server for managing Juniper Mist networks with AI assistants. Monitor, troubleshoot, and configure customer networks through natural language — built for MSPs managing multiple organizations across regions.

Input: Natural language via Claude Desktop (or any MCP client) Output: Device stats, client data, alarms, WLAN configs, inventory, and more

  AI Assistant  ──▶  MCP Server  ──▶  Juniper Mist API
  (Claude, etc.)     (multi-org       (US, EU, GC1, GC2,
                      routing)         APAC regions)

Installation

pip install juniper-mist-mcp

Option 2: Install with pipx (isolated environment)

pipx install juniper-mist-mcp

Verify installation

juniper-mist-mcp --help

Related MCP server: domotz-mcp

Setup

1. Get a Mist API Token

  1. Log in to the Mist portal at https://admin.mist.com

  2. Navigate to Organization → Settings → API Tokens

  3. Create a new API token with appropriate scope

2. Configure Organizations

Create a .env file with your organization credentials:

# US-based org (default region)
MIST_TOKEN_acme_corp=your_token_here

# EU-based org
MIST_TOKEN_euro_client=your_token_here
MIST_REGION_euro_client=api.eu.mist.com

# Government org
MIST_TOKEN_gov_agency=your_token_here
MIST_REGION_gov_agency=api.gc1.mist.com

Each org needs a MIST_TOKEN_<ORGNAME> variable. Region is optional — defaults to US (api.mist.com).

Supported Regions

Region

Endpoint

US (default)

api.mist.com

EU

api.eu.mist.com

Government Cloud 1

api.gc1.mist.com

Government Cloud 2

api.gc2.mist.com

Asia Pacific

api.ac2.mist.com


Usage

Run in stdio mode (Claude Desktop)

# Read-only mode (default — 10 tools)
juniper-mist-mcp

# With write tools enabled (14 tools)
juniper-mist-mcp --enable-write-tools

Run in HTTP mode (centralized deployment)

# Default port 8000
juniper-mist-mcp --transport=http

# Custom host and port
juniper-mist-mcp --transport=http --host=0.0.0.0 --port=8080

# HTTP + write tools
juniper-mist-mcp --transport=http --port=8080 --enable-write-tools

Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "juniper-mist": {
      "command": "juniper-mist-mcp",
      "env": {
        "MIST_TOKEN_acme_corp": "your_token_here",
        "MIST_REGION_acme_corp": "api.mist.com"
      }
    }
  }
}

Or if using a .env file alongside the install:

{
  "mcpServers": {
    "juniper-mist": {
      "command": "juniper-mist-mcp",
      "args": ["--env-file", "/path/to/your/.env"]
    }
  }
}

Verify it works

In your AI assistant, ask it to list organizations. The mist_list_orgs tool should return your configured orgs:

[
  {"name": "acme_corp", "region": "api.mist.com", "has_token": true},
  {"name": "euro_client", "region": "api.eu.mist.com", "has_token": true}
]

Available Tools

Read Tools (always available)

Tool

What it does

mist_list_orgs

List configured customer orgs and regions

mist_get_device_stats

AP, switch, and gateway statistics

mist_get_sle_summary

Service Level Experience metrics (throughput, latency, coverage)

mist_get_client_stats

Wireless client connection and bandwidth data

mist_get_alarms

Infrastructure, security, and Marvis AI alarms

mist_get_site_events

Config changes, user activities, system alerts

mist_list_wlans

WLAN/SSID profiles and security settings

mist_get_rf_templates

Radio frequency templates (channel, power, band)

mist_get_inventory

Device inventory with type/status/site filters

mist_get_device_config_cmd

Generated CLI config commands for a device

Write Tools (opt-in with --enable-write-tools)

Tool

What it does

mist_update_wlan

Modify WLAN/SSID configurations

mist_manage_nac_rules

Create, update, or delete 802.1X NAC rules

mist_manage_wxlan

Manage WXLAN microsegmentation policies

mist_manage_security_policies

Create, update, or delete security policies

Every tool takes an org parameter to route to the right customer org and region.


Safety Model

Four layers prevent accidental network changes:

  1. Read-only by default — write tools aren't registered unless you opt in

  2. CLI flag — must explicitly pass --enable-write-tools

  3. MCP annotations — read tools tagged readOnlyHint, write tools tagged destructiveHint so the AI asks for confirmation

  4. Pre-flight validation — UUID format checks and required field validation before any API call


CLI Reference

Flag

Description

Default

--enable-write-tools

Enable 4 write tools for network modification

Disabled

--transport

Transport protocol: stdio or http

stdio

--host

Host for HTTP transport

0.0.0.0

--port

Port for HTTP transport

8000

--env-file

Path to .env file

.env


Troubleshooting

Error

Fix

Configuration file not found: .env

Create a .env file from .env.example

Organization 'X' is not configured

Check MIST_TOKEN_<ORGNAME> in your .env (case-sensitive)

Unknown region 'X'

Use a supported region endpoint (see table above)

Failed to fetch orgs: 401

Token is invalid or expired — regenerate in Mist portal

Write tools not appearing

Start server with --enable-write-tools flag


Contributing

Build from source

git clone https://github.com/vahagn-madatyan/juniper-mist-mcp.git
cd juniper-mist-mcp

# Create virtual environment
python -m venv .venv
source .venv/bin/activate  # or .venv\Scripts\activate on Windows

# Install with dev dependencies
pip install -e ".[dev]"

# Run from source
python -m mist_mcp.server --help

Run tests

pytest tests/ -v
pytest tests/ -v --tb=short
pytest tests/test_config.py -v

Project structure

mist_mcp/
├── __init__.py        # Package version
├── __main__.py        # Module entry point
├── server.py          # MCP server, tool definitions, CLI
├── config.py          # .env loader, org routing, region validation
└── session.py         # Mist API session management

Architecture

  • FastMCP — MCP server framework handling tool registration, lifespan, and transport

  • mistapi SDK — Juniper Mist Python SDK for all API calls

  • Multi-tenant routing — each tool call includes an org parameter; the server maintains separate authenticated sessions per org

  • Conditional tool registration — write tools are only registered when --enable-write-tools is passed, using mcp.add_tool() with MCP annotations

Making a release

Releases are published to PyPI automatically via GitHub Actions when a version tag is pushed:

# Update version in pyproject.toml and mist_mcp/__init__.py
# Commit the version bump
git tag v0.2.0
git push origin v0.2.0

The CI pipeline builds the distribution, runs tests, publishes to TestPyPI on every push, and publishes to PyPI on tags matching v*.


License

Apache License 2.0

Available Tools

10 tools
mist_get_alarmsA
Read-only

Get alarms for an organization.

Returns alarms from the specified organization, including infrastructure, security, and Marvis AI-driven detections.

Inputs: org (required), end, limit, start, +1 more. Returns: object

mist_get_client_statsB
Read-only

Get client statistics for an organization.

Returns statistics for wireless clients in the specified organization, including connection details, bandwidth, and session information.

Inputs: org (required), limit, duration. Returns: object

mist_get_device_config_cmdA
Read-only

Get generated CLI configuration commands for a device.

Returns the generated CLI configuration for a specific device in a Mist site. The configuration includes the complete device-specific commands needed to configure the device based on its settings and policies.

Note: site_id and device_id are Mist IDs (UUIDs), not names. You can obtain site_id from mist_get_site_events or by listing sites, and device_id from mist_get_inventory.

Inputs: org (required), site_id (required), device_id (required), sort. Returns: object

mist_get_device_statsB
Read-only

Get device statistics for an organization.

Returns statistics for all devices in the specified organization, including APs, switches, gateways, and other network devices.

Inputs: org (required), duration. Returns: object

mist_get_inventoryA
Read-only

Search device inventory in an organization.

Returns devices from the organization inventory that match the specified filters. Supports filtering by device type, status, site, and name.

Inputs: org (required), name, type, limit, +3 more. Returns: object

mist_get_rf_templatesA
Read-only

List RF templates in an organization.

Returns all RF (Radio Frequency) templates configured in the specified organization, including channel, transmit power, and band settings.

Inputs: org (required), page, limit. Returns: object

mist_get_site_eventsA
Read-only

Get events for an organization or site.

Returns system events from the specified organization or site, including configuration changes, user activities, and system alerts.

Inputs: org (required), end, limit, start, +1 more. Returns: object

mist_get_sle_summaryA
Read-only

Get Service Level Experience (SLE) summary for a site.

Returns the SLE summary for a specific site, including metrics for throughput, latency, coverage, and capacity.

Inputs: org (required), site_id (required). Returns: object

mist_list_orgsA
Read-only

List configured customer organizations and their Mist regions.

Returns a list of organizations from the configuration, including the organization name, region, and whether a token is present.

Returns: List of dicts with keys: name, region, has_token.

Inputs: no named parameters. Returns: result

mist_list_wlansA
Read-only

List WLAN profiles in an organization.

Returns all WLAN profiles (SSIDs) configured in the specified organization, including security settings, broadcasting configuration, and access policies.

Inputs: org (required), page, limit. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Mist resource or metric (organizations, device stats, SLE summary, client stats, RF templates, alarms, site events, WLANs, inventory, device config). There is no functional overlap or ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent 'mist_[verb]_[noun]' pattern in snake_case. Two use 'list' for enumeration and eight use 'get' for specific data, maintaining a clear and predictable naming convention.

    Tool Count5/5

    Ten tools is an appropriate scope for a Mist network management MCP server. It covers key read-only operations without being excessive or too minimal.

    Completeness3/5

    The tool set is entirely read-only, lacking create, update, or delete operations. Additionally, basic entity listings like sites or detailed device endpoints are missing, which limits full lifecycle coverage for the Mist domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers