A Model Context Protocol (MCP) server that bridges SCIM 2.0 APIs, allowing MCP clients to interact with SCIM resources through standardized tools.
Tip
🚀 SCIM Playground: Test this SCIM MCP server live in the SCIM Playground before integrating it with your own SCIM server.
Add this configuration to your MCP client's configuration file:
{
"mcpServers": {
"scim": {
"command": "npx",
"args": ["github:limosa-io/mcp-scim", "--stdio"],
"env": {
"SCIM_URL": "https://your-scim-server.com",
"SCIM_AUTH_TOKEN": "your-bearer-token"
}
}
}
}
For HTTP-based MCP clients, add this configuration:
{
"mcpServers": {
"scim": {
"url": "http://localhost:3000/mcp",
"headers": {
"Authorization": "Bearer your-token"
},
"type": "http"
}
}
}
Note: Make sure to start the HTTP server first using
npx github:limosa-io/mcp-scim
(without --stdio flag). Please set the environment variableSCIM_URL
and optionallyPORT
.
Tool | Description |
---|---|
resourcetypes |
List available SCIM resource types |
schemas |
Get SCIM schemas and attribute definitions |
serviceProviderConfig |
Get server capabilities and configuration |
getResources |
Query resources with filtering and pagination |
getResourceById |
Retrieve a specific resource by ID |
createResource |
Create a new SCIM resource |
updateResource |
Update an existing resource (PUT) |
patchResource |
Modify a resource with specific operations (PATCH) |
deleteResource |
Delete a resource |
batchOperations |
Perform multiple operations in a single request |
git clone [email protected]:limosa-io/mcp-scim.git
cd mcp-scim
npm install
npm run dev:watch # Auto-reload on file changes
npm run dev # Run once in development mode
npm run build # Compile TypeScript to JavaScript
npm start # Run the compiled version