Support running as a remote MCP server

[wcarson]

New issue?

• I have reviewed the Existing Issues and confirm this is not an existing issue.

Feature

I'm currently working to host the server as a remote MCP server. The challenges have been:

1. Private key auth works, but you lose the user context, which for us would be required for create/update/delete actions.
2. Device auth works locally, but not when run on a server (e.g. "open browser" tries to open a browser on the server)

Would be nice to support auth code flow at a minimum or even the full MCP suggested auth flow with discovery, DCR, etc.

Currently I'm using FastMCP's OAuth Proxy to workaround some of this, but it's a bit messy.

Additional information

No response

[jasonnickels]

This would be fantastic as an enhancement.

[rcxwhiz]

Would also like to see this

[jbknight23]

This is what I need to implement it in production for our org.

[pranav-okta]

This is currently in our backlog, and we'll be working on this sooner.

[jbknight23]

This is currently in our backlog, and we'll be working on this sooner.

Thank you! I'm currently exploring integrating this with Microsoft Copilot Studio for a custom agent that can be shared internally. Please reach out to me if you'd like to collaborate.

[DrFaust92]

I have a working implementation i can contribute we are using internally from a fork. lmk and i can upstream it

[bulebuk]

Any plans to host it for us? Perhaps with dynamic client registration?