Is your feature request related to a problem? Please describe.
The current OAuth2-based Authorization concept of spec 2025-03-26 is too complex and not simple to implement for MCP servers. I am referring to discussions in #205.
The authentication concept also violates with the first MCP design principle https://modelcontextprotocol.io/specification/2025-03-26/architecture#design-principles:
"Servers should be extremely easy to build"
This is clearly not the case with the current Authorization Flow.
Describe the solution you'd like
Support Bearer-Authorization with Personal Access Tokens.
A (remote) MCP server could give the user a personal access token (e.g. Github), this access token could be configured with the MCP Client. Use this token as a Authorization: Bearer eyJhbGciOiJIUzI1NiIs...
Is your feature request related to a problem? Please describe.
The current OAuth2-based Authorization concept of spec 2025-03-26 is too complex and not simple to implement for MCP servers. I am referring to discussions in #205.
The authentication concept also violates with the first MCP design principle https://modelcontextprotocol.io/specification/2025-03-26/architecture#design-principles:
"Servers should be extremely easy to build"
This is clearly not the case with the current Authorization Flow.
Describe the solution you'd like
Support Bearer-Authorization with Personal Access Tokens.
A (remote) MCP server could give the user a personal access token (e.g. Github), this access token could be configured with the MCP Client. Use this token as a
Authorization: Bearer eyJhbGciOiJIUzI1NiIs...