Skip to content

Supporting Azure Identity for Authentication #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

SolomonTomer
Copy link

For MCP servers that rely on Azure identity for authentication (MSAL, MISE, etc), this PR adds support for interactive login when the local MCP proxy is starting, sending the generated JWT token for the given audience, in every request.
This enables remote HTTP MCP servers to fully authorize Azure tokens within each request.

@geelen
Copy link
Owner

geelen commented Jul 4, 2025

Hmm, this is a pretty heavy change to support a single auth strategy. But I've enabled pkg.pr.new builds so if you fix the conflicts you should get a URL you can do some testing with. I'd love to see a little screencast of what this enables..

My only thought to make this less invasive would be something like adding a --generate-env or --token-cmd flag to mcp-remote, and then a new standalone CLI like npx generate-azure-tokens or something. So you make mcp-remote know basically nothing about azure, it just has some way of shelling out to a custom command that does? Idk if that would work though...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants