Bring It Documentation
to CrewAI
Learn how to connect Hudu to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hudu MCP Server?
Connect your Hudu instance to any AI agent and manage your IT documentation through natural conversation.
What you can do
- Company Management — List all client companies, inspect profiles, and create new company records
- Asset Tracking — Browse all assets (servers, workstations, network devices), filter by company, inspect details, and create new asset records with tags
- Password Vault — List stored passwords filtered by company, and securely retrieve individual password entries with secrets
- Knowledge Base — Browse all articles and read full content with metadata for any specific article
- Procedures & Checklists — List all procedures filtered by company and inspect detailed steps for operational checklists
How it works
1. Subscribe to this server
2. Enter your Hudu Instance URL and API Key
3. Start managing IT documentation from Claude, Cursor, or any MCP-compatible client
Who is this for?
- MSPs (Managed Service Providers) — access client documentation, passwords, and asset inventories without opening the Hudu portal
- IT Administrators — track assets, review procedures, and manage knowledge base articles through AI
- Support Engineers — quickly retrieve client passwords, asset details, and troubleshooting procedures during incidents
Built-in capabilities (12)
Requires asset name and company ID. Create a new asset
Requires a name. Create a new company
Get details for a specific article
Get details for a specific asset
Get details for a specific company
Get details for a specific password
Get details for a specific procedure
List knowledge base articles
Can be filtered by company ID. List assets
List all companies in Hudu
Can be filtered by company ID. List passwords
Can be filtered by company ID. List procedures
Why CrewAI?
When paired with CrewAI, Hudu becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hudu tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Hudu in CrewAI
Hudu and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hudu to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hudu in CrewAI
The Hudu MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Hudu for CrewAI
Every tool call from CrewAI to the Hudu MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I retrieve stored passwords for a specific client?
Yes. Use list_passwords with an optional company_id to filter passwords by client. Then use get_password with a specific password ID to retrieve the full entry including the secret. Use list_companies to find the company ID first.
Does Hudu require a custom instance URL?
Yes. Hudu is self-hosted or uses dedicated instances, so you need to provide your Instance URL (e.g., https://your-company.huducloud.com) along with the API Key. The API Key is sent via the x-api-key header (not Bearer), and all API calls are routed to {instanceUrl}/api/v1.
Can I track all assets for a specific company?
Yes. Use list_assets with the company_id parameter to retrieve all assets (servers, workstations, network devices) for a specific client. Use get_asset for detailed specifications and tags. Use create_asset to add new assets with a name, company ID, and optional asset tag.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.