# rustmistmcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/mechubsec/rustmistmcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rustmistmcp

## Description
HPE Juniper Mist MCP server: scoped, audited, two-person change control. Rust.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What rustmistmcp MCP server does

rustmistmcp MCP server exposes selected HPE Juniper Mist cloud operations to MCP clients. The target operating area includes organizations, sites, access points, switches, gateways, WLANs, clients, service-level expectations, events, alarms, audit records, radio-resource management, rogue detection, firmware, policy, guest access, webhooks, floor plans, and Marvis. The repository intentionally uses a curated catalog instead of registering the very large generated tool set found in the related Python project.

The server is designed for a multi-tenant cloud control plane. An organization-scoped request can span many sites and devices, so authorization scope, response bounds, attribution, and auditability are treated as core behavior. Mist-specific REST handling lives in this repository, while authentication, audit primitives, transport, runtime behavior, inventory, and change-set mechanics come from the shared `mecmcp` foundation.

## How it works

Mist uses regional API endpoints, including `api.mist.com`, `api.eu.mist.com`, and `api.gc1.mist.com`. The operator must configure the correct region; the server does not infer it. Version 1 authenticates with Mist API tokens sent in the `Authorization: Token <token>` header. OAuth credentials are not supported, and HTTP Basic authentication is intentionally excluded.

At startup, each allowlisted organization is queried with `listOrgSites` so site-scoped requests can be checked against known sites. A background refresh repeats that discovery every 300 seconds by default. The interval can be changed with `--site-refresh-interval-secs`, and `0` limits discovery to startup. Known sites are retained when a refresh fails or reaches the tracked-site limit.

## Setup and configuration

The server can run without a credential, but that mode uses a blocked client that performs no network I/O and returns the `LIVE_MIST_BLOCKER` refusal. A working deployment therefore needs a Mist API token, configured organization and site scope, and the appropriate regional Mist origin. The excerpt does not document the complete configuration file, command-line option set, or environment-variable names.

The repository includes Docker, archive, systemd, and LXC deployment assets, but labels them pre-release packaging. Its OCI image uses a digest-pinned Rust build stage and a digest-pinned distroless Debian 13 runtime, runs as UID/GID `65532`, and contains no shell or package manager.

## Tools and capabilities

The live read-only acceptance run reached a real Mist organization and verified three operations: `get_mist_self` (`getSelf`), `get_mist_org` (`getOrg`), and `list_mist_sites` (`listOrgSites`). The catalog-bound client also validates operation inputs and binds opaque pagination cursors to the configured origin.

Batch-1 mutations cover create and update operations for networks, services, service policies, gateway templates, and device profiles. These operations are available only through the plan, digest, approve, apply, and verify change lifecycle. They are not equivalent to unrestricted direct writes.

## Limitations and notes

rustmistmcp MCP server is an unofficial community project and does not claim endorsement by Hewlett Packard Enterprise or Juniper Networks. Read-only live-tenant acceptance has passed, but full packaging acceptance has not: TLS validation, Host and Origin enforcement, anonymous-request rejection, and bad-bearer rejection remain outside the completed test run.

The server does not yet perform a `/api/v1/self` identity probe during startup. No live-tenant mutation has been applied. Delete operations and assignment or unassignment of `mist_configured` device profiles are not available. The documented read acceptance used one organization, one token, a loopback endpoint, and no TLS, so it should not be treated as production packaging validation.

_Full upstream README: https://allmcps.com/mcp/rustmistmcp/readme_