scim-mcp by chenhunghan - MCP Server

title: System for Cross-domain Identity Management (SCIM) MCP Server emoji: 🌖 colorFrom: pink colorTo: blue sdk: docker app_port: 7860 pinned: false short_description: SCIM 2.0 relay for AI agents to manage identities tags:

building-mcp-track-enterprise

SCIM Relay for Agents

scim-mcp is a SCIM (System for Cross-domain Identity Management) relay for AI agents. This MCP server enables LLMs to manage enterprise user identities and groups through the battle-tested SCIM 2.0 standard (RFC7644). It acts as a privacy first relay between AI agents and service providers (SP) or identity providers (IdP), allowing organizations to provision, de-provision, and manage authorization policies.

Post on Social Media

Demo

screencast

Features

Full SCIM 2.0 user and group lifecycle management with built-in PII masking for GDPR/privacy compliance:

Privacy & Compliance:

PII Masking - Automatically masks sensitive personal data (emails, phone numbers, names, addresses) in LLM responses to minimize PII exposure while maintaining operational utility. Critical for GDPR Article 5 (data minimization) and Article 25 (privacy by design) compliance when AI agents process identity data.

User Operations:

POST - Create users with core and enterprise schema attributes (RFC7644 §3.3)
GET - Retrieve user information (RFC7644 §3.4.1)
PUT - Replace user records entirely (RFC7644 §3.5.1)
PATCH - Update specific user attributes (RFC7644 §3.5.2)
DELETE - Remove users (RFC7644 §3.6)
Deactivation - Disable user accounts by setting active: false

Group Operations:

POST - Create groups (RFC7644 §3.3)
GET - Retrieve group information (RFC7644 §3.4.1)
PUT - Replace group records entirely (RFC7644 §3.5.1)
PATCH - Add/remove users to/from groups for authorization management (RFC7644 §3.5.2)
DELETE - Remove groups (RFC7644 §3.6)

Use Cases

Connect Enterprise App Directly - Manage users and groups directly in your service provider without Azure AD, Okta, or other IdP interfaces
SCIM Endpoint Development & Testing - Validate your SCIM endpoint implementation without setting up Azure AD or Okta
Control MCP Server Access - Use Auth0's inbound SCIM connector to manage which OAuth accounts can access which MCP servers

Demo

On Vercel https://scim-mcp.vercel.app/mcp

On Alpic https://scim-mcp-d8a54d7b.alpic.live/

Architecture

sequenceDiagram
    participant LLM as LLM/AI Agent
    participant MCP as scim-mcp<br/>(MCP Server)
    participant SP as Service Provider<br/>(SCIM Endpoint)
    
    Note over MCP: Credentials stored as<br/>environment variables:<br/>SCIM_API_TOKEN<br/>SCIM_API_BASE_URL
    
    LLM->>MCP: MCP Tool Request<br/>(e.g., create-user)
    Note over LLM,MCP: No credentials exposed to LLM
    
    MCP->>MCP: Retrieve credentials<br/>from environment
    
    MCP->>SP: SCIM API Request<br/>Authorization: Bearer {token}
    
    SP->>MCP: SCIM Response
    
    MCP->>LLM: MCP Tool Response

Setup

Codex

[mcp_servers.scim]
command = "npx"
args = ["-y", "mcp-remote@latest", "https://scim-mcp-d8a54d7b.alpic.live/", "--header", "x-scim-api-token:${SCIM_AUTH_TOKEN}", "--header", "x-scim-base-url:https://service.provider.scim.base.url"]

Development

First, run the development server:

npm run dev