HEYM

What is HEYM?

HEYM is a self-hosted, source-available AI workflow automation platform built around LLMs, agents, and intelligent tooling. It integrates with the Model Context Protocol (MCP) in two directions—as a client connecting to external MCP servers and as a server exposing workflows to MCP clients. It is intended for developers and teams who want to visually wire together AI agents, vector stores, web scrapers, HTTP calls, and message queues, then deploy via Docker.

How to use HEYM?

To start HEYM, clone the repository, copy .env.example to .env, run ./run.sh, and open the editor at http://localhost:4017. For MCP client usage, configure agent nodes to connect to any external MCP server; for MCP server usage, add the URL http://localhost:4017/api/mcp/sse to your MCP client configuration. Workflows are then callable from Claude Desktop, Cursor, or any MCP client.

Key features of HEYM

• Visual drag-and-drop workflow canvas with 30+ node types
• AI Assistant to describe workflows in natural language
• LLM & Agent nodes with tool calling and persistent memory
• Multi-agent orchestration with orchestrator and sub-agents
• Human-in-the-Loop (HITL) checkpoints
• Built-in RAG with QDrant vector stores
• MCP client and server support
• Portal to publish workflows as public chat UIs
• LLM traces, cost tracking, and evals
• Self-hosted — your data, your infrastructure

Use cases of HEYM

—

FAQ from HEYM

How does HEYM support the Model Context Protocol?

HEYM supports MCP in two directions: as a client (agent nodes automatically gain tools from any external MCP server) and as a server (workflows exposed at /api/mcp/sse can be called from MCP clients like Claude Desktop or Cursor).

How do I get started with HEYM?

Clone the repository, copy the .env.example file, run ./run.sh, and open the editor at http://localhost:4017. No additional installation is required beyond Docker.

How do I configure HEYM as an MCP server?

Add the following to your MCP client configuration: `{"mcp