You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Legacy MCP Server as Authorization Server (Backwards Compatibility)
92
+
93
+
For backwards compatibility with older MCP implementations, a legacy server is provided that acts as an Authorization Server (following the old spec where MCP servers could optionally provide OAuth):
1. Try RFC 9728 discovery at `/.well-known/oauth-protected-resource` (404 on legacy server)
118
+
2. Fall back to direct OAuth discovery at `/.well-known/oauth-authorization-server`
119
+
3. Complete authentication with the MCP server acting as its own AS
120
+
121
+
This ensures existing MCP servers (which could optionally act as Authorization Servers under the old spec) continue to work while the ecosystem transitions to the new architecture where MCP servers are Resource Servers only.
122
+
91
123
## Manual Testing
92
124
93
125
### Test Discovery
94
126
```bash
95
-
# Test Resource Server discovery endpoint
127
+
# Test Resource Server discovery endpoint (new architecture)
0 commit comments