Asgardeo MCP Server

What is Asgardeo MCP Server?

The Asgardeo MCP Server allows you to manage your Asgardeo organization or WSO2 Identity Server deployment seamlessly using LLM tools, enabling natural language interactions for various configuration tasks. This software is experimental and not intended for production use.

How to use Asgardeo MCP Server?

Create an M2M application in your Asgardeo or WSO2 Identity Server tenant, authorize the required management API scopes, then clone the repository, install dependencies with go mod tidy, build the executable with go build -o asgardeo-mcp, and configure your MCP client (VS Code, Claude Desktop, or Cursor) with the absolute path to the binary and environment variables BASE_URL, CLIENT_ID, and CLIENT_SECRET. For WSO2 Identity Server, set PRODUCT_MODE to wso2is and optionally CERT_PATH.

Key features of Asgardeo MCP Server

• List, create, and update applications in your organization
• Configure application OAuth/OIDC and claim settings via tools
• Authorize APIs for applications with scopes
• Update login flows using natural language prompts
• Manage API resources, users, and claims
• Supports both Asgardeo and WSO2 Identity Server

Use cases of Asgardeo MCP Server

• Create a Single Page or mobile application with a single natural language prompt
• Retrieve details of any application by name or client ID
• Update an application’s claim configuration to include specific user attributes
• Set up a multi‑step login flow (e.g., username/password then email OTP)
• Create a test user and authorize an API resource from a chat interface

FAQ from Asgardeo MCP Server

What is Asgardeo MCP Server?

It is an MCP server that enables you to manage Asgardeo or WSO2 Identity Server resources (applications, APIs, users, claims) using natural language commands via LLM‑compatible clients like Claude Desktop.

What are the prerequisites for using Asgardeo MCP Server?

You need an Asgardeo organization or a WSO2 Identity Server instance, an M2M application with the required API scopes (Application Management, API Resource Management, Identity Provider, Authenticators, Claim Management, SCIM2 Users, OIDC Scope), and Go 1.18+ installed on your machine. The server communicates over stdio using OAuth2 client credentials.

How do I configure Asgardeo MCP Server for WSO2 Identity Server?

Set the PRODUCT_MODE environment variable to wso2is, replace BASE_URL with your WSO2 Identity Server base URL (e.g., https://<host>/t/<tenant-domain>), and optionally set CERT_PATH to the CA certificate file if using a server with a custom CA.

What should I do if I get a 403 Forbidden error?

Check that your M2M application has all required scopes authorized. Also verify that your client ID, client secret, and organization name in the BASE_URL are correct.

Is Asgardeo MCP Server ready for production use?

No, it is an experimental feature. Features, APIs, and functionality may change without notice, and it is not intended for use in production environments.