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.
@asgardeo
Basic information
MCP server to interact with your Asgardeo organization through LLM tools
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
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.
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.
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.
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.
No, it is an experimental feature. Features, APIs, and functionality may change without notice, and it is not intended for use in production environments.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
A search tool helps dev to solve the naming things problem.
Senso MCP turns a Joomla 5 or 6 site into a remote MCP server. It runs inside Joomla itself (no extra server, no Node.js bridge) and is secured with OAuth 2.1 and Joomla's own ACL. The free pack lets an AI assistant crea

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
Comments