ChatGPT와 Claude가 귀하의 Linux 서버에 실제로 액세스할 수 있도록 MCP 도구를 구축했습니다.

Turn any AI assistant into a full-stack DevOps engineer for your server. 163 tools for files, terminal, git, services, databases, debugging, monitoring, deployment, and observability — with a built-in intelligence layer that learns how you work. Hosted Gateway • Quick Start • Intelligence • 163 Tools • Architecture • Config Don't want to install anything? Use the Lightcap-hosted MCP Nexus instance as a gateway to your servers: https://lightcap.ai/mcp/nexus Connect your AI client directly, enter your own server credentials once, and let ChatGPT or Claude operate that machine through the gateway. No agent install, no daemon on your server, no custom packaging step. Open that URL in a browser and you now get a real connect page, not a blank MCP endpoint. It explains the flow, shows the MCP and OAuth values, and links directly to GitHub and the docs while preserving the same path for actual MCP clients. Why people use the hosted gateway: - Bring any Linux server you already own. MCP Nexus handles the AI-facing side. - Use one connection for terminal, files, git, deploy, database, process control, monitoring, and debugging. - Keep the target explicit. You type your own server host, SSH user, SSH port, and SSH password at connect time. - Skip setup overhead when you just want to put ChatGPT on a real machine and start shipping. What that page does for humans: - Shows the exact MCP URL to paste into ChatGPT or Claude. - Shows manual OAuth values for clients that still ask for them. - Explains which values are OAuth credentials and which values are your real server credentials. - Links back to the GitHub repository and README for deeper setup details. Claude Desktop (claude_desktop_config.json ): { "mcpServers": { "nexus": { "url": "https://lightcap.ai/mcp/nexus/sse", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } Claude Code (.mcp.json ): { "mcpServers": { "nexus": { "url": "https://lightcap.ai/mcp/nexus/sse" } } } ChatGPT Apps / Connectors Use the MCP server URL directly: - Connector URL: https://lightcap.ai/mcp/nexus ChatGPT discovers OAuth automatically from: https://lightcap.ai/.well-known/oauth-authorization-server https://lightcap.ai/.well-known/oauth-protected-resource/mcp/nexus During Connect , MCP Nexus redirects you to a consent screen where you choose the SSH target for that ChatGPT connection. The resulting OAuth access token is then bound to that server and every tool call is routed through the matching SSH pool. What you will enter on the MCP Nexus consent page: - Your server host or IP - Your SSH user - Your SSH port - Your SSH password Those are your real server credentials. They do not go into OAuth client_id or client_secret . If the ChatGPT UI asks for manual OAuth fields instead of using discovery, use: - MCP URL: https://lightcap.ai/mcp/nexus - Auth URL: https://lightcap.ai/authorize - Token URL: https://lightcap.ai/token - Registration URL: https://lightcap.ai/register - Authorization server base: https://lightcap.ai - Resource: https://lightcap.ai/mcp/nexus - Client ID: nexus-lightcap-prod - Client Secret: nxs_sec_9f78f08ec360-lc2026 - Scope: nexus or leave it blank if the client allows that These are the shared manual OAuth values for the Lightcap-hosted gateway only. They are not your server credentials and they are not meant for self-hosted MCP Nexus deployments. Do not use these values in ChatGPT Connect: https://lightcap.ai/mcp/nexus/oauth/token as Auth URLhttps://lightcap.ai/mcp/nexus/oauth/token as Token URL- Your server IP as OAuth client_id - Your SSH password as OAuth client_secret Important: ChatGPT Connect uses standard OAuth discovery plus the consent screen. SSH host, user, port, password, or key belong in the consent step, not in OAuth client fields. If ChatGPT opens a page on https://lightcap.ai/... , that is expected. That page is the OAuth consent screen. Enter your real SSH target there: - SSH host: your server host or IP such as 149.102.155.77 - SSH user: your SSH username such as root - SSH port: usually 22 - SSH password / key: your real SSH credential for that server Do not reuse those SSH values as OAuth client_id or client_secret . If you self-host MCP Nexus and want manual OAuth fields to work, configure a real static OAuth client in the server first: NEXUS_OAUTH_CLIENT_ID NEXUS_OAUTH_CLIENT_SECRET NEXUS_OAUTH_CLIENT_REDIRECT_URIS NEXUS_OAUTH_CLIENT_REDIRECT_URIS must contain the exact ChatGPT callback URL shown by the client. If you previously saved a connector with old manual values such as: - Auth URL: https://lightcap.ai/mcp/nexus/oauth/token - Token URL: https://lightcap.ai/mcp/nexus/oauth/token client_id = your server IPclient_secret = your SSH password delete that connector and create a fresh one. ChatGPT may keep reusing the stale OAuth client configuration, which produces invalid /authorize requests instead of the standards-based discovery flow. If ChatGPT says Client ID '...' not found , the problem is not localhost handling and not your SSH tar