## Documentation

- About
- Read First
  - What is IdentityServer
  - Installation Scenarios
- Migrations
- Bootstrapping
- Configuration & Integration
  - AdminUI Settings
  - Configuring AdminUI
  - Configuring AdminUI (NuGet)
  - Integrating with Identity Server
  - Integrating with Identity Server Custom Schema
  - Integrating with Quickstarts
  - Enabling Logging
- Installation
  - IIS
  - Azure
    - Install in Azure
    - Create Azure Web App
  - Docker
  - NuGet
- Custom Database Connections
- Custom Identity Store
  - Overview
  - Partial Implementation
  - Full Implementation
  - Tenancy With Entity Framework
  - NoSql Implementation (MongoDB)
- Custom CSP
- Users
  - Searching for Users
  - Adding Users
  - Editing Users
  - Deleting Users
  - Merge Users
  - Set User Password
  - Session Management
  - User Reports
  - Bulk User Import
- Roles
  - Creating Roles
  - Managing Roles
  - Managing Users in a Role
  - Managing Role Claims
- Claim Types
- Clients
  - Searching for Clients
  - Adding Clients
  - Adding a SAML Client
  - Adding a WS-Fed Client
  - Editing Clients
  - Deleting Clients
  - Clone Client
- Import and Export
  - Exporting Clients
  - Importing Clients
  - Importing Client Configuration with Secrets
  - Importing SAML Clients with Certificates
  - Import and Export Via the API
- Dynamic Authentication Providers
  - What is Dynamic Authentication
  - Enabling or disabling Dynamic Authentication
  - Add a Dynamic Provider
    - First Steps
    - Adding OIDC Provider
    - Adding SAML Provider
  - Edit a Dynamic Provider
    - Accessing edit view
    - Editing a OIDC Provider
    - Editing a SAML Provider
  - Deleting a Provider
  - Searching for Provider
- Resources
  - Searching for Resources
  - Creating Resources
  - Editing resources
- Webhooks
  - Webhooks
  - Endpoint Configuration
- MCP
  - Overview
  - Default Server Prompt Instructions
- User Settings Endpoints
- Access Policy
- Keys
- Auditing
- FAQs
- Troubleshooting
  - Unable to start AdminUI
  - Unable to contact IdentityServer
  - Unable to contact API
  - Unable to log in

The following are the default instructions on the AdminUI MCP server. If you want change this instructions you can do it from here.

    # AdminUI MCP Server Instructions

    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

    ### User Management

    - Manage user accounts, role assignments, and claim type definitions.
    - Trigger password resets and MFA flows for users.

    ### Client and Resource Management

    - Manage client applications, API resources (Protected Resources), and identity resources.
    - Define and manage scopes for API resources to control access levels.

    ### Audit Tracking

    - Track all actions taken within AdminUI, including changes to users, clients, and resources.
    - If configured, can track also IdentityServer actions like user logging or client authentication challenge.

    ## 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.
    - **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

    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` tool with `query:"Jon", page:1, pageSize:25`
    2. If multiple matches exist, ask the user to clarify which Jon
    3. Once confirmed, 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.
    - Respect the default page size unless its absolutely necessary to change it.
    - For paginated results, if the required information is not found on the first page, ask the user whether they want to continue searching additional pages specialy with the audit tools.

    ## 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.
    - Never omit warning messages even if they seem routine. Warnings often contain important security, confidentiality, or operational information.

    ## Upcoming Features

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

Previous Next