Conduct AI MCP server
✓ VerifiziertVerwalte AI Agents, triggere Workflows und erzwinge Security-Policies für dein Team über AI Clients wie Claude Code und Cursor.
Auch bekannt als sseshachala/conduct-cli, conduct-cli
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- 3.139
- Neueste Version
- 0.6.10
- Letzter Commit
- 13. Aug. 2026
- Lizenz
- —
Was ist Conduct AI MCP?
Verwalte AI Agents, triggere Workflows und erzwinge Security-Policies für dein Team über AI Clients wie Claude Code und Cursor.
Zusammenfassung generiert aus dem README des Projekts
Über Conduct AI MCP server
Conduct AI ermöglicht es Engineering-Teams, AI Agents zu verwalten und Security-Policies über verschiedene Entwicklungsumgebungen hinweg durchzusetzen. Entwickler können Agents aus Playbooks installieren, Projekte verwalten und End-to-End-Tests über ein Command Line Interface ausführen. Das System läuft lokal auf Linux, macOS und Windows und benötigt eine Python-Installation sowie einen Agent Token, den du im Conduct AI Dashboard generierst, um dich via conduct login zu authentifizieren.
Security-Teams nutzen ConductGuard, um die Kontrolle über die Nutzung von AI Tools in Clients wie Claude Code, Cursor und Windsurf zu behalten. Durch Ausführen von conduct guard sync installiert das CLI einen PreToolUse Hook und einen MCP server, der Team-Regeln automatisch erzwingt. Dieses Setup ermöglicht es, Tool-Aufrufe basierend auf vordefinierten Policies zu blockieren, zu warnen oder zu auditieren. Das System bietet zudem Tools, um Security-Events auf die OWASP Agentic Top 10 abzubilden und die Compliance in CI-Umgebungen mit dem Befehl conduct verify zu überprüfen.
Was du damit machen kannst
- 1Deployment von Agent FleetsEin Entwickler kann mit nur einem einzigen Befehl eine komplette Suite von Agents für ein spezifisches Repository aufsetzen.
- 2Durchsetzung von Security-PoliciesSecurity-Administratoren können unbefugte Tool-Aktionen verhindern, indem sie Policies automatisch auf die Rechner der Entwickler synchronisieren.
- 3Validierung der AI Security ComplianceTeams können ihre jüngsten Security-Events gegen die OWASP Agentic Top 10 prüfen, um sicherzustellen, dass Sicherheitsstandards eingehalten werden.
- 4Testen von Agent WorkflowsEntwickler können synthetische Test-Payloads triggern, um sicherzustellen, dass ihre installierten Agents korrekt funktionieren.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Conduct AI MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenConduct AI MCP in Claude Code installieren
$ claude mcp add conduct-cli -- uvx conduct-cliConduct AI MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"conduct-cli": {
"command": "uvx",
"args": [
"conduct-cli"
]
}
}
}Conduct AI MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"conduct-cli": {
"type": "stdio",
"command": "uvx",
"args": [
"conduct-cli"
]
}
}
}Conduct AI MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"conduct-cli","type":"stdio","command":"uvx","args":["conduct-cli"]}'Conduct AI MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"conduct-cli": {
"command": "uvx",
"args": [
"conduct-cli"
]
}
}
}Conduct AI MCP in Codex installieren
$ codex mcp add conduct-cli -- uvx conduct-cliConduct AI MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.conduct-cli] command = "uvx" args = ["conduct-cli"]
Conduct AI MCP in Gemini CLI installieren
$ gemini mcp add -s user conduct-cli uvx -- conduct-cliConduct AI MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"conduct-cli": {
"command": "uvx",
"args": [
"conduct-cli"
]
}
}
}Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarsseshachala/conduct-cli is public and reachablegithub.com/sseshachala/conduct-cli ↗Bestanden
- Paket nennt dieses Repository als Quelleconduct-cli names https://github.com/sseshachala/conductai/issues as its sourcepypi.org/project/conduct-cli/ ↗Befund
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for conduct-clipypi.org/project/conduct-cli/ ↗Bestanden
- Open Source Lizenz (OSI)No licenseBefund
- Commit oder Release im letzten JahrLast commit or release 2026-08-13github.com/sseshachala/conduct-cli ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from conduct-cliBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten6 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenconduct-cli
Official CLI for Conduct AI — install AI agents, manage projects, run end-to-end tests, and enforce team AI policies with ConductGuard.
Runs on Linux, macOS, and Windows. Python 3.9–3.12.

