Give the agent you already run a business to operate.
Bring the agents you already run and give them a business to operate. Connect Helm to Claude Code, Claude Desktop, Cursor, Windsurf, or Codex over an open-source MCP server, or drive everything from the helm-ai CLI. One API key opens 84 tools across every app: projects, tasks, time, invoices, CRM, calendar, and more.
Connect the client you already use.
One config block and an API key. Each guide walks through setup for that client.
Claude Code
Anthropic · Terminal coding agent
Run your whole business from the same terminal you ship code in.
Claude Desktop
Anthropic · Desktop app
Talk to Claude about your business, and let it act on the answer.
Cursor
Anysphere · AI code editor
Track the work in Helm while Cursor writes the code.
Windsurf
Codeium · Agentic IDE
Your business data, right next to your codebase.
Codex
OpenAI · CLI coding agent
Give the Codex CLI your whole business to work with.
Any stdio-capable MCP client works, plus your own agents on the Claude API. No provider lock-in.
██╗ ██╗███████╗██╗ ███╗ ███╗ ██║ ██║██╔════╝██║ ████╗ ████║ ███████║█████╗ ██║ ██╔████╔██║ ██╔══██║██╔══╝ ██║ ██║╚██╔╝██║ ██║ ██║███████╗███████╗██║ ╚═╝ ██║ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝
Claude
Codex
OpenClaw
HermesA CLI and an MCP server.
Same workspace, same 84 tools, same data. Pick the door that fits how you work.
The CLI
@helm-ai/cli
Drive your whole business from the terminal. Create tasks, list overdue invoices, log time, and send email as an agent. Scriptable and built for automation.
$ npm i -g @helm-ai/cliThe MCP server
@helm-ai/mcp-server
Expose your workspace to any stdio MCP host. Claude Code, Cursor, Windsurf, Codex, or your own agent reads and writes Helm directly, with the same tools and the same data.
$ npx @helm-ai/mcp-server84 tools. Every app.
Your agent reads and writes the same records your team edits by hand. Full tool reference in the setup docs.
Products
Manage the catalog, prices, and account and deal line items.
Forms
Create lead forms, steps, and fields. Read submissions and stats.
Agent Schedules
List, create, update, and delete scheduled agent runs.
Sequences & more
Email sequences, enrollments, workflows, and attachments.
Questions about bringing your own agent.
What does "bring your own agent" mean?
You already run an agent or AI client (Claude Code, Cursor, Codex, or something you built). Instead of rebuilding it inside Helm, you point it at Helm over MCP or the CLI, and it gains a real business to operate: your projects, tasks, invoices, CRM, and more.
CLI or MCP, which should I use?
Use the CLI (@helm-ai/cli) to drive Helm from a terminal or a script. Use the MCP server when you want an AI client or agent (Claude Code, Cursor, Windsurf, Codex, or your own) to read and write Helm as it works. Both authenticate the same way and reach the same 84 tools.
Which clients are supported?
Any client that speaks MCP over stdio. Confirmed: Claude Code, Claude Desktop, Cursor, Windsurf, Codex, and custom agents built on the Claude API or any framework. ChatGPT and Claude.ai web connectors need a remote (HTTP) server, which is on the roadmap.
How does authentication work?
Generate a workspace-scoped API key in Helm under Settings → API Keys, then pass it as HELM_API_KEY to the CLI or your MCP client. The key grants access to every tool your plan supports. Rotate or revoke it anytime, and every call is logged.
Is it open-source?
Yes. The CLI and the MCP server are MIT-licensed and published on npm as @helm-ai/cli and @helm-ai/mcp-server. Install via npx or global npm, or fork them for custom deployments.
Bring your agent to your business.
Open-source. MIT-licensed. Included on every plan.