BloodHound MCP
BloodHound MCP (Model Context Protocol) is an innovative extension of the BloodHound tool, designed to enable Large Language Models (LLMs) to interact with and analyze Active Directory (AD) and Azure Active Directory (AAD) environments through natural language queries. By leveraging the power of LLMs, BloodHound MCP allows users to perform complex queries and retrieve insights from their AD/AAD environments using simple, conversational commands.
Features
- Natural Language Queries: Use conversational language to query your AD/AAD environment without needing to write Cypher queries manually.
- LLM-Powered Analysis: Harness the capabilities of Large Language Models to interpret and execute queries on your behalf.
- Seamless Integration: Works with existing BloodHound data stored in Neo4j, providing a user-friendly interface for complex analysis.
- Customizable: Easily configure the system to work with your specific environment and tools.
Configure the MCP Server
{
"mcpServers": {
"BloodHound": {
"name": "BloodHound",
"isActive": true,
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli],neo4j",
"mcp",
"run",
"<PATH_TO_THE_PROJECT>server.py"
],
"env": {
"BLOODHOUND_URI": "bolt://localhost:7687",
"BLOODHOUND_USERNAME": "neo4j",
"BLOODHOUND_PASSWORD": "bloodhound"
}
}
}
}
Usage
Configuration
To customize BloodHound MCP, update the configuration file in your MCP-supported tool. Key settings include:
- Neo4j Database Connection:
BLOODHOUND_URI: The URI of your Neo4j database (e.g., bolt://localhost:7687).BLOODHOUND_USERNAME: Your Neo4j username.BLOODHOUND_PASSWORD: Your Neo4j password.
- Server Settings: Adjust the command and args to match your environment and tool requirements.
Contributing
We welcome contributions to BloodHound MCP! To get involved:
- Fork the Repository: Create your own copy on GitHub.
- Create a Branch: Work on your feature or fix in a new branch.
- Submit a Pull Request: Include a clear description of your changes.
Special Thanks
Custom queries from : https://github.com/CompassSecurity/BloodHoundQueries
Metadata
Release files for iflow-mcp_stevenyu113228_bloodhound_mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2.tar.gz | 10.8 kB | Without provenance | Details for iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2-py3-none-any.whl |
Total release size: 22.3 kB
Release files / iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2.tar.gz
| Download URL | iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5b0bf9a72d60c26876eb23b4d2ca7fe816a7a80ea69aff71c6d14fcd557a773
|
|
BLAKE2b-256 checksum How to use checksums |
45b35c0161b40fc596425dad41d5a24fd7cea3ac97defaf743001dfdbd1e8d76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2-py3-none-any.whl
| Download URL | iflow_mcp_stevenyu113228_bloodhound_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1bcbd228dc8a2b3b66c2e4600508f819935d759525ee53298d1522f49c253c5
|
|
BLAKE2b-256 checksum How to use checksums |
ebdbf4383de59f3537bf9b3a1833fb211cd260c2710956e63869718c5190e4bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_stevenyu113228_bloodhound_mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.