LightNow MCP 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.

- Keep MCP access organized in personal and organization profiles.
- Connect localstdioand remote Streamable HTTP servers through one entry.
- Resolve credentials on the user's machine instead of embedding them in MCP client configuration.
- Apply profile and policy changes without rebuilding every client setup.
- Observe client, profile, server health, and tool usage. Tool arguments are captured by default with credential-like fields redacted and can be disabled; tool results and resolved secrets are never collected.

The installed command remainslightnow-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 asgithub__create_issueidentify both the upstream server and its tool and avoid collisions when several servers use the same tool name.

The proxy supports the official MCP2026-07-28revision with stateless, per-request protocol metadata andserver/discover. It keeps automatic compatibility with handshake-era servers and clients through2025-11-25.

- Python 3.11 or higher
- pipx
- aLightNow account
- the LightNow CLI

pipx install lightnow-cli lightnow login

brew tap lightnow-ai/tap brew install lightnow-proxy

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-proxy

lightnow-proxy --health lightnow-proxy --health --json

lightnow-proxy --config ~/.lightnow/lightnow-proxy/codex.yaml --health lightnow-proxy --config ~/.lightnow/lightnow-proxy/codex.yaml --health --json

When telemetry is enabled, active health checks and runtime events are sent to the LightNow Control Plane. Tool-call arguments are captured by default and can be disabled independently in the Local Proxy settings. Credential-like fields are redacted before transmission. The proxy also sends device presence immediately at startup and every two minutes. The Control Plane can then show which devices, clients and profiles are active, healthy, degraded, or failing, along with CLI/Proxy versions and update status. Tool results, resolved LightNow secrets, unredacted authorization values, network addresses, hardware identifiers and local paths are not stored. Credential-like argument fields, including authorization headers, are replaced with[REDACTED]before transmission.

Vault providers configured for runtime resolution are resolved on this host, after Registry API has returned a provider reference without credentials or a secret value. HashiCorp Vault Proxy auto-auth on127.0.0.1:8200is the default. Provider-specific loopback listeners can be mapped underruntime_secrets.providersin the generated YAML; LightNow CLI preserves these non-secret mappings on subsequent syncs. The optional OS-keyring path is available withlightnow-proxy[keyring]. Resolution failures are fail-closed and plaintext values are never added to the tool-schema cache.

Detailed setup guides, examples, diagrams, supported client paths, telemetry behavior and troubleshooting live in the LightNow docs:

- Connect MCP clients
- CLI reference
- Release process

uv venv uv pip install -e .[dev] make test

uv run lightnow-proxy --config config.example.yaml

uv run lightnow-proxy --config config.example.yaml --transport stdio

Run a local health check against the example config:

uv run lightnow-proxy --config config.example.yaml --health

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB