Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Coding agents: Add SCIM directory sync to your app

Let your coding agents guide you into adding Scalekit SCIM provisioning to your application in minutes

Use AI coding agents like Claude Code, GitHub Copilot CLI, Cursor, and OpenCode to add Scalekit’s Modular SCIM directory sync to your applications. Configure the agents to analyze your codebase, apply SCIM patterns, and generate production-ready code for user provisioning, deprovisioning, and lifecycle management. This follows security best practices and reduces implementation time from hours to minutes.

  1. Install the authstack plugin

    Not yet on Claude Code? Follow the official quickstart guide to install it.

    Terminal
    npx @scalekit-inc/cli setup

    For repeated use:

    Terminal
    npm install -g @scalekit-inc/cli
    scalekit setup

    The CLI installs the authstack plugin for you. The plugins guide the coding agent to generate implementation code that matches your project structure.

    Alternative: Enable SCIM plugins via plugin wizard

    Run the plugin wizard to browse and enable available plugins:

    Claude REPL
    /plugins

    Navigate through the visual interface to enable the Modular SCIM plugin.

  2. Generate SCIM implementation

    Use a structured prompt to direct the coding agent. A well-formed prompt ensures the agent generates complete, production-ready SCIM code that includes all required security components.

    Copy the following prompt into your coding agent:

    SCIM implementation prompt
    Guide the coding agent to add Scalekit SCIM directory sync to my app — set up the webhook endpoint to receive SCIM events, validate the webhook signature, and handle user provisioning and deprovisioning events to create, update, and delete users in my database. Code only.

    When you submit this prompt, Claude Code loads the Modular SCIM skill from the marketplace -> analyzes your existing application structure -> generates a webhook endpoint to receive SCIM events from Scalekit -> implements webhook signature validation to prevent unauthorized requests -> creates handlers for user provisioning events (create and update) -> adds deprovisioning logic to delete or deactivate users in your database.

  3. Verify the implementation

    After the coding agent completes, verify that all SCIM components are properly configured:

    Check generated files:

    • Webhook endpoint that receives SCIM events from Scalekit (you may need to set up a .env file with your Scalekit webhook secret)
    • Webhook signature validation to authenticate incoming requests
    • User provisioning handler that creates or updates users in your database
    • Deprovisioning handler that deletes or deactivates users when they are removed from the identity provider

    The SCIM flow should receive webhook events from Scalekit when users are added, updated, or removed in the connected identity provider. Your application should validate each event’s signature, then apply the corresponding change to your user database.

When directory sync is active, user lifecycle changes in the identity provider propagate automatically to your application. Verify that provisioning events correctly create or update users, and that deprovisioning events properly remove or deactivate accounts.