Automation and no-code
Connect Hyperdex to the workflow and chat platforms your team already uses, without writing code. Each one gets the same tools as any other agent.
| Endpoint | https://hyperdex.hypervect.com/mcp |
| Transport | Streamable HTTP (MCP 2026-07-28; 2025-era clients also work) |
| Authentication | Header Authorization: Bearer hdx_… |
- n8n
- Zapier
- Make
- Dify
- Flowise
- Langflow
- Voiceflow
- LibreChat
- Open WebUI
- Microsoft Copilot Studio
- Platforms that only run local servers
n8n
On an AI Agent node, add the MCP Client Tool. Set the endpoint to https://hyperdex.hypervect.com/mcp, the server transport to HTTP Streamable, and authentication to Bearer Auth with a new credential holding your key. Choose which Hyperdex tools the agent may use under Tools to Include.
A good first workflow: a Gmail or WhatsApp trigger, an AI Agent with Hyperdex, and the inbox assistant instructions as its system message.
Zapier
Add a connection to the MCP Client app (in beta): server URL https://hyperdex.hypervect.com/mcp, transport Streamable HTTP, OAuth No, and your key as the Bearer Token. In a Zap, use Run Tool, for example log_activity whenever a new form response or email arrives.
Make
Add the MCP Client module, create a connection, choose New MCP Server, enter https://hyperdex.hypervect.com/mcp and paste your key into API Key / Access token.
Dify
Open Tools, MCP, Add MCP Server (HTTP) and enter https://hyperdex.hypervect.com/mcp. Under Advanced Options, add a custom header Authorization with the value Bearer hdx_your_key, and turn off dynamic client registration so Dify does not try OAuth.
Flowise
Create a Flowise variable named hyperdex holding your key, then add a Custom MCP tool with this configuration:
{
"url": "https://hyperdex.hypervect.com/mcp",
"headers": { "Authorization": "Bearer {{$vars.hyperdex}}" }
}Langflow
In Settings, MCP Servers, Add MCP Server, HTTP/SSE, enter https://hyperdex.hypervect.com/mcp and add a header Authorization whose value is a global variable containing Bearer hdx_your_key (the word Bearer must be part of the value). Then add the MCP Tools component in tool mode and connect it to your agent.
Voiceflow
In Settings, MCP servers (or an MCP step), enter https://hyperdex.hypervect.com/mcp, add the header Authorization with Bearer hdx_your_key, and choose which tools the agent may use. Useful for voice and chat agents that should remember every caller.
LibreChat
Add Hyperdex to librechat.yaml. Each user enters their own key in LibreChat, so keys are never shared.
mcpServers:
hyperdex:
type: streamable-http
url: https://hyperdex.hypervect.com/mcp
requiresOAuth: false
headers:
Authorization: "Bearer {{HYPERDEX_API_KEY}}"
customUserVars:
HYPERDEX_API_KEY:
title: "Hyperdex API key"
sensitive: trueOpen WebUI
From version 0.6.31, open Admin Settings, Integrations, External Tool Servers, Add Connection. Choose type MCP (Streamable HTTP), enter https://hyperdex.hypervect.com/mcp, and set authentication to Bearer with your key. No mcpo proxy is needed.
Microsoft Copilot Studio
In your agent, choose Tools, Add a tool, New tool, Model Context Protocol. Enter a name, a description and https://hyperdex.hypervect.com/mcp. For authentication choose API key, type Header, header name Authorization. When you create the connection, enter your key; Hyperdex accepts it with or without the word Bearer.
Platforms that only run local servers
If a platform can only start local (stdio) MCP servers, bridge to Hyperdex with the community mcp-remote package. It needs Node.js on the same machine.
{
"command": "npx",
"args": ["-y", "mcp-remote", "https://hyperdex.hypervect.com/mcp",
"--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer hdx_your_key" }
}Checked against each vendor’s own documentation in October 2026. Products change quickly; if a step no longer matches, write to transform@hypervect.com and we will update it.