Use Hoko with n8n
Connect n8n through MCP, REST, or the private Hoko node.
Before you start
The private node targets self-hosted n8n 2.42.x with Node.js 24. n8n Cloud is not verified. Create a key with linksRead and linksWrite as needed.
Connect n8n
Store the key in an n8n Hoko credential. For MCP, use https://mcp.hoko.to with a bearer header. For REST, use https://api.hoko.to, GET /collections, POST /links, and GET /links?externalId=....
Verify the connection
Run a credential test or list links before creating anything. Keep Retry On Fail off for creates. Reconcile an uncertain create by external ID.
Fix common issues
- A 401 means the key is invalid or revoked.
- A 403 means a scope is missing.
- A 429 requires Retry-After.
- Keep the key in n8n's encrypted store.
Disconnect
Disable workflows, remove the credential and node, and revoke the key.
Choose the path
Use the MCP Client node with https://mcp.hoko.to when you need the shared MCP tools. Use HTTP Request with https://api.hoko.to for direct REST. The private node is a self-hosted package path for n8n 2.42.x and Node.js 24. n8n Cloud is not verified.