Lucid SCIM MCP integration for AI agents.
Connect AI agents to Lucid 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 Lucid SCIM integration exposes
The Lucid SCIM Agent App exposes 5 provider-backed actions for security and productivity work. Its current contract lets an authorized agent get one lucid scim org group or team by id, get the lucid scim service provider configuration for the connected account, and get one lucid 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 Lucid SCIM account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Lucid 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 Lucid SCIM org group or team by ID.
INPUTS: id / attributes / excludedAttributes
get_service_provider_configREADGet the Lucid SCIM service provider configuration for the connected account.
get_userREADGet one Lucid SCIM user by ID.
INPUTS: id / attributes / excludedAttributes
list_groupsREADList Lucid SCIM org groups or teams with optional SCIM filter, pagination, and attributes.
INPUTS: startIndex / count / filter / attributes / excludedAttributes
list_usersREADList Lucid SCIM users with optional SCIM filter, pagination, and attributes.
INPUTS: startIndex / count / filter / attributes / excludedAttributes
INPUT CONTRACTS
Know what the action needs before it runs.
get_group
idREQUIRED- Lucid SCIM group or team ID, such as lucid-group-1234.
attributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
excludedAttributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
get_user
idREQUIRED- Lucid SCIM resource ID, such as lucid-1234.
attributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
excludedAttributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
list_groups
startIndexOPTIONAL- One-based index of the first SCIM result to return.
countOPTIONAL- Maximum number of SCIM resources to return.
filterOPTIONAL- SCIM group filter. Lucid currently supports single displayName equality filters such as displayName eq "Engineering".
attributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
excludedAttributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
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. Lucid recommends optimized attributes such as email, userName, displayName, or externalId.
attributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
excludedAttributesOPTIONAL- SCIM attributes to include or exclude, sent as a comma-separated list.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Group
Get one Lucid SCIM org group or team 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 Lucid SCIM service provider configuration for the connected account. 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 Lucid SCIM with explicit limits
- Authorize Lucid SCIM with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Lucid 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 Lucid SCIM rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Lucid SCIM task completed successfully.
CONNECTION MODEL
API key
Lucid SCIM bearer token sent in the Authorization header. Generate it in Lucid Admin under App integration > SCIM for admin management or SCIM for content access: https://lucid.app/teams#/apps/integrations-general/scim-for-admin-management
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 Lucid SCIM.