Active Directory MCP Server by CData

Created By
CDataSoftwarea year ago
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Active Directory (beta): https://www.cdata.com/download/download.aspx?sku=CDZK-V&type=beta
Overview

What is Active Directory MCP Server by CData?

This project builds a read-only Model Context Protocol (MCP) server for Active Directory, allowing LLMs to query live data without needing SQL.

How to use Active Directory MCP Server?

  1. Clone the repository and build the server using Maven.
  2. Install the CData JDBC Driver for Active Directory.
  3. Configure your connection and create a properties file for your JDBC connection.
  4. Set up the server configuration for your AI client (e.g., Claude Desktop).
  5. Run the server and query data using natural language.

Key features of Active Directory MCP Server?

  • Read-only access to Active Directory data.
  • Natural language querying without SQL.
  • Integration with AI clients like Claude Desktop.

Use cases of Active Directory MCP Server?

  1. Querying user information from Active Directory.
  2. Retrieving organizational data for reporting.
  3. Integrating with AI tools for enhanced data interaction.

FAQ from Active Directory MCP Server?

  • Can I write data to Active Directory using this server?

No, this server is read-only.

  • Is there a trial version available?

Yes, you can download the free CData MCP Server for Active Directory (beta).

  • What is the licensing for this server?

The MCP server is licensed under the MIT License.

Server Config

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\active-directory.prp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago