Juniper Mist MCP integration for AI agents.
Connect AI agents to Juniper Mist through 3 structured actions, including get self, list org sites, and list site devices. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Juniper Mist integration exposes
The Juniper Mist Agent App exposes 3 provider-backed actions for security and developer tools work. Its current contract lets an authorized agent get the authenticated juniper mist administrator profile and accessible organizations or sites, list sites in a juniper mist organization with optional pagination, and list devices in a juniper mist site with optional type, name, and pagination filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Juniper Mist account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Juniper Mist capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_selfREADGet the authenticated Juniper Mist administrator profile and accessible organizations or sites.
list_org_sitesREADList sites in a Juniper Mist organization with optional pagination.
INPUTS: orgId / limit / page
list_site_devicesREADList devices in a Juniper Mist site with optional type, name, and pagination filters.
INPUTS: siteId / type / name / limit / page
INPUT CONTRACTS
Know what the action needs before it runs.
list_org_sites
orgIdREQUIRED- Juniper Mist organization ID.
limitOPTIONAL- Maximum number of records to return.
pageOPTIONAL- One-based page number to request.
list_site_devices
siteIdREQUIRED- Juniper Mist site ID.
typeOPTIONAL- Juniper Mist device type filter.
nameOPTIONAL- Device name filter.
limitOPTIONAL- Maximum number of records to return.
pageOPTIONAL- One-based page number to request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Self
Get the authenticated Juniper Mist administrator profile and accessible organizations or sites. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_selfVerify with List Org Sites
List sites in a Juniper Mist organization with optional pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_org_sitesSAFETY BOUNDARY
Operate Juniper Mist with explicit limits
- Authorize Juniper Mist with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Juniper Mist data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Juniper Mist rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Juniper Mist task completed successfully.
CONNECTION MODEL
API key
Juniper Mist API token sent with the Authorization: Token header. Create it from the Mist portal API Token page: https://api-class.mist.com/rest/createapitoken/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Juniper Mist.