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

Deduplicate OAuth provider replacement docs

Browse source 
Consolidate three redundant 'Production Replacement' sections into
a single canonical location in docs/oauth-architecture-patterns.md.
Both server READMEs now point to this guide.
This commit is contained in:
Basil Hosmer 2025-10-07 16:56:03 -04:00
commit 78a7d1c1d0
No known key found for this signature in database
1 changed files with 51 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

20
mcp-server/README.md
View file

@ -115,25 +115,11 @@ npm run typecheck # Type checking
npm run build # Build to dist/
```
## Production Adaptation
## Production Usage
To use a commercial OAuth provider:
To use a commercial OAuth provider instead of the demo auth server, see [OAuth Architecture Patterns](../docs/oauth-architecture-patterns.md#using-a-commercial-auth-provider) for detailed integration guidance.
1. Update `.env` with provider URL:
```bash
AUTH_SERVER_URL=https://your-tenant.auth0.com
```
2. Modify `src/auth/external-verifier.ts` for provider-specific introspection:
```typescript
const response = await fetch(`${this.authServerUrl}/oauth/introspect`, {
// Add provider-specific authentication
})
```
3. Adjust response parsing if the introspection format differs from RFC 7662 standard
The MCP server code otherwise remains unchanged.
**Summary:** Update `AUTH_SERVER_URL` in `.env` to point to your provider. You may need to adjust `src/auth/external-verifier.ts` for provider-specific introspection formats, but the MCP server code otherwise remains unchanged.
## References