Compatible with every major AI agent and IDE
What is the Casdoor (IAM) MCP Server?
Connect your Casdoor IAM instance to any AI agent to streamline your identity and access management workflows through natural conversation.
What you can do
- User Management — Create, update, delete, and retrieve detailed profiles for users across your organizations using the
add_user,update_user, anddelete_usertools. - Organization Oversight — List all organizations and fetch specific configuration details for your IAM hierarchy with
list_organizationsandget_organization. - Application Control — Query and manage applications registered within your Casdoor instance using
list_applicationsandget_application. - Identity Inspection — Instantly retrieve the profile of the currently authenticated user to verify permissions via
get_userinfo.
How it works
- Subscribe to this server
- Enter your Casdoor Endpoint, Client ID, and Client Secret
- Start managing your identity infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — Automate user provisioning and organization audits without leaving the terminal or IDE.
- Security Teams — Quickly inspect user permissions and application configurations for compliance and security reviews.
- Full-stack Developers — Manage test users and application settings directly while coding to maintain development flow.
Built-in capabilities (10)
Requires owner (organization) and name (username). Add a new user
Requires the owner (organization) and name (username) of the user to delete. Delete a user
Get a specific application
Get a specific organization
Get a specific user by ID
Get the profile of the authenticated user
List applications in an organization
List all organizations
List users in an organization
The ID parameter must be formatted as <organization>/<username>. Update an existing user
Why VS Code Copilot?
GitHub Copilot Agent mode brings Casdoor (IAM) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Casdoor (IAM) in VS Code Copilot
Casdoor (IAM) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Casdoor (IAM) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Casdoor (IAM) in VS Code Copilot
The Casdoor (IAM) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Casdoor (IAM) for VS Code Copilot
Every tool call from VS Code Copilot to the Casdoor (IAM) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I list all users belonging to a specific organization?
Use the list_users tool and provide the organization name in the 'owner' parameter. The agent will return a list of all users registered under that organization.
What format should I use to fetch a specific user's details?
When using the get_user tool, the ID must be formatted as <organization>/<username>. For example, to find user 'alice' in the 'built-in' organization, use 'built-in/alice'.
Can I manage applications and organizations as well?
Yes. You can use list_organizations and get_organization to manage your hierarchy, and list_applications or get_application to inspect app-specific configurations.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Activepieces
32 toolsAutomate workflows with Activepieces — manage flows, monitor executions, and handle app connections directly from your AI agent.

Metorial
8 toolsEnterprise observability and serverless scaling infrastructure directly mapping MCP agents logic.

E2B
3 toolsSecure cloud sandboxes for AI code execution — run Python, JavaScript, and shell commands in isolated Firecracker microVMs with ~150ms cold start.

SEC EDGAR Filings — 10-K, 10-Q, 8-K, Insider Trades & Full-Text Search
6 toolsAccess all SEC filings: 10-K annual reports, 10-Q quarterly reports, 8-K material event disclosures, Form 4 insider trading data, and full-text search across every document ever filed on EDGAR. Filter by company, form type, and date range.
