Keeper SCIM MCP integration for AI agents.
Connect AI agents to Keeper SCIM through 5 structured actions, including get group, get service provider config, and get user. Review authentication, inputs…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Keeper SCIM integration exposes
The Keeper SCIM Agent App exposes 5 provider-backed actions for security work. Its current contract lets an authorized agent get one keeper scim group by id, get the keeper scim service provider configuration for the connected node, and get one keeper scim user by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Keeper SCIM account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Keeper SCIM capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_groupREADGet one Keeper SCIM group by ID.
INPUTS: id / excludedAttributes
get_service_provider_configREADGet the Keeper SCIM service provider configuration for the connected node.
get_userREADGet one Keeper SCIM user by ID.
INPUTS: id
list_groupsREADList Keeper SCIM groups with optional pagination and excluded member attributes.
INPUTS: startIndex / count / excludedAttributes
list_usersREADList Keeper SCIM users with optional SCIM filter and pagination.
INPUTS: startIndex / count / filter
INPUT CONTRACTS
Know what the action needs before it runs.
get_group
idREQUIRED- Keeper SCIM resource ID returned by the Users or Groups endpoint.
excludedAttributesOPTIONAL- SCIM attributes to exclude, sent as a comma-separated list. Keeper documents this for the members attribute on group queries.
get_user
idOPTIONAL- Keeper SCIM resource ID returned by the Users or Groups endpoint.
list_groups
startIndexOPTIONAL- One-based index of the first SCIM result to return.
countOPTIONAL- Maximum number of SCIM resources to return.
excludedAttributesOPTIONAL- SCIM attributes to exclude, sent as a comma-separated list. Keeper documents this for the members attribute on group queries.
list_users
startIndexOPTIONAL- One-based index of the first SCIM result to return.
countOPTIONAL- Maximum number of SCIM resources to return.
filterOPTIONAL- SCIM user filter, such as id eq "user_id".
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Group
Get one Keeper SCIM group by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_groupVerify with Get Service Provider Config
Get the Keeper SCIM service provider configuration for the connected node. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_service_provider_configSAFETY BOUNDARY
Operate Keeper SCIM with explicit limits
- Authorize Keeper SCIM with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Keeper SCIM data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Keeper SCIM rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Keeper SCIM task completed successfully.
CONNECTION MODEL
API key
Keeper SCIM bearer token sent in the Authorization header. Generate it on the SCIM provisioning setup page in the Keeper Admin Console: https://docs.keeper.io/enterprise-guide/user-and-team-provisioning/automated-provisioning-with-scim/using-scim-api-provisioning
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Keeper SCIM.