remote-mcp-oauth-github
If you are the rightful owner of remote-mcp-oauth-github and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
A Model Context Protocol (MCP) server for Claude.ai custom integrations, running on Cloudflare Workers with GitHub OAuth authentication.
Cloudflare Workers MCP Server with OAuth
A Model Context Protocol (MCP) server for Claude.ai custom integrations, running on Cloudflare Workers with GitHub OAuth authentication.
Demo(Slide)
https://slide-tubone24.pages.dev/slides/authmcp/1
Features
- ✅ Claude.ai Custom Integration support
- ✅ Full compliance with MCP authentication specification
- ✅ OAuth 2.0 authorization flow (GitHub)
- ✅ Dynamic Client Registration (DCR) for OAuth clients
- ✅ OAuth 2.0 Protected Resource Metadata (RFC 9728)
- ✅ Session management with KV storage
- ✅ Permission-based access control
- ✅ MCP tools for user information, calculations, and GitHub repository access
Architecture
graph TB
subgraph "Claude.ai Platform"
User[User]
Claude[Claude.ai]
MCP[MCP Client]
end
subgraph "Cloudflare Workers"
Worker[MCP OAuth Server]
KV[(KV Storage)]
subgraph "OAuth Endpoints"
Auth["/auth"]
Token["/token"]
Register["/register"]
Callback["/callback"]
end
subgraph "Well-Known Endpoints"
AuthMeta["/.well-known/oauth-authorization-server"]
ResourceMeta["/.well-known/oauth-protected-resource"]
end
subgraph "MCP Endpoints"
MCPHttp["/mcp"]
SSE["/sse"]
end
end
subgraph "External Services"
GitHub[GitHub OAuth API]
GitHubAPI[GitHub API]
end
User --> Claude
Claude --> MCP
MCP --> Worker
Worker --> Auth
Worker --> Token
Worker --> Register
Worker --> Callback
Worker --> AuthMeta
Worker --> ResourceMeta
Worker --> MCPHttp
Worker --> SSE
Worker --> KV
Worker --> GitHub
Worker --> GitHubAPI
Auth --> GitHub
Callback --> GitHub
GitHub --> Callback
Authentication Flow Sequence
sequenceDiagram
participant User
participant Claude as Claude.ai
participant MCP as MCP Client
participant Worker as Cloudflare Worker
participant KV as KV Storage
participant GitHub as GitHub OAuth
User->>Claude: Start conversation with integration
Claude->>MCP: Initialize MCP connection
MCP->>Worker: GET /.well-known/oauth-protected-resource
Worker-->>MCP: Return resource metadata (RFC 9728)
MCP->>Worker: POST /register (Dynamic Client Registration)
Worker->>KV: Store client credentials
Worker-->>MCP: Return client_id & client_secret
Note over MCP: Generate PKCE code_verifier & code_challenge
MCP->>User: Request authorization
User->>Worker: GET /auth?client_id=...&redirect_uri=...&code_challenge=...&code_challenge_method=S256
Worker->>KV: Store state, redirect_uri & code_challenge
Worker->>User: Redirect to GitHub OAuth
User->>GitHub: Authorize application
GitHub->>Worker: GET /callback?code=...&state=...
Worker->>KV: Verify state
Worker->>GitHub: Exchange code for access token
GitHub-->>Worker: Return access token
Worker->>KV: Store session with auth context
Worker->>KV: Store authorization code with PKCE data
Worker->>User: Redirect with auth code
MCP->>Worker: POST /token (Exchange auth code + code_verifier)
Worker->>KV: Validate auth code & client
Worker->>Worker: Verify PKCE: SHA256(code_verifier) == code_challenge
Worker->>KV: Create MCP access token
Worker-->>MCP: Return access token
MCP->>Worker: POST /mcp (with Bearer token)
Worker->>KV: Validate access token
Worker->>KV: Get auth context
Worker-->>MCP: Return MCP response
MCP->>Claude: Provide tool results
Claude->>User: Display results
Setup
1. Prerequisites
- Cloudflare account
- GitHub account
- Node.js 18+
- Wrangler CLI
2. Setup Cloudflare Worker
Login to Cloudflare (if not already logged in)
npx wrangler auth login
Update the worker name in wrangler.toml
if desired
name = "your-mcp-server-name"
3. Create GitHub OAuth App
- Go to GitHub Settings > Developer settings > OAuth Apps
- Create a new OAuth app:
- Application name:
MCP Auth Demo
- Homepage URL:
https://your-worker.workers.dev
- Authorization callback URL:
https://your-worker.workers.dev/callback
- Application name:
- Save the Client ID and Client Secret
4. Create Cloudflare KV Namespace
npx wrangler kv namespace create "OAUTH_KV"
Update wrangler.toml
with the generated ID:
[[kv_namespaces]]
binding = "OAUTH_KV"
id = "your-kv-namespace-id"
5. Configure Environment Variables
Set the following secrets using Wrangler CLI:
# Set GitHub OAuth credentials
wrangler secret put GITHUB_CLIENT_ID
wrangler secret put GITHUB_CLIENT_SECRET
# Set cookie encryption key (generate a random string)
wrangler secret put COOKIE_ENCRYPTION_KEY
# Optional: Restrict access to specific GitHub usernames (comma-separated)
wrangler secret put ALLOWED_USERNAMES
6. Deploy
# Install dependencies
npm install
# Deploy to Cloudflare Workers
npm run deploy
Claude.ai Configuration
Adding Custom Integration
- Log into Claude.ai (Team/Enterprise plan required)
- Go to Settings > Integrations
- Click "Add Custom Integration"
- Enter the following information:
- Name: MCP Auth Demo
- MCP Server URL:
https://your-worker.workers.dev/mcp
- OAuth Authorization URL:
https://your-worker.workers.dev/auth
- OAuth Token URL:
https://your-worker.workers.dev/token
- Client Registration URL:
https://your-worker.workers.dev/register
Usage
- Start a new conversation in Claude
- Enable the integration
- When prompted, authenticate with GitHub
- MCP tools become available
Available Tools
1. get_user_info
Retrieves authenticated user information.
User: Show my user info
Claude: Using get_user_info tool...
2. calculate
Performs basic arithmetic calculations.
User: Calculate 7 to the power of 8
Claude: Using calculate tool...
3. get_github_repos
Lists user's GitHub repositories.
User: Show my GitHub repositories
Claude: Using get_github_repos tool...
OAuth Endpoints
Well-Known Endpoints
/.well-known/oauth-authorization-server
- OAuth 2.0 Authorization Server Metadata/.well-known/oauth-protected-resource
- OAuth 2.0 Protected Resource Metadata (RFC 9728)
OAuth Flow Endpoints
/auth
- Authorization endpoint/callback
- OAuth callback endpoint/token
- Token exchange endpoint/register
- Dynamic client registration endpoint
MCP Endpoints
/mcp
- HTTP POST endpoint for MCP requests/sse
- Server-Sent Events endpoint for streaming
Development
Local Development
# Start development server
npm run dev
# Generate TypeScript types
npm run cf-typegen
Testing
You can test the MCP server using the Claude Code Inspector:
-
Start the Inspector:
npx @modelcontextprotocol/inspector https://your-worker.workers.dev/mcp
-
Test OAuth 2.0 Metadata Endpoints:
- Visit
https://your-worker.workers.dev/.well-known/oauth-authorization-server
- Visit
https://your-worker.workers.dev/.well-known/oauth-protected-resource
- Verify RFC 9728 compliance
- Visit
-
Test Dynamic Client Registration:
curl -X POST https://your-worker.workers.dev/register \ -H "Content-Type: application/json" \ -d '{ "client_name": "Test MCP Client", "redirect_uris": ["urn:ietf:wg:oauth:2.0:oob"] }'
-
Test OAuth Flow (using Inspector):
- The Inspector will automatically handle the OAuth flow
- Follow the GitHub authentication prompts
- Verify successful token exchange
-
Test MCP Tools: Once authenticated, test the available tools in the Inspector:
get_user_info
- Retrieve authenticated user informationcalculate
- Perform arithmetic operationsget_github_repos
- List GitHub repositories
-
Verify Server Health:
curl https://your-worker.workers.dev/health
The Inspector provides a comprehensive interface for testing MCP servers with OAuth authentication, making it easy to verify all functionality works correctly.
Resources
- MCP Specification
- OAuth 2.0 Protected Resource Metadata (RFC 9728)
- Claude.ai Integrations Documentation
- Cloudflare Workers Documentation
License
MIT License