It should work, though HPE doesn't name it. The Mist MCP server is a remote HTTP endpoint, and HPE's Mist MCP setup page says any MCP client with remote HTTP support will do. It lists Claude Desktop, Claude Code and VS Code: https://www.juniper.net/documentation/us/en/software/mist/mist-aiops/shared-content/topics/concept/juniper-mist-mcp-claude.html
The headers are what to watch in Copilot Studio. Mist expects Authorization: Bearer with your API token, plus X-Mist-Base-URL for your regional cloud. X-Mist-Org-ID is optional and pins it to one org. The Copilot Studio MCP wizard takes a single API key header. If it won't carry the base URL as well, a custom connector that adds that header is where I'd go next.
Create a read-only org token for it. The Mist token guide covers access levels: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/topics/task/create-token-for-rest-api.html Get your security team to sign off first, because the MCP can hand PSKs and RADIUS secrets to whatever model sits on the other end.
------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
www.wei.com- - -
The comments I post here are my own, and not my employers
If my post was useful accept solution and/or give kudos
Personal Blog:
www.networkfieldnotes.com- - -
------------------------------