juniper-mist-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@juniper-mist-mcp show alarms for acme_corp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Option 1: Install from PyPI (recommended)
pip install juniper-mist-mcpOption 2: Install with pipx (isolated environment)
pipx install juniper-mist-mcpVerify installation
juniper-mist-mcp --helpRelated MCP server: domotz-mcp
Setup
1. Get a Mist API Token
Log in to the Mist portal at https://admin.mist.com
Navigate to Organization → Settings → API Tokens
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.comEach org needs a MIST_TOKEN_<ORGNAME> variable. Region is optional — defaults to US (api.mist.com).
Supported Regions
Region | Endpoint |
US (default) |
|
EU |
|
Government Cloud 1 |
|
Government Cloud 2 |
|
Asia Pacific |
|
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-toolsRun 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-toolsConfigure 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 |
| List configured customer orgs and regions |
| AP, switch, and gateway statistics |
| Service Level Experience metrics (throughput, latency, coverage) |
| Wireless client connection and bandwidth data |
| Infrastructure, security, and Marvis AI alarms |
| Config changes, user activities, system alerts |
| WLAN/SSID profiles and security settings |
| Radio frequency templates (channel, power, band) |
| Device inventory with type/status/site filters |
| Generated CLI config commands for a device |
Write Tools (opt-in with --enable-write-tools)
Tool | What it does |
| Modify WLAN/SSID configurations |
| Create, update, or delete 802.1X NAC rules |
| Manage WXLAN microsegmentation 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:
Read-only by default — write tools aren't registered unless you opt in
CLI flag — must explicitly pass
--enable-write-toolsMCP annotations — read tools tagged
readOnlyHint, write tools taggeddestructiveHintso the AI asks for confirmationPre-flight validation — UUID format checks and required field validation before any API call
CLI Reference
Flag | Description | Default |
| Enable 4 write tools for network modification | Disabled |
| Transport protocol: |
|
| Host for HTTP transport |
|
| Port for HTTP transport |
|
| Path to |
|
Troubleshooting
Error | Fix |
| Create a |
| Check |
| Use a supported region endpoint (see table above) |
| Token is invalid or expired — regenerate in Mist portal |
Write tools not appearing | Start server with |
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 --helpRun tests
pytest tests/ -v
pytest tests/ -v --tb=short
pytest tests/test_config.py -vProject 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 managementArchitecture
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
orgparameter; the server maintains separate authenticated sessions per orgConditional tool registration — write tools are only registered when
--enable-write-toolsis passed, usingmcp.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.0The CI pipeline builds the distribution, runs tests, publishes to TestPyPI on every push, and publishes to PyPI on tags matching v*.
License
Available Tools
10 toolsmist_get_alarmsARead-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_statsBRead-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_cmdARead-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_statsBRead-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_inventoryARead-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_templatesARead-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_eventsARead-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_summaryARead-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_orgsARead-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_wlansARead-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
Scored across 10 tools
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.
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.
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.
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
Related MCP Connectors
AI-powered incident management and server monitoring via MCP.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
MCP server providing AI assistants with integration capabilities for QuickBooks Online.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for Juniper networks, enabling AI assistants to execute CLI commands, manage configuration, perform upgrades, and run diagnostics on Junos devices via STDIO transport.28304 PyPI1Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for Domotz network monitoring and management. Enables AI assistants to query network devices, alerts, and topology via the Domotz API.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for network operations that lets AI assistants interact with Cisco/Juniper network devices through safe, well-defined tools like compliance audits and configuration backups.MIT
- AlicenseAqualityDmaintenanceMCP server enabling AI assistants to interact with your LogicMonitor, providing 125 tools for comprehensive monitoring and management operations.7090 npm14AGPL 3.0