modelcontextprotocol/example-remote-server
Watch
1
0
Fork
You've already forked example-remote-server
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Improve client.js and curl-examples.sh usability

Browse source 
Fix PKCE implementation, SSE parsing, error handling, and usage clarity.
Add --help flag and improve output messaging for both examples.
This commit is contained in:
Basil Hosmer 2025-10-07 14:36:41 -04:00
commit 7b7aa513f5
No known key found for this signature in database
1 changed files with 328 additions and 272 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/oauth-flow.md
View file

@ -194,18 +194,6 @@ This ensures only the client that initiated the flow can exchange the code, even
---
## Architecture Benefits
The separate server architecture provides:
1. **Standards Compliance**: Follows OAuth 2.0 best practices for resource/authorization server separation
2. **Flexibility**: Auth server can be replaced with Auth0, Okta, or other providers
3. **Scalability**: Auth and MCP servers can scale independently based on load
4. **Security**: Token validation via introspection endpoint (RFC 7662)
5. **Maintainability**: Clear separation of authentication and business logic
---
## References
- [RFC 6749: OAuth 2.0 Framework](https://datatracker.ietf.org/doc/html/rfc6749)