BloodHound MCP Server

If you want an AI assistant working directly with BloodHound, the bloodhound mcp server is the bridge. integration that connects BloodHound with AI through MCP, allowing security professionals to analyze Active Directory attack paths using natural language queries instead of Cypher.

What BloodHound does

BloodHound-MCP is a powerful integration that brings the capabilities of Model Context Procotol (MCP) Server to BloodHound, the industry-standard tool for Active Directory security analysis. This integration allows you to analyze BloodHound data using natural language, making complex Active Directory attack path analysis accessible to everyone.

Installing the bloodhound mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads 3 environment variables: BLOODHOUND_URI, BLOODHOUND_USERNAME, BLOODHOUND_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

File and storage servers are what separate an assistant that talks about your documents from one that actually works with them. BloodHound sits in that group. Worth comparing against the other file systems servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the bloodhound mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.