LightNow Local Proxy
OfficialClick on "Install 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., "@LightNow Local Proxyshow me all the tools available from my MCP servers"
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.
LightNow Local Proxy
The LightNow Local Proxy lets local MCP clients use one LightNow-managed MCP entry instead of storing every MCP server configuration and secret in every client.
It runs on your machine, uses your LightNow CLI login session, resolves the MCP
servers enabled for your selected LightNow profile, and forwards tool/resource
requests to local stdio or reachable Streamable HTTP MCP servers.
Install
Requirements:
Python 3.11 or higher
pipxthe 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-proxyRelated MCP server: mcpware
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.
Check the local setup:
lightnow config-status --client codexCheck whether the proxy can resolve the selected profile and reach its upstream MCP servers:
lightnow-proxy --config ~/.lightnow/lightnow-proxy/codex.yaml --health
lightnow-proxy --config ~/.lightnow/lightnow-proxy/codex.yaml --health --jsonWhen telemetry is enabled, active health checks are also sent to LightNow Insights as metadata-only proxy health events. The Insights page can then show which clients and profiles are healthy, degraded, or failing without storing secrets, tool arguments, or response bodies.
More Documentation
Detailed setup guides, examples, diagrams, supported client paths, telemetry behavior and troubleshooting live in the LightNow docs:
Local Development
For contributors working on this repository:
uv venv
uv pip install -e .[dev]
make testRun the proxy with the example config:
LIGHTNOW_PROXY_CONFIG=config.example.yaml uv run lightnow-proxyRun the proxy as a stdio MCP server:
uv run lightnow-proxy --config config.example.yaml --transport stdioRun a local health check against the example config:
uv run lightnow-proxy --config config.example.yaml --healthThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lightnow-ai/lightnow-proxy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server