ad-ldap
by seanGSISG
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AD_PORT | No | LDAPS port (default 636, 3269 for Global Catalog) | 636 |
| AD_SERVER | Yes | Domain controller hostname or LDAPS URI (e.g., dc01.example.com or ldaps://dc01.example.com) | |
| AD_BASE_DN | Yes | Base distinguished name for the directory (e.g., DC=example,DC=com) | |
| AD_USE_SSL | No | Must be true; false is rejected because it would send credentials in cleartext | true |
| AD_BIND_USER | Yes | Service account UPN or full DN (e.g., svc-ldap@example.com) | |
| AD_CA_BUNDLE | No | Path to CA bundle file for LDAPS certificate validation (blank = system trust store) | |
| AD_SEARCH_BASE | No | Optional OU to scope searches (e.g., OU=Staff,DC=example,DC=com) | |
| AD_BIND_PASSWORD | Yes | Service account password (stored securely in keychain for plugin, but provided as env var for container) | |
| AD_VALIDATE_CERT | No | Whether to validate the DC's certificate (true/false, default true) | true |
| MCP_BEARER_TOKEN | No | Bearer token for HTTP transport authentication (required if running as HTTP container) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues