Loftlancer

Features

Everything in the product today — grounded in how the studio app and MCP server actually behave.

  • Encrypted at rest

    Secrets are encrypted in the database and masked in the UI until you choose to reveal them.

  • Per-environment targets

    Dev, staging, and production variables live in one project—with clear separation.

  • Projects & organizations

    Group repositories, invite teammates, and control access with org roles.

  • Activity timeline

    See who changed what with an audit-style feed across your workspace.

  • GitHub sign-in

    Authenticate with GitHub—no extra passwords to rotate or forget.

Permissions and audit

Every sensitive operation maps to a canonical action in @loftlancer/actions. The studio API checks requireAction using organization role, optional project grants, and action blocks. When ACTIONS_AUDIT_ENABLED is on, successful and denied operations can be recorded for the timeline.

MCP for agents

The MCP server (apps/mcp, package @loftlancer/mcp) exposes the same action layer over OAuth 2.1. Tools call studio tRPC with the authenticated user — scopes gate which tools a token may invoke; each call still enforces RBAC.