Integrations & runtime profiles
LightNow integrations are managed through Runtime Profiles. A profile groups the MCP server configuration that belongs to one usage context, such as your personal setup, an engineering team, or an organization-wide approved set.
Use Runtime Profiles when you want to:
- keep client configuration separate by context,
- store secret metadata without exposing plaintext values,
- limit a profile to specific MCP servers, and
- make organization profiles available only to the right tenant roles.
You can manage profiles in the LightNow app under Settings -> Integrations.
Profile behavior
Every account has a default profile. The default profile always exists and cannot be deleted.
Plan boundaries:
- Free users can use the default profile only.
- Standard users can create multiple personal profiles.
- Enterprise tenants can manage organization Runtime Profiles with role availability.
- Enterprise Dedicated supports the same profile model inside an isolated or dedicated deployment.
Organization profiles can define which roles may use them. Tenant owners and admins manage tenant Runtime Profiles and stored config or secret metadata. Members can use active tenant profiles only when the profile allows the member role.
Server allowlists
A Runtime Profile can optionally define a server allowlist. When an allowlist is present, that profile can be used only with the listed MCP servers.
If no allowlist is set, the profile is available for all servers in that scope. This is useful for a broad default profile. Use allowlists for team-specific contexts, sensitive tools, or curated organization profiles.
Config and secrets
Runtime Profiles store client configuration and secret metadata for MCP servers. For example, a profile can hold transport settings, command or URL details, environment variable names, headers, and argument metadata.
Secret list responses expose metadata only. Plaintext secret material is used only when a user or approved runtime explicitly needs a runnable configuration.
For local MCP clients, profiles can be used in two ways:
- Local Proxy mode: the client contains one LightNow entry. The Local Proxy fetches the profile and resolves secrets at runtime.
- Direct sync mode: the CLI writes the profile directly into the client configuration. Plaintext secret export requires explicit confirmation and can be controlled by policy.
Typical workflow
- Open Settings -> Integrations.
- Use
defaultor create a new Runtime Profile if your plan allows it. - Add a clear label and description so users understand the profile context.
- For organization profiles, choose the allowed roles.
- Optionally restrict the profile to specific MCP servers.
- Open a server detail page and save integration config or secret metadata against the selected profile.