Skip to content

Support externally sourced JWT in Auth header from MCP client #917

@johnkwaters

Description

@johnkwaters

I have been using the MCP OAuth support and even DCR, which is awesome.
But there are other scenarios where we are building in using MCP Servers into some host that doesn't understand this protocol, or that doesn't have an OAuth 2.1 server available, but where we might have obtained a valid access token (Jwt Bearer token) through some other means.
In this case I would like to add this to the MCP client so that it can be passed in the Authorization: Bearer {jwt} header on each call.
Is there a good way to do this - and if not can there be a way that feel intuitive to provide that kid of 'out of band' auth support for the MCP calls?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions