lab-mcp-identity-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Look up an Okta user by id. Returns a sanitized profile or not-found. |
| provision_userA | Provision a new Okta user in STAGED status (Tier 2, additive, audited). |
| grant_accessA | Add a user to a group. Normal groups are Tier 2; protected groups are Tier 3 and fail closed until gated. |
| revoke_accessA | Request revoke of group membership (Tier 3). Creates a pending approval; does not execute. |
| deactivate_userA | Request user deactivation (Tier 3). Creates a pending approval; does not execute. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action (provision, get, grant, revoke, deactivate) with no overlap. The descriptions clearly differentiate execute vs. pending approval operations.
All tools follow a consistent verb_noun pattern using snake_case (e.g., deactivate_user, grant_access).
Five tools cover the essential identity management operations without being excessive or insufficient for the stated purpose.
Core lifecycle is covered (provision, read, group grants, deactivation) but lacks update user profile or password reset, leaving a minor gap.