lighthouse-mcp-oauth
Wraps a Hermes MCP server with OAuth authentication and reverse proxy for secure access via Claude.ai.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lighthouse-mcp-oauthshow me the available tools and resources"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
lighthouse-mcp-oauth
Minimal OAuth 2.1 authorization server + reverse proxy wrapper, Hermes MCP'yi
(mcp-proxy / hermes mcp serve) Claude.ai'nin "Add custom connector" akışına
uyumlu hale getirmek için.
Çalışma şekli
Claude.ai, custom connector eklerken OAuth discovery + Dynamic Client
Registration + Authorization Code (PKCE) akışı bekler. Bu servis bu akışı
minimal şekilde implemente eder ve doğrulanmış istekleri arkadaki
mcp-proxy'ye (varsayılan http://hermes-mcp:8765) proxy'ler.
Tek kullanıcılıdır: /authorize isteği geldiğinde ACCESS_PASSWORD ile
korunan basit bir HTML form gösterilir.
Related MCP server: ticktick-mcp-server
Ortam değişkenleri
PUBLIC_BASE_URL— bu servisin dışarıdan erişilen URL'i (örn.https://mcp.lighthousegroup.net.tr/SECRET)UPSTREAM_BASE_URL— arkadaki mcp-proxy adresi (örn.http://hermes-mcp:8765)ACCESS_PASSWORD—/authorizeformundaki şifre (zorunlu)ACCESS_TOKEN_TTL_SECONDS— access token ömrü (varsayılan 30 gün)
Çalıştırma
docker build -t lighthouse-mcp-oauth .
docker run -d --name mcp-oauth \
--network dokploy-network \
-e PUBLIC_BASE_URL="https://mcp.lighthousegroup.net.tr/SECRET" \
-e UPSTREAM_BASE_URL="http://hermes-mcp:8765" \
-e ACCESS_PASSWORD="..." \
lighthouse-mcp-oauthEndpoint'ler
GET /.well-known/oauth-authorization-server— RFC 8414 metadataGET /.well-known/oauth-protected-resource— protected resource metadataPOST /register— Dynamic Client Registration (RFC 7591), kayıt tutmadan client_id/secret dönerGET|POST /authorize— şifre formu, onaylanırsa authorization code üretir (PKCE)POST /token— code → access_token/*— diğer her şey, geçerliAuthorization: Bearer <token>ile mcp-proxy'ye proxy'lenir
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
- StytchOAuthdev.stytch.mcp
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
Related MCP Servers
- AlicenseAqualityAmaintenance🦞 MCP server for OpenClaw - secure bridge between Claude.ai and your self-hosted OpenClaw assistant with OAuth2 authentication7297 npm184MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables Claude to manage TickTick tasks and projects via OAuth 2.1 with PKCE authentication.10MIT
- AlicenseNot gradedqualityBmaintenanceActs as a secure OAuth 2.0/2.1 proxy gateway for MCP servers, enabling integration with Claude and ChatGPT platforms.19 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server that bridges Claude to an OAuth-protected API, handling OAuth flows and token refresh to enable tools like listing and creating notes.-