Microsoft Entra SCIM MCP Server

Microsoft Entra SCIM is an MCP integration. Microsoft Entra SCIM 2.0 Provisioning API: user and group lifecycle, with a local mock.

Packages and local setup

The published npm package is entra-scim-mcp, version 0.3.0. Its declared MCP transport is stdio.

The package declares ENTRA_TENANT_ID: Directory (tenant) GUID. Required to authenticate against a live tenant; not needed for ENTRA_SCIM_DRY_RUN or ENTRA_SCIM_STATIC_TOKEN, which supply their own placeholder.; ENTRA_CLIENT_ID: App registration (client) GUID. Required to authenticate against a live tenant; not needed for ENTRA_SCIM_DRY_RUN or ENTRA_SCIM_STATIC_TOKEN.; ENTRA_CLIENT_SECRET: Client secret value. For a live tenant set exactly one of ENTRA_CLIENT_SECRET or ENTRA_CLIENT_CERT_PATH; a certificate is preferred for anything long-lived.; ENTRA_CLIENT_CERT_PATH: Path to a PEM holding the certificate and its private key. Set exactly one of ENTRA_CLIENT_SECRET or ENTRA_CLIENT_CERT_PATH.; ENTRA_CLIENT_CERT_PASSWORD: Password for the PEM, if it is encrypted.; ENTRA_SCIM_BASE_URL: Override the SCIM base URL (default https://graph.microsoft.com/rp/scim). Point it at the bundled mock to try the tools without a tenant.; ENTRA_SCIM_STATIC_TOKEN: Use a fixed bearer token instead of Azure AD. Refuses any microsoft.com/microsoft.us host and requires ENTRA_SCIM_BASE_URL; intended for the local mock only.; ENTRA_SCIM_DRY_RUN: Set to 1 to run every client-side validation and return the request that would have been sent, without sending it or acquiring a token..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.