Skip to main content
Version: Omada Identity Cloud

Technical Preview feature: Omada Identity MCP

The Omada Identity MCP (Technical Preview feature) exposes the Omada AI assistant as an MCP server, that is, a service that uses the Model Context Protocol (MCP). MCP is the open standard that AI assistants use to reach external tools. Any client that supports MCP can connect to Omada Identity MCP. This documentation covers Claude (Team, Enterprise, and Desktop) and ChatGPT Enterprise.

It allows you to request access, find resources, and search the Omada documentation from your AI assistant. Depending on your authorization roles, you can also act on pending approvals, revoke access, and review Compliance Workbench data. For details, see Omada Identity MCP tools.

Third-party references

This page refers to third-party products, such as Claude, ChatGPT, Node.js, and Microsoft Entra ID. Omada strives to keep this information up to date, but these products are developed independently of Omada, and their behavior, settings, and error messages may change without notice. If you spot any inconsistency, report it to our Helpdesk.

All product names, logos, and trademarks shown on this page belong to their respective owners.

Prerequisites and availability​

Omada Identity MCP is enabled per environment, on request, as part of your agreement with Omada, with the following conditions:

  • Your agreement with Omada must include the Omada Identity Graph API. Omada Identity MCP works through the Graph API, so without it, this solution cannot access the data that it needs.

  • Omada Identity MCP is only included in Omada Identity Cloud. It is not available in Omada Identity (on-premises) and is currently not supported in Omada Identity Cloud Private.

  • Your environment must be the November 2026 Cloud Update or later.

Previous MCP solution

Omada Identity MCP is different from the previous self-hosted Omada MCP Server project on GitHub. The previous solution is now deprecated.

Omada hosts and operates Omada Identity MCP for you, and you do not deploy or run any server yourself.

How Omada Identity MCP works​

You work with Omada Identity MCP by chatting with your AI assistant in natural language. You do not need to know the names of the tools or call them directly. You describe what you want, for example:

What do I need to approve right now?

The assistant selects the matching Omada Identity MCP tool and answers in the conversation. For actions that change data, such as requesting or revoking access, the assistant shows a form where you review the details and confirm the action before anything is submitted.

Omada Identity MCP follows these rules:

  • The assistant acts as you. Each person signs in with their own account in your identity provider. The assistant sees what you can see and can request only what you could request. Omada records every action against your name.
  • Each person gets their own set of tools. Most Omada Identity MCP tools are gated by an authorization role. A user is offered only the tools whose roles they hold, so two people with different roles see different tools. For the list of roles, see Review the tool authorization roles.
  • No app to install. An administrator adds Omada Identity MCP once to Claude or ChatGPT for the whole organization. A single user can also connect Claude Desktop through a configuration file.

For details on how the sign-in is secured and how you control the connection, see Omada Identity MCP security.

Onboarding overview​

Onboarding has four stages:

  1. Your administrator sends an enablement ticket. An Omada administrator, a partner, or an Omada consultant on your behalf sends an enablement ticket to Omada. See Send the enablement ticket.
  2. Your agreement is updated. Your agreement with Omada is updated to include Omada Identity MCP.
  3. Omada enables the environment. Omada switches on Omada Identity MCP and confirms when the environment is ready. The tool authorization roles are created and assigned to the standard user groups at this point. Reviewing them is optional.
  4. Your administrator configures Omada Identity and the AI assistant. Your administrator configures Omada Identity and your Microsoft Entra ID app registration, as described in Enable Omada Identity MCP. Then an administrator adds Omada Identity MCP to Claude or ChatGPT for the whole organization, and each user signs in. See Connect your AI assistant to Omada Identity MCP.

For the available tools, see Omada Identity MCP tools.