This article details a method for securely running an MCP server behind a secret URL, primarily for use with Claude. The approach involves setting up the MCP server on a virtual private server, protected by nginx and a firewall, with the URL path acting as the sole authentication mechanism due to limitations in Claude's connector options. It also addresses potential issues like process spawning and memory pressure from concurrent sessions, and suggests disabling access logs for the secret URL to prevent it from becoming a side-channel leak. AI
IMPACT Provides a method for integrating custom tools with LLM connectors when direct authentication options are limited.
RANK_REASON The article describes a technical workaround for integrating a specific tool (MCP server) with another service (Claude) using existing infrastructure components (nginx, VPS) and addresses practical implementation challenges.
- .claude
- HTTP
- MCP
- MCP Gateway
- nginx
- OAuth
- supergateway
- systemd
- Uncomplicated Firewall
- virtual private server
AI-generated summary · Google Gemini · from 1 sources. How we write summaries →