Frontegg

Lightweight, dependency-free, in-memory fake of the Frontegg API over HTTP/JSON. Exercise vendor tokens, user login, user management and tenants with zero cost and zero side effects.

Default port: 4824

Quick start

import { FronteggServer } from "./services/frontegg/src/server.js";

const server = new FronteggServer(4824);
await server.start();
// ... run your app/tests ...
await server.stop();

Point the @frontegg/client SDK at it via FRONTEGG_BASE_URL=http://127.0.0.1:4824. First exchange your vendor credentials for a token:

const res = await fetch("http://127.0.0.1:4824/auth/vendor", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ clientId: "parlel", secret: "parlel" }),
});
const { token } = await res.json(); // use as Bearer on /identity/resources/* routes

Implemented operations

The vendor token and user login endpoints are public. The /identity/resources/* management routes require Authorization: Bearer <token>. State is in-memory and ephemeral; ids are deterministic UUIDs.

Auth

Users (Bearer required)

Tenants (Bearer required)

Service & control endpoints (parlel extensions)

Access via MCP / preview URL

Frontegg is an HTTP service, so in a sandbox it is exposed at its own Daytona preview URL (not via MCP parlel_execute). Use the preview URL from the Connect panel with the preview token header, and set FRONTEGG_BASE_URL to that host.

Surface coverage

This emulator faithfully replicates the API surface most application code and agents exercise. Anything below the supported lines is either an intentional design choice for a fast, zero-cost local emulator (✓ By design) or a candidate for a future release (⟳ Roadmap) — never a silent inaccuracy.

Legend: ✅ fully supported · ◐ accepted (stored, not strictly enforced) · ✓ by design · ⟳ on the roadmap.

FeatureStatus
Vendor token + user login✅ Supported
Users CRUD✅ Supported
Tenants list / create✅ Supported
Deterministic UUIDs + JWT-shaped tokens✅ Supported
Real JWT signing / JWKS verification✓ By design — Structurally faithful tokens; cryptographic verification is skipped for local use
Roles / permissions / feature flags / entitlements◐ Stored, not enforced
MFA / SSO / social login / passwordless flows⟳ Roadmap
Email/SMS delivery (invites, verification)✓ By design — Accepted, never delivered
Token validity / scope enforcement✓ By design — Any non-empty credential is accepted — no real secrets needed
<!-- parlel:testenv:start -->

Configuration — test.env

Copy these into your test.env (used by the bridge sidecar flow). Tokens are Parlel's seeded test credentials — any non-empty value is accepted by the emulator, so you rarely need to change them. Swap in real credentials only when pointing at the live service in prod.env.

FRONTEGG_BASE_URL=http://parlel-bridge:4824
FRONTEGG_CLIENT_ID=parlel
FRONTEGG_API_KEY=parlel
<!-- parlel:testenv:end -->