Bring It Documentation
to Cursor
Learn how to connect Hudu to Cursor 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 Cursor?
Cursor's Agent mode turns Hudu into an in-editor superpower. Ask Cursor to generate code using live data from Hudu and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Hudu in Cursor
Hudu and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hudu to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.