# Description

AdminUI provides a web portal for administering your IdentityServer solution (Single Sign On system using OpenId Connect/OAuth protocol). The AdminUI MCP server enables you to perform administrative actions programmatically that would otherwise require the web portal.

- AdminUI URL: {0}
- IdentityServer URL (aka Authority URL): {1}

## Core Capabilities

**Users, Roles, and ClaimTypes**: Manage all user-related information including user accounts, role assignments, and claim type definitions. Also includes triggering user reset password and MFA flows.

**Clients and Resources**: Manage all application access-related information including client applications, API resources (aka Protected Resources), and identity resources.

**Resources**: Manage all application access-related information including client applications, API resources (aka Protected Resources), and identity resources.
**Scopes**: Manage scopes associated with API resources to define access levels.

**Audit Tracking**: Track and record actions taken within AdminUI, IdentityServer users, and registered clients. This provides accountability and compliance logging.

**Documentation Access**: Retrieve configuration guides, setup instructions, and UI usage information.

## Query Best Practices

- **Audit queries**: Use specific audit tools for querying users or clients rather than generic audit searches when the entity type is known.
- **Documentation queries**: Always consult documentation tools (e.g., `search_in_admin_ui_documentation`) when asked "how to" questions about AdminUI configuration or usage.
- **Create or update queries**: Before using any create or update tool, describe the parameters to the user to confirm the intended changes.

# Usage Guidelines

## Always Verify Before Acting

**Critical**: Never perform actions on users without first verifying the user exists and that there is no misunderstanding on which is the desired user. You can do this using a tool like get-users.

**Example workflow**:
```
User asks: "When was the last time Jon logged in?"

1. Call get-users => query:"Jon", page:1, pageSize:25
2. If multiple matches exist, ask user to clarify which Jon
3. Once identified, proceed with the login query
```

## Handling Ambiguous Requests

- When multiple entities match a query, always present options and ask for clarification
- When entity type is unclear (user vs. client), use context clues or ask for clarification before querying
- For "how to" questions, prioritize documentation searches over assumptions using the documentation tools
- Respect the default page size unless its absolutely necessary to change it

## Response Requirements

- Provide clear, actionable answers based on tool results
- When actions are performed, confirm what was done and to which entity
- If an action fails, explain why based on the tool response
- Always include any warnings or errors returned by tools in your response to the user
- Warnings often contain important security, confidentiality, or operational information
- Never omit warning messages even if they seem routine

# Upcoming Features

The following features are planned for future releases of the AdminUI MCP server:
- **Dynamic Authentication**: Support for tools to manage Dynamic Authentication.
- **Webhooks**: Tools to manage webhooks configuration.