LightNow MCP Proxy MCP server
io.github.lightnow-ai/lightnow-proxy·v1.9.1·2 starsConnect your AI clients to your MCP servers—securely managed in one place.
2 stars40 downloads/wk
Reviews
Write oneNobody has reviewed LightNow MCP Proxy yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
LightNow MCP Proxy tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- Code scan16 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How LightNow MCP Proxy compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,243 servers
- GitHub stars
- 2
- more than 75% of 28,706 servers
- Downloads a week
- 40
- more than 30% of 12,306 servers with a package
Install LightNow MCP Proxy in Claude Code, Cursor or VS Code
claude mcp add lightnow-proxy -- uvx lightnow-proxy
What the publisher says
From the LightNow MCP Proxy repository's README, as published. We do not edit it. Read it on GitHub
LightNow MCP Proxy
<!-- mcp-name: io.github.lightnow-ai/lightnow-proxy -->
Connect your AI clients to your MCP servers—securely managed in one place.
The LightNow MCP Proxy is the local runtime behind LightNow profiles. Connect Codex, Claude Desktop, Cursor, VS Code, or Antigravity once, then manage the MCP servers available to that client in LightNow instead of copying server configuration and secrets into every tool.
client configuration.
- Keep MCP access organized in personal and organization profiles.
- Connect local stdio and remote Streamable HTTP servers through one entry.
- Resolve credentials on the user's machine instead of embedding them in MCP
captured by default with credential-like fields redacted and can be disabled; tool results and resolved secrets are never collected.
- Apply profile and policy changes without rebuilding every client setup.
- Observe client, profile, server health, and tool usage. Tool arguments are
The installed command remains lightnow-proxy. It runs locally, uses the identity-bound LightNow CLI session, resolves the selected profile, and routes tool and resource requests to the profile's MCP servers.
Capabilities come from your LightNow profile
The proxy deliberately does not ship demo tools. Its MCP capabilities are the real tools and resources exposed by the servers selected in the active LightNow profile, so the list differs between teams and clients. Names such as githubcreateissue identify both the upstream server and its tool and avoid collisions when several servers use the same tool name.
The proxy supports the official MCP 2026-07-28 revision with stateless, per-request protocol metadata and server/discover. It keeps automatic compatibility with handshake-era servers and clients through 2025-11-25.
Install
Requirements:
- Python 3.11 or higher
- pipx
- a LightNow account
- the LightNow CLI
pipx install lightnow-cli
lightnow loginInstall the proxy with Homebrew:
brew tap lightnow-ai/tap
brew install lightnow-proxyOr install it with pipx:
pipx install lightnow-proxyOr install it with uv:
uv tool install lightnow-proxyThe Python package installs the lightnow-proxy command used by MCP clients.
For repository-local development:
uv tool install --from . lightnow-proxyUpdate supported CLI and Proxy installations through the LightNow CLI:
lightnow update --check
lightnow updateHomebrew, pipx and uv are managed. The proxy only reports its observed version and update state in metadata-only heartbeats; it never invokes a package manager or delays MCP startup to check for releases.
Configure a Client
Use the LightNow CLI. It writes the client MCP entry and the per-client Local Proxy config.
lightnow sync --client codex --local-proxy
lightnow sync --client claude-desktop --local-proxy
lightnow sync --client cursor --local-proxy
lightnow sync --client vscode --local-proxy
lightnow sync --client antigravity --local-proxyRestart the MCP client after syncing.
Multiple accounts and organizations
Use a distinct --connection alias for every account, organization or profile that should appear in the same MCP client:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
LightNow MCP Proxy: common questions
- Is LightNow MCP Proxy MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the LightNow MCP Proxy safety report
- How do I install LightNow MCP Proxy?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does LightNow MCP Proxy need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is LightNow MCP Proxy maintained?
- The last commit was 8 days ago (2026-10-28). The latest release is v1.9.1.
- How does LightNow MCP Proxy compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,243 servers); github stars 2 (more than 75% of 28,706 servers); downloads a week 40 (more than 30% of 12,306 servers with a package). Full comparison.