Install
pip install conduct-cli
Quick start
# Authenticate (one-time)
conduct login \
--server https://api.conductai.ai \
--token cond_agt_xxx \
--workspace <workspace-id>
# Browse available agents
conduct playbooks
# Create a project and install all agents in one shot
conduct install-all --project DevOps --repo owner/repo
# List installed agents
conduct agents
# Run a test trigger on any agent
conduct test "PR Reviewer"
conduct test --all
Commands
| Command | Description |
|---|---|
conduct login |
Save connection config to ~/.conduct/config.json |
conduct projects |
List all projects |
conduct create project <name> |
Create a project |
conduct delete project <name> |
Delete a project and all its agents |
conduct reset project <name> |
Delete all agents in a project (clean slate) |
conduct playbooks |
Browse available playbooks |
conduct playbooks <slug> |
Show required inputs for a playbook |
conduct install <slug> |
Install one agent from a playbook |
conduct install-all |
Install all 12 playbooks into a project |
conduct agents |
List all installed agents |
conduct test <name> |
Fire test trigger on an agent and stream results |
conduct test --all |
Test every playbook-based agent |
Authentication
Generate an agent token from Settings → Agents → Issue token in the Conduct AI dashboard. Tokens start with cond_agt_ and are stored as SHA-256 hashes — the plaintext is shown only once.
conduct login --server https://api.conductai.ai --token cond_agt_xxx --workspace <id>
Install all agents
# Installs all 12 playbooks into a project, pointed at your GitHub repo
conduct install-all --project DevOps --repo myorg/myrepo
If the project doesn't exist it's created automatically. Use --input key=value to override any playbook input.
Test agents
# Test a single agent (fires synthetic test payload, streams run events)
conduct test "Autopilot Quick"
# Test all playbook-based agents in sequence
conduct test --all
Exit code is 0 if all pass, 1 if any fail — works in CI.
ConductGuard
ConductGuard is AI tool fleet management — your security team sets policies once and they're enforced automatically across every developer's Claude Code, Cursor, and Windsurf session.
How it works
Admin configures policies and budgets in the Guard dashboard
└─ developers are workspace members automatically — no invite step needed
Developer runs: conduct guard sync
├─ pulls latest policy to ~/.conductguard/policy.json
├─ writes PreToolUse hook → ~/.conductguard/hook.py
├─ registers hook → ~/.claude/settings.json
└─ registers conductguard-mcp → ~/.claude/settings.json (mcpServers) + Codex
Every Claude Code tool call:
├─ PreToolUse hook fires (hook.py) → checks policy → block / warn / audit
└─ Event posted async to ConductGuard API → visible in Activity feed
Developer setup
pip install conduct-cli
# Authenticate (already done if you use Conduct)
conduct login --server https://api.conductai.ai --api-key <api-key>
# Sync Guard — installs hook + MCP, pulls policies
conduct guard sync
That's it. Policy enforcement is active from the next tool call.
Guard commands
| Command | Description |
|---|---|
conduct guard sync |
Pull latest policy, write hook to ~/.conductguard/hook.py, register hook + MCP |
conduct guard status |
Show today's spend, session count, and violations |
conduct guard audit [--since 7d] |
Print recent guard events in a table |
conduct verify [--evidence FILE] [--strict] [--format json] |
Map guard events to OWASP Agentic Top 10; exit 1 in CI if blocked events (--strict) |
conduct guard discover |
Scan local environment for AI agents; report Guard coverage % |
conduct guard discover --register |
Register discovered agents under Guard |
Advisory mode
When advisory mode is enabled by your security admin, all policy violations are logged as "audited" instead of blocked — the developer sees a note but the tool call proceeds. The hook still posts every event to the audit log.
To check if advisory mode is active:
conduct guard sync # shows "· advisory" badge if active
conduct guard status
conduct verify
# Map last 24h of guard events to OWASP Agentic Top 10
conduct verify
# Use a saved evidence file
conduct verify --evidence ./conduct-evidence.json
# CI mode — exit 1 if any blocked events
conduct verify --strict
# JSON output for downstream tooling
conduct verify --format json
OWASP mapping: no-rm-rf → A04 Excessive Agency, no-sudo → A09 Privilege Escalation, policy_signature_invalid → A07 Insufficient Monitoring, etc. All 10 categories covered.
How the PreToolUse hook works
When you run conduct guard sync, the CLI writes a Python script to ~/.conductguard/hook.py and registers it as a PreToolUse hook in ~/.claude/settings.json:
{
"hooks": {
"PreToolUse": [
{
"matcher": ".*",
"hooks": [{ "type": "command", "command": "python3 ~/.conductguard/hook.py" }]
}
]
}
}
Before every tool call, Claude Code runs the hook. The hook:
- Reads
tool_nameandtool_inputfrom stdin (JSON) - Loads
~/.conductguard/policy.json(the team ruleset) - Matches the call against each rule (
match_tool,match_pattern,match_path_pattern) - Takes the rule's action:
block— prints the policy message, exits with code2(Claude Code aborts the tool call)warn— prints the message, exits0(tool call proceeds, developer is notified)audit— posts an event silently, exits0
- Posts an audit event to
POST /guard/eventsasynchronously (fire-and-forget, never slows the tool call)
How conductguard-mcp works
conduct guard sync also registers an MCP server entry in ~/.claude/settings.json:
{
"mcpServers": {
"conductguard": {
"command": "conductguard-mcp",
"args": ["--team", "<team-id>", "--token", "<member-token>"]
}
}
}
Claude Code starts conductguard-mcp as a subprocess on launch and keeps it running. It communicates via JSON-RPC 2.0 over stdin/stdout (MCP stdio transport).
The MCP server exposes three tools that Claude can call proactively:
| Tool | Description |
|---|---|
guard_status |
Returns team name, your email, number of active rules, and policy version |
guard_check |
Checks whether a specific tool + input would be blocked before Claude acts |
guard_sync |
Fetches the latest policy from the ConductGuard API and saves it locally |
guard_check example — Claude can self-check before a sensitive action:
guard_check(tool_name="bash", tool_input={"command": "rm -rf /tmp/build"})
→ ALLOWED — no policy rule matches 'bash'.
guard_check(tool_name="bash", tool_input={"command": "curl http://internal-api/secrets"})
→ BLOCKED — External network calls to internal endpoints are not permitted. [rule: no-internal-curl]
guard_sync example — after your security team pushes new rules:
guard_sync()
→ Policy synced — 12 rule(s) active (version: 2026-05-31T14:22:00Z).
Policy file format
Policy is stored at ~/.conductguard/policy.json and synced from the server:
{
"team_id": "uuid",
"version": "2026-05-31T14:22:00Z",
"rules": [
{
"rule_id": "no-rm-rf",
"match_tool": "bash",
"match_pattern": "rm\\s+-rf",
"match_path_pattern": null,
"action": "block",
"message": "Recursive deletes are not permitted. Use trash or targeted rm."
},
{
"rule_id": "audit-prod-writes",
"match_tool": "edit,write",
"match_path_pattern": "/prod/",
"match_pattern": null,
"action": "warn",
"message": "Writing to prod directory — make sure this is intentional."
}
]
}
Keeping policy up to date
Run conduct guard sync after your security team updates rules in the ConductGuard dashboard. The sync command pulls the latest policy, rewrites the hook, and re-registers the MCP entry in any newly detected AI tool configs.
# Add to a daily cron or run manually after policy changes
conduct guard sync
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"conduct": {
"command": "conduct-mcp",
"args": []
},
"conductguard": {
"command": "conductguard-mcp",
"args": ["--team", "<workspace-id>", "--token", "<member-token>"]
}
}
}
Run conduct login first — conduct-mcp reads credentials from ~/.conduct/config.json. Get your agent token from Settings → Agents → Issue token in the Conduct AI dashboard.
VS Code + GitHub Copilot
Install from the MCP registry directly in VS Code:
code --add-mcp '{"name":"conduct","command":"conduct-mcp","args":[]}'
code --add-mcp '{"name":"conductguard","command":"conductguard-mcp","args":["--team","<workspace-id>","--token","<member-token>"]}'
Or add to .vscode/mcp.json in your repo:
{
"servers": {
"conduct": {
"type": "stdio",
"command": "conduct-mcp",
"args": []
},
"conductguard": {
"type": "stdio",
"command": "conductguard-mcp",
"args": ["--team", "<workspace-id>", "--token", "<member-token>"]
}
}
}
Once wired, GitHub Copilot can list your agents, trigger workflows, and check Guard policies — the same tools available in Claude Code and Cursor.
Prerequisites: pip install conduct-cli + conduct login
Links
- Dashboard: conductai.ai
- Docs: conductai.ai/docs
- Issues: github.com/sseshachala/conductai/issues
Conduct AI MCP Fragen
Wie füge ich Conduct AI MCP zu Claude Code hinzu?
Führe claude mcp add conduct-cli -- uvx conduct-cli in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Conduct AI MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie installiere ich Conduct AI?
Du kannst das offizielle CLI über pip mit dem Befehl pip install conduct-cli installieren.
Was ist ConductGuard?
ConductGuard ist ein Management-System für AI Tool Fleets, mit dem Security-Teams Policies festlegen können, die automatisch in den AI-Sessions der Entwickler durchgesetzt werden.
Kann ich Conduct AI in meiner CI/CD-Pipeline nutzen?
Ja, der Befehl conduct test --all gibt den Exit Code 0 zurück, wenn alles erfolgreich ist, und 1, wenn etwas fehlschlägt, was ihn ideal für CI-Umgebungen macht.