adds-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@adds-mcplist all locked out users"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hg-directory-mcp
A pair of read-only MCP servers for monitoring and investigation of a Microsoft directory + PKI environment:
Server | Purpose | Data sources | Default port |
| Active Directory Domain Services (users, groups, OUs, computers, GPOs, domain metadata) | LDAPS to any DC | 8080 |
| Active Directory Certificate Services (CAs, templates, trust anchors, issued certs) | LDAPS (AD PKI subtree) + WinRM to each online issuing CA | 8081 |
Both servers refuse to mutate anything: adds-mcp opens LDAP with
read_only=True and neither exposes any tool that accepts a write. adcs-mcp
runs only Get-* and read-only registry reads on the CA hosts.
adds-mcp — Active Directory
35 read-only tools grouped by object type:
Domain | Tools |
Users |
|
Groups |
|
OUs |
|
Computers |
|
Group Policy Objects |
|
Domain / directory |
|
Escape hatch |
|
Every attribute is decoded before it leaves the tool: SIDs, GUIDs, FILETIMEs,
userAccountControl, groupType, tick-interval durations, and gPLink.
Related MCP server: BloodyAD MCP
adcs-mcp — Active Directory Certificate Services
Tools are split by data source. AD-side tools work as soon as you have LDAPS
to any DC and the ADDS_* vars set. WinRM-side tools additionally require the
ADCS_* vars and WinRM listeners on each issuing CA.
AD-side (LDAPS to CN=Public Key Services,CN=Configuration,DC=...)
Tool | Description |
| Every Enterprise CA published in the domain |
| Detailed attributes for a single Enterprise CA |
| Root CA certificates published as trust anchors |
| Contents of |
| All templates, with flag decoding |
| One template by displayName / cn / OID / DN |
| Templates that include a given EKU OID |
| Templates a specific Enterprise CA is configured to issue |
| Authority Information Access entries in AD |
| CRL Distribution Points and published CRLs in AD |
| Key Recovery Agent certificates in AD |
| Custom OIDs registered under |
WinRM-side (PowerShell / PSPKI on each online issuing CA)
Tool | Description |
| Certificate DB rows with disposition = issued |
| Requests awaiting officer approval |
| Failed / denied requests |
| Revoked entries |
| Full row + raw cert for a single serial |
| Grouped counts across the CA DB |
| CRL/AIA/CDP settings, allowed templates, publication URIs |
| CA ACL decoded (CA Admins, Certificate Managers, Auditors, …) |
| Per-template certificate manager rights |
| The CA's own certificate chain (PEM) |
| Registry-level CA config from |
Standalone
Tool | Description |
| Decode any PEM or base64 DER cert into JSON (SAN, EKU, key usage, chain) |
3-tier PKI notes
Tier 0 (offline Root) and Tier 1 (offline Policy) aren't queried directly — there's no live endpoint. Use
parse_certificate_pemto inspect any offline root/intermediate cert or CRL you export from them, and cross-reference them withlist_ntauth_cas/list_aia_entries/list_root_casto verify the domain still trusts them.Tier 2 (online Issuing CAs) are the target of the WinRM-backed tools. Provide their hostnames in
ADCS_CA_HOSTSand grant the WinRM service account read rights to the CA (typically membership in the CA's built-in Auditor role on each issuing CA).
Requirements
Python 3.11+
LDAPS reachable from wherever the servers run
For
adcs-mcp: WinRM 5986 (HTTPS) reachable to each entry inADCS_CA_HOSTS, plus a WinRM service account with read rights on the CA
Configuration
Configuration is loaded from environment variables (.env supported). See
.env.example for the full list.
ADDS_* variables are read by both servers (they share the LDAPS bind).
ADCS_* variables are read only by adcs-mcp.
Running
Install the package (add [adcs] extra for WinRM support):
pip install -e . # adds-mcp only
pip install -e ".[adcs]" # adds-mcp + adcs-mcpRun either server:
adds-mcp # HTTP :8080, endpoint /mcp
adcs-mcp # HTTP :8081, endpoint /mcpDocker (two separate images):
docker build -t adds-mcp -f Dockerfile .
docker build -t adcs-mcp -f Dockerfile.adcs .
docker run --rm -p 8080:8080 --env-file .env adds-mcp
docker run --rm -p 8081:8081 --env-file .env adcs-mcpRepository layout
src/
adds_mcp/ # AD DS server
__init__.py
config.py
client.py # ldap3 wrapper, read_only=True, filter/DN escaping
formatting.py # SID/GUID/FILETIME/UAC/groupType decoders
server.py
tools/ # users, groups, ous, computers, gpos, domain, search
adcs_mcp/ # ADCS server (reuses adds_mcp.client for LDAPS)
__init__.py
config.py
ldap_source.py # Points reused ldap client at CN=Public Key Services
winrm_source.py # pypsrp WinRM PowerShell runner (optional)
cert_utils.py # X.509 parsing (cryptography)
server.py
tools/ # cas, templates, trust, issued, admin, parsingThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- -license-quality-maintenanceProvides secure access to Microsoft Entra ID (Azure AD) resources including users, devices, and applications through Microsoft Graph API. Enables querying organizational data with comprehensive audit logging to Azure Blob Storage.Last updated
- Alicense-qualityCmaintenanceEnables Active Directory enumeration and abuse operations through the bloodyAD tool. Supports LDAP queries, user/group management, DNS operations, and security testing directly from AI assistants.Last updated16MIT
- FlicenseAqualityCmaintenanceProvides AI assistants with unified access to on-prem Active Directory via LDAP and Azure AD / Entra ID through the Microsoft Graph API. It enables comprehensive management and search of users, groups, computers, and cloud devices using 18 specialized tools.Last updated18
- Alicense-qualityDmaintenanceEnables managing Active Directory users, groups, and computers using natural language, with support for queries and updates.Last updated55MIT
Related MCP Connectors
Read-only breach intelligence from public feeds: reports THAT a domain leaked, never the data.
Read-only DERO blockchain MCP: 33 tools (12 composites) incl. TELA discovery + bundled docs.
Query WHOIS/RDAP information for domains, IP addresses, CIDR prefixes and ASNs. Self-hostable.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Chiefff-Kiefff/adds-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server