MCP server written in Go that lets you configure and manage an Asgardeo organization through LLM-compatible MCP clients (Copilot, Claude Desktop, Cursor, etc.).
https://github.com/asgardeo/asgardeo-mcp-serverIf you're building applications with Asgardeo and find yourself constantly switching between your IDE and the admin console to set up OAuth apps, configure login flows, or manage users, there's a better way. The Asgardeo MCP Server brings your identity management directly into Claude Desktop, GitHub Copilot, and Cursor—no more context switching.
Setting up authentication for a new application typically means:
With natural language commands in your existing LLM tools, you can handle all of this without leaving your development environment.
Application Management: Create SPAs, web apps, mobile apps, and M2M applications with a single prompt. Configure OAuth settings, update claim mappings, and modify login flows using conversational commands.
"Create a new Single Page Application called 'Customer Portal' with redirect URL 'https://portal.example.com/callback' and configure it to include username and email claims"
Dynamic Login Flow Configuration: This is where it gets interesting. Instead of manually dragging authentication steps in the admin UI, describe your desired flow in plain English:
"Update the login flow for my Customer Portal app to use username/password first, then SMS OTP as a second factor"
API Resource Management: Set up API resources and authorize applications to access them without navigating through multiple admin screens:
"Create a new API resource called 'Orders API' with read:orders and write:orders scopes, then authorize my Customer Portal app to access it"
The MCP server works through the Model Context Protocol, which means it integrates natively with:
You get full application lifecycle management—create, configure, update, and authorize—all through natural language in tools you're already using.
The server exposes 20+ specialized tools covering the full spectrum of Asgardeo management:
Each tool accepts natural language parameters and handles the underlying API complexity.
You'll need an Asgardeo organization with an M2M application configured with the appropriate management API scopes. The setup involves:
The server runs locally and securely connects to your Asgardeo organization using your M2M app credentials.
git clone https://github.com/asgardeo/asgardeo-mcp-server.git
cd asgardeo-mcp-server
go build -o asgardeo-mcp
Then configure Claude Desktop, Copilot, or Cursor to use the executable with your Asgardeo credentials.
This is marked as experimental by the Asgardeo team—they're actively developing the feature set. For development and testing environments, it provides immediate productivity gains. The natural language interface significantly reduces the cognitive overhead of IAM configuration.
For teams managing multiple Asgardeo applications or frequently setting up new authentication flows, this bridges the gap between development tools and identity management in a way that feels natural and efficient.
The source is available on GitHub with Apache 2.0 licensing, and the Asgardeo team is accepting contributions as they refine the tool set.